Salesforce Certified Administrator Service and Support Applications

Service and Support Applications Detailed Explanation

This section is foundational for administrators working with the Service Cloud.

Service Cloud

The Service Cloud is designed to manage customer service and support processes, enabling organizations to respond effectively to customer inquiries and issues.

4.1 Case Management

Cases are records of customer requests, issues, or feedback. Managing cases efficiently ensures customer satisfaction and better service outcomes.

1. Create and Assign Customer Support Requests:

   • Case Creation:
     • Cases can be created manually by agents or automatically through channels like email, web forms, or social media.
     • Each case contains:
       • Case Number: Automatically assigned for tracking.
       • Contact Information: The customer who raised the issue.
       • Case Details: Description of the problem.
   • Case Assignment:
     • Automatically assign cases to specific users or queues using assignment rules.
     • Example: Assign all "High Priority" cases to senior agents.

2. Set Case Priorities, Statuses, and Types:

   • Priorities:
     • Used to rank the urgency of cases (e.g., Low, Medium, High).
   • Statuses:
     • Reflect the progress of a case (e.g., New, In Progress, Escalated, Closed).
   • Types:
     • Categorize cases based on the issue type (e.g., Technical Support, Billing Issue, Feature Request).

4.2 Support Queues

Queues are holding areas for cases before they are assigned to agents. They improve organization and ensure no request is missed.

1. Assign Cases to Specific Queues:

   • Cases can be routed to queues based on criteria like:
     • Case Type: Billing issues go to the "Finance" queue.
     • Region: U.S. cases go to the "U.S. Support" queue.
   • Example:
     • A case about "Technical Support" is assigned to the "Tech Support" queue for triage.

2. Configure Automatic Assignment Rules:

   • Assignment rules automatically assign cases to queues or agents.
   • Example:
     • If a case has "High Priority," assign it directly to a senior support agent.
   • Configure in Setup > Assignment Rules > Case Assignment Rules.

4.3 Email-to-Case

This feature converts incoming customer emails into cases, reducing manual data entry.

1. Convert Customer Emails into Cases:

   • When a customer sends an email to a designated address (e.g., [email protected]), Salesforce automatically creates a case.
   • The system captures:
     • Email Subject → Case Subject.
     • Email Body → Case Description.

2. Support Automated Response Templates:

   • Use email templates to acknowledge receipt of customer inquiries.
   • Example:
     • "Thank you for contacting support. Your case number is #12345. We’ll respond shortly."

3. Setup Options:

   • On-Demand Email-to-Case:
     • Emails are processed without the need for local infrastructure.
   • Email-to-Case:
     • Requires installing an agent on your network to process emails.

Knowledge Base

The Knowledge Base is a repository of articles that help agents and customers resolve issues faster by providing useful information.

4.4 Knowledge Articles

Knowledge articles serve as a self-help tool for customers and a resource for agents during case resolution.

1. Create, Categorize, and Publish Articles:

   • Create Articles:
     • Articles can include step-by-step guides, FAQs, or troubleshooting steps.
   • Categorize Articles:
     • Use data categories to group articles (e.g., Product A, Product B).
   • Publish Articles:
     • Draft articles can be reviewed and published to make them accessible to the target audience.

2. Set Access Permissions for Knowledge Content:

   • Permissions control who can view articles:
     • Internal Users: Articles for agents only.
     • External Users: Articles accessible via a customer portal or public site.
   • Use profiles or permission sets to define article access.

Omni-Channel Routing

Omni-Channel Routing ensures customer requests are routed to the right agents, considering their workload and skill set.

4.5 Automatic Assignment

1. Route Customer Requests Based on Workload:

   • Omni-Channel dynamically assigns work to agents who are available and have the right skills.
   • Example:
     • If an agent is handling two cases, Omni-Channel assigns the next case to an agent with a lighter workload.

2. Configuration Options:

   • Presence Status:
     • Agents set their status to "Available" or "Busy" to indicate their readiness to take new cases.
   • Routing Configurations:
     • Prioritize work items based on factors like priority or age.

Key Salesforce Features for Service and Support Applications

Feature	Purpose	Example Use Case
Cases	Track and resolve customer issues.	Managing a case for a billing discrepancy.
Support Queues	Organize and prioritize unassigned cases.	A "Tech Support" queue holds technical issue cases.
Email-to-Case	Convert emails into cases automatically.	A customer’s email about a refund creates a new case.
Knowledge Articles	Provide self-help resources for customers and agents.	Publishing a troubleshooting guide for a common error.
Omni-Channel Routing	Route cases to agents based on availability and workload.	Assigning an escalated case to the next available senior agent.

Summary

The Service and Support Applications section equips you to handle customer service effectively. By mastering Case Management, Knowledge Articles, and Omni-Channel Routing, you can create a streamlined process for resolving customer issues and improving agent productivity.

Service and Support Applications (Additional Content)

1. Case Management

Case Management in Salesforce tracks customer issues and ensures timely resolution. Enhancements like Case Escalation Rules and Case Milestones help enforce service level agreements (SLAs) and improve customer service efficiency.

Case Escalation Rules

• Definition: Escalation rules automatically reassign cases or notify managers when a case is not resolved within a specified time.
• Use Case:
  • A High Priority case remains "New" for more than 2 hours.
  • The case is automatically escalated to a senior support manager.
