Skip to content
Tutorials Center
My learning

Topics

Lesson 35 of 36 ยท Projects and Practice

Project: Set Up a Support Desk in Salesforce

Configure a Salesforce support desk: case fields and statuses, queues and assignment, escalation by service level, an agent console, an approval-style refund flow and service dashboards.

This project turns a basic Salesforce org into a working support desk for a fictional company, Brightfield Energy, which sells home solar kits. Customers write by email and web form; the support team of 12 must answer within a target time, escalate stalled cases, approve refunds, and show managers how the desk performs. You will go through the requirements, the configuration (objects, fields, queues, automation, pages, reports) and test the logic with labelled JavaScript stand-ins. Nothing here is real Salesforce output; the product cannot run on this site.

Requirements

  1. Cases arrive from Email-to-Case and Web-to-Case; each gets a priority and lands in the right queue.
  2. Service levels: Urgent first response in 1 hour, High in 4 hours, Normal in 1 business day.
  3. Cases that miss the target escalate to the team lead.
  4. Agents work in a console with the case, customer history, a knowledge panel and a refund button.
  5. Refunds over 200 need a manager's approval.
  6. Managers track backlog, response times and satisfaction on a dashboard.

Step 1: case model

Use the standard Case object. Configure (Setup, Object Manager, Case):

  • Status values: New, Working, Waiting on Customer, Escalated, Closed. Mark Closed as a closed status.
  • Priority values: Urgent, High, Normal, Low.
  • Case Origin: Email, Web, Phone, Chat.
  • Custom fields: Product__c (picklist), Refund_Amount__c (currency), Refund_Status__c (picklist: None, Pending, Approved, Rejected), First_Response_At__c (date/time), Customer_Tier__c (formula from the account), Escalated__c (checkbox).
  • Record types if different case types need different statuses or layouts: Technical, Billing.
  • Page layouts with required fields by status and a compact layout that shows number, subject, account, priority and status.

Add a validation rule so that closing needs a reason:

TEXT
AND(ISPICKVAL(Status, "Closed"), ISBLANK(TEXT(Reason)))

Step 2: queues, assignment and email-to-case

Create queues (Setup, Queues): Tier 1 Support, Billing, Escalations, each with members and an email address. Create a case assignment rule with ordered entries (Priority = Urgent goes to Escalations; Record Type = Billing goes to Billing; everything else goes to Tier 1 Support). Configure Email-to-Case (Setup, Email-to-Case) with routing addresses (support@, billing@) that set the record type, priority and queue, and Web-to-Case with a generated HTML form for the website; add spam protection (reCAPTCHA) for web forms.

Add auto-response rules so customers get an immediate acknowledgement with the case number and expected response time. Use email templates with merge fields, and make sure Case Thread IDs are included in outgoing mail, so replies attach to the right case.

JS Stand-in: case routing

Press Run (or Ctrl + Enter) to see the console output here.

No output.

Step 3: service levels with entitlements and milestones

Salesforce Entitlement Management models service levels: an entitlement process defines milestones (First Response, Resolution) with a time trigger, a business hours calendar and actions at warning and violation times (send an email, update a field, create a task). Priority-based timing is done with separate entitlement processes or with a milestone's criteria (Priority = Urgent: 1 hour). Enable it in Setup (Entitlement Settings), add the Milestone Tracker to the case page, and assign entitlements to accounts or contracts.

If your edition lacks Entitlement Management, approximate it with a scheduled flow or a record-triggered flow with a Wait element that checks First_Response_At__c after the target time has passed, and then escalates. The stand-in below calculates deadlines with business hours so you can test the rule before you build it.

JS Stand-in: first-response deadlines in business hours

Press Run (or Ctrl + Enter) to see the console output here.

No output.

Step 4: escalation flow

