Query and Task Management Process Documentation
Introduction
Our query and task management process ensures timely resolution of all queries and issues. It involves structured steps and follow-ups to guarantee that no query goes unresolved within a reasonable timeframe. Agents and staff are encouraged to use our internal app or the provided JotForm link to proactively send queries to the correct department. The term "escalation" is reserved for issues that require the Branch Manager's intervention.
- Steps of the Query and Task Management Process
Initial Query Submission
- Agents can send their queries to support via the internal app or the JotForm link: Internal Query Form.
- If the internal app is used, it guides the agent proactively on the appropriate department and helps structure an email so that support can follow up effectively.
- This action triggers a task creation on our CRM system (Salesforce) by our support team as they receive a copy of the emai
- Staff is required to update the google sheets by 4:00pm daily to ensure ownership assignment and status updates are addressed timely.
- Email 1: Initial Email to Department
- The support team sends a well-structured email to the correct department the same day the query is received. If the app is not used, the agent would have either called or sent an email.
- Task Status: In Progress, Priority: Normal.
- Regular Communication
- The support team should provide regular communication to the agent regarding the status of their query.
- If there is no resolution within 3 working days, the support team sends a follow-up email to the department.
- TAT: 3 days from the initial email.
- The task is updated to reflect the follow-up action, "waiting on someone else."
- Email 2: Follow-Up Email to Department
- If there is no resolution within 3 more days (working day 4), the support team sends another follow-up email copying the BMA (Branch Manager's Assistant) and the Department Team Leader (TL).
- TAT: 3 days from the last email.
- The task status is updated accordingly in Salesforce.
- BMA Liaison with Team Leaders
- If the issue remains unresolved for 7 days, the support creates a follow-up task for the BMA, determining the priority (high, medium, or low) and sending the email trail for the BMA to review and direct accordingly.
- The BMA liaises with the team leader on day 7-8 via email trail and a call.
- This step is not an escalation but a reinforcement of communication efforts.
- The BMA sends the email trail that was prepared by the support to the team leader and has 2 days to resolve the issue.
- The status of the original task is updated to "waiting on someone," and the follow-up task to the BMA is set to "not started" with priority "High."
- Before assigning the task to the BMA, the support team ensures that the last correspondence is sent to the BMA for a proper update.
- Automation Trigger at 10 Days
- If the issue remains unresolved for 10 days, an automated email is sent to the agent from the original task opened by support with an internal JotForm link to gather insights from the agent and review whether the support and BMA followed the process.
- The automation states that 10 days have passed without resolution and the issue will now move to an escalation. The agent is asked for additional insights.
- The task is updated to reflect the escalation process.
- A task is then created by the BMA to the Branch Manager for the escalation, including the follow-up email from the BMA and the agent's response from JotForm.
- Branch Manager Intervention
- If the BMA and team leader cannot resolve the issue within 2 days, it becomes an escalation to the Branch Manager.
- The Branch Manager has 1 day to resolve the issue, relying on the email trail prepared by the BMA.
- The task status is updated to reflect the escalation.
- The Branch Manager will request responses from both the support and the BMA to understand the issue before escalating further to the VPs if necessary.
Reporting and Accountability
Daily reports are generated at 8 am and are visible on the branch WhatsApp group and dashboards for transparency and accountability.
Best Practices from Salesforce for further reading and learing by support team
- Creating Effective Tasks and Events
- Create tasks/events from the lowest level records to ensure proper linking and reduce errors. For example, create a task on an Opportunity record rather than on the Account or Contact record (StarrData).
- Logging Calls
- Log calls during or immediately after the call to ensure accuracy and accessibility of information for the team (StarrData).
- Using Salesforce Queues
- Implement Salesforce Queues to manage and prioritize tasks effectively. Queues can distribute and assign records such as cases, leads, and tasks among team members, enhancing workflow efficiency (Salesforce Ben).
- Automation and Notifications
- Configure system automation to send email alerts, push notifications, and in-app alerts to remind and help improve prospect follow-up. This helps maintain timely communication and task management (StarrData).
- Fault Paths in Flows
- Design fault paths in your flows to handle errors effectively. This includes showing error screens for screen-based flows or sending email alerts containing error messages to a designated group (Salesforce Admins).