ADM-201 Managing the Support Process

Managing the Support Process Detailed Explanation

Salesforce's service management tools are designed to enhance customer support efficiency. By properly configuring and using features like Case Management, Knowledge Base, and the Service Console, organizations can ensure quick and effective resolution of customer issues.

9.1 Case Management

Cases are Salesforce’s way of tracking and managing customer issues, complaints, or service requests. Case Management tools streamline the process of assigning, tracking, and resolving these cases.

Case Queues

What Are Case Queues?

• Queues allow multiple users to share responsibility for managing cases. Cases in a queue are unassigned until a team member claims them.

How to Configure Case Queues

1. Go to Setup and search for Queues.
2. Click New to create a queue.
3. Set the Queue Name (e.g., "Technical Support Team").
4. Choose the Objects the queue applies to (e.g., Cases).
5. Assign Users or Groups to the queue.
6. Save the queue.

Example Use Case

• A "Billing Support" queue is created for all cases related to invoices and payments. Members of the billing team can claim cases from the queue.

Auto-Response Rules

What Are Auto-Response Rules?

• Automatically send acknowledgment emails to customers when they submit cases via email, web forms, or other channels.

How to Configure Auto-Response Rules

1. Navigate to Setup and search for Auto-Response Rules.
2. Select the object (e.g., Cases).
3. Create a new rule and define the criteria:
   • Example: If the Case Type is "Technical Support," send a specific email template.
4. Assign an email template for each rule entry.
5. Activate the rule.

Example Use Case

• A customer submits a case via a web form. An auto-response rule sends an email acknowledging receipt of the request and providing a case number.

9.2 Knowledge Base

The Salesforce Knowledge Base allows organizations to create, store, and share articles that help resolve common issues quickly.

What Is a Knowledge Base?

• A centralized repository of articles, FAQs, and documentation that support agents and customers can use to find answers to questions.

Features of Knowledge Base

1. Article Types:
   • Define different templates for various types of articles (e.g., FAQ, How-To).
2. Publishing Workflow:
   • Articles can go through a review and approval process before being published.
3. Article Search:
   • Agents can search for relevant articles directly within a Case record or the Service Console.

How to Create a Knowledge Article

1. Go to the Knowledge tab.
2. Click New to create a new article.
3. Select the article type (e.g., FAQ, How-To).
4. Enter the content, such as title, body, and relevant tags.
5. Save and publish the article.

Example Use Case

• A customer reports a technical issue. A support agent searches the Knowledge Base and finds an article with step-by-step troubleshooting instructions, which they share with the customer.

9.3 Service Console

The Service Console is a workspace designed specifically for support agents to manage cases, search for knowledge articles, and interact with customers efficiently.

What Is the Service Console?

• A unified, customizable workspace that displays all the tools and information a support agent needs on a single screen.

Features of the Service Console

1. Tabs:
   • Cases, Contacts, Knowledge Articles, and other relevant records open in tabs, reducing the need to switch screens.
2. Case Feed:
   • Displays the history of customer interactions in a timeline format.
3. Macros:
   • Automates repetitive actions, such as sending a standard email response or updating a case status.
4. Omni-Channel Routing:
   • Automatically assigns cases, chats, and other work items to agents based on their availability and skill set.

How to Configure the Service Console

1. Go to Setup and search for App Manager.
2. Select the Service Console app and click Edit.
3. Customize the layout:
   • Add tabs for frequently accessed records or tools.
   • Include components like Knowledge Search and Case Feed.
4. Save and assign the app to the appropriate user profiles.

Example Use Case

• An agent opens the Service Console and sees a list of open cases in their queue. They claim a case, review the customer's previous interactions in the Case Feed, search the Knowledge Base for troubleshooting instructions, and use a macro to send a follow-up email.

Step-by-Step Summary

1. Case Management

• Use Queues to organize cases by team or department.
• Configure Auto-Response Rules to send acknowledgment emails automatically.

2. Knowledge Base

• Create and publish articles to help agents and customers resolve common issues.
• Integrate the Knowledge Base with the Service Console for quick access.

3. Service Console

• Customize the Service Console to display relevant tools and information.
• Use features like Macros and Omni-Channel Routing to improve agent productivity.

Key Takeaways for Beginners

• Case Queues: Ensure efficient case assignment and management by teams.
• Auto-Response Rules: Enhance customer satisfaction with immediate acknowledgment emails.
• Knowledge Base: Empower agents and customers with quick access to helpful resources.
• Service Console: Optimize agent workflows with an all-in-one support workspace.

Managing the Support Process (Additional Content)

1. Case Assignment Rules (Automatically Assigning Cases to the Right Support Team)