A schedule-triggered flow (every 15 minutes) or milestone action finds open cases where First_Response_At__c is empty and the deadline has passed, sets Escalated__c = true and Status = Escalated, reassigns the case to the Escalations queue (or the team lead) and posts to Chatter or sends an email. Use a collection and a single Update after the loop (Loops, collections and limits), and a fault path that logs failures. A record-triggered flow (before-save) stamps First_Response_At__c when the first outbound email is logged or the status changes from New to Working.

Step 5: refund approval

Refunds above 200 need approval. A modern design uses a screen flow launched by a quick action on the case: the agent enters the refund amount and reason; a Decision checks the amount; below 200, the flow updates Refund_Status__c = Approved and creates a task for finance; above 200, it sets Pending and submits for approval (the Submit for Approval action) to the manager. An approval process (Setup, Approval Processes) defines entry criteria, approvers (the manager via the Manager field, or a queue), email templates, and final actions (field updates to Approved or Rejected, an email to the agent). Record locking during approval prevents edits.

Salesforce is developing newer approval tooling in Flow (Flow Orchestration and approval steps), but the classic approval process is still widely used. The design principles are the same: clear entry criteria, a named approver, a time limit and a final action.

JS Stand-in: refund decision logic

Press Run (or Ctrl + Enter) to see the console output here.

No output.

Step 6: agent workspace

Create a Service Console Lightning app (console navigation) with: the Case record page (Highlights panel, Path for status, Milestones, Knowledge sidebar, Related Lists for emails, activities and the customer's other cases), utility items (History, Open CTI softphone if used, Macros to automate repeat steps), and quick actions (Email, Log a Call, Refund, Close Case). Turn on Knowledge and let agents attach articles to cases. Use a list view of "My open cases" and "Escalations queue", and set Omni-Channel routing if you need work pushed to available agents. Build and activate the pages as in Lightning apps, App Builder and pages.

Step 7: reports and dashboard

Reports: Open cases by queue and priority (summary), Average first response time (row-level formula First_Response_At__c - CreatedDate), Cases closed per agent per week (matrix), SLA breaches (filter Escalated__c = true), and a customer satisfaction report if you collect a survey score. Put them on a Support Manager dashboard with metrics for current backlog, a line chart for cases per day, and a table of oldest open cases. Choose the running user carefully (Dashboards and components), and schedule a refresh at 07:00.

JS Stand-in: support KPIs

Press Run (or Ctrl + Enter) to see the console output here.

No output.

Test plan and release

  1. Unit tests in a sandbox: each route, each priority, each approval path; run the flows in Debug.
  2. Bulk test: load 200 cases with the Data Loader (Importing data and the Data Loader).
  3. Permission test: an agent, a team lead, a manager; make sure agents cannot edit Refund_Status__c directly (field-level security) and only the flow or approval does.
  4. UAT with three real agents for a week; collect feedback.
  5. Deploy with a validated change set; do manual steps (queues, entitlement process activation, email routing addresses, Email-to-Case verification) from a checklist.
  6. After go-live, review the dashboard weekly and adjust thresholds.

Check your understanding

Quick check ยท 4 questions

of 4 answered You scored / 4 ยท perfect!

  1. 1. Which feature models first-response and resolution targets with warning and violation actions?

    Entitlement processes use milestones with time triggers and actions.
  2. 2. A refund of 350 is requested. What should happen in the design above?

    Amounts over the 200 limit set Pending and go through the approval process.
  3. 3. Why include Case Thread IDs in outgoing emails?

    The thread ID lets Email-to-Case match a reply to its case.
  4. 4. How do you stop agents from editing the refund status directly?

    Real protection comes from field-level security, not page visibility.

Summary

  • A support desk needs a case model, queues, routing, auto-responses, service-level targets, escalation, approvals, a console and dashboards.
  • Test the rules (routing, deadlines, refund limits) before you build; the stand-ins show how.
  • Use field-level security, not page visibility, to protect sensitive fields.
  • Test in a sandbox with bulk data and different users, then deploy with a checklist.

Next: Admin certification practice