• Key Features:
  • Time-Based Triggers: Define escalation based on elapsed time.
  • Notification Alerts: Send email or Chatter alerts when cases escalate.
• Configuration Path:
  Setup > Escalation Rules > New Rule
• Example Rule:
  • If Case Priority = "High" and Case Status = "New" for more than 2 hours, escalate to Tier 2 Support.

Case Milestones

• Definition: Milestones define specific service goals that must be met within a Service Contract.
• Use Case:
  • A company guarantees "Urgent cases will receive a response within 30 minutes".
  • A milestone is created to enforce this rule.
• Key Features:
  • Time-Based Tracking: Measure response and resolution times.
  • Entitlement Processes: Combine milestones with entitlements to enforce SLAs.
• Configuration Path:
  Setup > Entitlement Management > Milestones

2. Support Queues

Support Queues improve case management by organizing and prioritizing cases based on category.

Queue-Based Case Assignment

• Definition: Assign cases to specific queues based on case type or priority.
• Use Case:
  • Billing Cases → Sent to Finance Queue.
  • Technical Cases → Sent to Tech Support Queue.
• Key Features:
  • Automatic Routing: Cases automatically enter the correct queue based on rules.
  • Multiple Queue Memberships: Agents can belong to multiple queues.
• Configuration Path:
  Setup > Queues > New Queue

3. Email-to-Case

Email-to-Case allows customers to submit cases via email, which Salesforce automatically converts into Case records.

Email Threading

• Definition: Automatically matches customer email replies to existing cases instead of creating duplicates.
• Use Case:
  • A customer replies to a case email with "Re: Case #1234".
  • Salesforce links the reply to Case #1234 instead of creating a new case.
• Key Features:
  • Threading Logic: Uses Case Number in email subjects for tracking.
  • Prevents Duplicate Cases.
• Configuration Path:
  Setup > Email-to-Case > Enable Email Threading

High-Volume Email Processing

• Definition: Optimizes mass email case handling for large customer support teams.
• Use Case:
  • A company receives 10,000+ emails per day.
  • Email-to-Case automatically processes incoming messages.
• Configuration Path:
  Requires Email-to-Case Agent for Advanced Settings

4. Knowledge Base

The Salesforce Knowledge Base provides searchable articles to help agents and customers resolve issues.

Article Approval Process

• Definition: Before publishing knowledge articles, approval workflows ensure content accuracy.
• Use Case:
  • A support agent writes a troubleshooting guide.
  • A manager reviews and approves the article before publishing.
• Key Features:
  • Multi-Step Approvals: Articles go through review and approval.
  • Prevents Incorrect Information from Being Published.
• Configuration Path:
  Setup > Approval Processes > Knowledge Article Approval

Knowledge Search Recommendations

• Definition: AI-powered Einstein Search recommends articles based on case content.
• Use Case:
  • A customer submits a case with "password reset" in the description.
  • Salesforce suggests a knowledge article on how to reset passwords.
• Configuration Path:
  Requires Einstein Search (Available in Service Cloud)

5. Omni-Channel Routing

Omni-Channel automatically assigns cases to the most available or skilled agents.

Skill-Based Routing

• Definition: Assigns cases based on agent skills rather than random distribution.
• Use Case:
  • A "Technical Issue" case requires Advanced Troubleshooting skills.
  • The case is assigned to an agent with the required skills.
• Key Features:
  • Dynamic Assignment: Matches agent expertise with case requirements.
• Configuration Path:
  Setup > Omni-Channel > Skills-Based Routing

Push-Based Routing

• Definition: Instead of letting agents manually pick cases, Omni-Channel pushes new cases into their workspace.
• Use Case:
  • An agent logs into Salesforce, and a new case automatically appears in their console.
• Key Features:
  • Reduces Case Handling Time.
  • Ensures Even Distribution of workload.
• Configuration Path:
  Setup > Omni-Channel > Routing Configurations

6. Service Contracts & Entitlements

Service Contracts and Entitlements ensure customers receive the level of support they purchased.

Service Contracts

• Definition: Defines support levels and service agreements.
• Use Case:
  • Gold customers receive 24/7 support.
  • Silver customers receive support only during business hours.
• Key Features:
  • Defines Support Tiers (Gold, Silver, Bronze).
  • Links to Entitlements for SLA Enforcement.
• Configuration Path:
  Setup > Service Contracts > New Contract

Entitlements

• Definition: Ensures customers only receive services they are eligible for.
• Use Case:
  • A Basic Support customer cannot request on-site assistance.
• Key Features:
  • Restricts Service Availability based on the customer’s contract.
• Configuration Path:
  Setup > Entitlement Management > New Entitlement

Summary

These additional Service and Support Applications elements help improve customer service efficiency, SLA enforcement, and intelligent case routing.

Key Enhancements

1. Case Escalation & Milestones – Ensure timely case resolution through automation.
2. Support Queues & Queue-Based Assignment – Organize cases by category and priority.
3. Email-to-Case Enhancements – Prevent duplicate cases and optimize high-volume support teams.
4. Knowledge Base & AI Search – Enhance agent productivity with AI-powered article recommendations.
5. Omni-Channel Routing – Distribute cases to the most available and skilled agents automatically.
6. Service Contracts & Entitlements – Define service agreements and restrict support based on customer tiers.