Why is it important?

• Case Assignment Rules ensure that incoming cases are automatically assigned to the correct support team or individual, improving response times and efficiency.
• Reduces the need for manual case triaging, ensuring customers get faster resolutions.

How to Configure Case Assignment Rules

1. Navigate to Setup → Search for Case Assignment Rules.
2. Click New → Name the rule (e.g., "Premium Support Cases").
3. Click New Rule Entry → Define the criteria:

• If Case Type = Urgent, assign to "Senior Support Team".
• If Case Region = APAC, assign to "APAC Support Queue".

4. Set the Owner of the Case (Queue, Specific User).
5. Save and Activate the rule.

Example Scenario

• A customer submits a High Priority case.
• Instead of waiting for manual assignment, Salesforce automatically routes it to the Senior Support Team.

2. Escalation Rules (Ensuring Timely Case Resolution for High-Priority Issues)

Why is it important?

• Escalation Rules automatically reassign unresolved cases after a set period, ensuring high-priority cases are not left unattended.
• Helps maintain Service Level Agreements (SLAs) by escalating overdue cases.

How to Configure Case Escalation Rules

1. Navigate to Setup → Search for Escalation Rules.
2. Click New → Name the rule (e.g., "High Priority Case Escalation").
3. Click New Rule Entry → Define escalation conditions:

• If Case Priority = High AND Response Time > 2 hours, escalate the case.

4. Choose Escalation Actions:

• Reassign the case to a Senior Manager.
• Send an email notification to the Support Supervisor.

5. Save and Activate the rule.

Example Scenario

• A VIP customer submits a High-Priority case.
• If no agent responds within 2 hours, the case is escalated to the support manager and an urgent email alert is sent.

3. Service Level Agreements (SLAs) – Managing Customer Support Commitments

Why is it important?

• SLAs define expected response and resolution times for cases, ensuring customer commitments are met.
• Helps track whether customer support is meeting service expectations.

How to Implement SLAs in Salesforce

1. Set Up Milestones (Response & Resolution Times):

• First Response Time: Example → All High-Priority Cases must be responded to within 1 hour.
• Resolution Time: Example → All cases must be resolved within 24 hours.

2. Use Entitlement Management to track SLAs for each customer.
3. Combine SLAs with Escalation Rules:

• If a milestone is missed, the case automatically escalates.

Example Scenario

• A Platinum customer’s case must be responded to within 1 hour.
• If the support team misses the deadline, the case is escalated to the senior team.

4. Omni-Channel Routing (Smart Case Distribution to Agents in Real-Time)

Why is it important?

• Omni-Channel Routing automatically assigns cases, live chats, and tasks to available agents based on:
  • Agent Skill Set
  • Current Workload
  • Priority Levels
• Ensures even workload distribution and faster customer response times.

How to Configure Omni-Channel

1. Navigate to Setup → Search for Omni-Channel → Enable it.
2. Create a Routing Configuration:

• Skill-Based Routing: Example → Technical issues are routed only to certified engineers.
• Load Balancing: Example → If an agent has 3 active cases, new cases are assigned to another agent.

3. Enable the Omni-Channel Widget in the Service Console.

Example Scenario

• A customer initiates a live chat for technical support.
• Instead of waiting in a queue, Omni-Channel automatically assigns the chat to an available agent with the right skills.

5. Case Merge (Eliminating Duplicate Cases for Cleaner Case Management)

Why is it important?

• Case Merge helps support teams combine duplicate cases from the same customer into a single case, reducing redundancy and improving efficiency.
• Ensures that agents work on one case rather than multiple duplicates.

How to Merge Cases

1. Go to the Case List View.
2. Select multiple similar cases submitted by the same customer.
3. Click "Merge Cases".
4. Choose the Master Case (the primary case to keep).
5. Select which field values to retain.
6. Click Merge.

Example Scenario

• A customer submits 3 separate cases about the same issue.
• Instead of having 3 different agents working on the same problem, the support team merges the cases into one.

Final Summary

Feature	Description	Best Use Cases
Case Assignment Rules	Automatically assigns cases to the right agent/team	Assigning urgent cases to senior support staff
Escalation Rules	Ensures unresolved cases are escalated to the right team	Escalating High-Priority Cases if no response within 2 hours
Service Level Agreements (SLAs)	Tracks response and resolution time commitments	Ensuring Platinum customers get responses in 1 hour
Omni-Channel Routing	Distributes cases, live chats, and tasks based on skills and workload	Assigning technical cases to certified engineers
Case Merge	Combines duplicate cases from the same customer	Merging multiple cases about the same issue