Customer Support and Voice AI
AI receptionist for small business: calls, bookings and handoffs
What an AI receptionist does on a real call, the rules that apply, a sample greeting and a pass/fail checklist to launch one safely.
Support Operations
AI Ticket Routing for Salesforce Service Cloud
New Service Cloud cases reach the right queue or owner, weighed by what customers wrote and the support they are entitled to.
Service Cloud assignment rules see fields, not meaning, and they rarely weigh what support a customer is entitled to. This workflow reads each new case, the contact record and the account's entitlement, then assigns the case to the right queue or owner. It sets the agreed case fields and adds an internal comment explaining why, so supervisors can trust and check every assignment.
- Cases routed by content, contact and entitlement
- Premium customers reach the queue they are entitled to
- An internal comment explains every assignment
$4,400
20–30 working days
Optional maintenance $249/mo
What it is
AI Ticket Routing for Salesforce Service Cloud reads each new case and assigns it to the right queue or owner, based on what the customer wrote, the contact record and the entitlement the account holds. It sets the agreed case fields, adds an internal comment with the reason, and runs in the background.
Why businesses buy it
When a premium customer's case lands in the general queue, you risk breaking the service level they pay for, and nobody notices until they complain. Manual triage in Service Cloud is slow and depends on who is on shift. After launch, each case reaches the right queue or owner as it arrives, weighed by what the customer wrote and the entitlement they hold. The Scope Card sets the queues, case fields and fallback rules before you order, so your Salesforce admin can approve every write.
Problems this solves
Cases land in a catch-all queue regardless of the customer's entitlement
Each new case is assigned to the right queue or owner. The workflow weighs what the customer wrote, the contact record and the entitlement the account holds.
Assignment rules grow complex and still misroute cases
One background workflow with an AI decision step reads the case content, rather than relying only on field values. It sets the agreed case fields as part of each assignment.
Case owners cannot see why a case reached them
An internal comment on the case records the reason for the routing choice. Service managers can review those comments and tune the routing rules inside Salesforce whenever a pattern looks wrong.
A good fit if
Cases from email and web forms land in one queue, and a supervisor reassigns them by hand every morning.
Your case assignment rules rely on a few fields and keywords, and misroute whenever a customer describes the problem differently.
Customers on different support entitlements should reach different queues, but today's routing ignores the entitlement.
Your Salesforce admin can set up a connected app with a Service Cloud user and give thirty minutes to a setup call.
Not the right fit if
You want cases answered from your knowledge articles, not just routed. See AI Customer Support Agent for Salesforce Service Cloud.
You need topic, urgency and sentiment tags across cases for reporting. See AI Ticket Classification.
Your concern is spotting cases that must go up a tier. See AI Escalation Agent.
It is the sales records in Salesforce that go stale, not cases. See AI CRM Assistant for Salesforce.
How it works
- Queues, owners, skills and entitlement levels are mapped with your support lead, together with the kinds of case that belong to each.
- On a thirty-minute call your Salesforce admin agrees which case fields the router may set, such as owner or queue, type, reason and priority, and how it fits your assignment rules.
- Each new case is read with its contact and the entitlement behind it, so the support level shapes the route alongside the content.
- One AI routing decision sets the queue or owner and the agreed fields on the case.
- An internal case comment records the reason. Cases that fit no route go to a triage queue you name.
- Twenty test runs on past cases, in a sandbox or on test records, check every route before launch.
What you provide within 72 hours
Your portal lists these the moment you order. Delivery starts the working day after everything is in and your access is checked.
- A Salesforce connected app with a Service Cloud user, set up by your admin.
- Your Salesforce admin for the thirty-minute mapping call.
- A description or recording of how cases are assigned today, including current assignment rules.
- Your queues, entitlement levels, priority rules and support hours.
- Five to ten real cases showing typical and difficult routing decisions.
- The person who gets alerts and errors, plus access to any second system.
- One decision-maker who approves queue and entitlement rules.
- An API key for your own AI model account (for example OpenAI or Google Gemini), created for this build with a spending limit.
The 72-hour rule. Send everything on your checklist, including access, within 72 hours of ordering so your build starts on time.
Timeline
Start
Intake verified; Salesforce admin call booked.
Weeks 1–2
Queue, entitlement and field mapping documented; workflow built.
Week 3
Connected app and second system linked; comments tested.
Weeks 3–4
Twenty test runs on past cases in a sandbox or test records.
Week 4
Review with your support lead and admin; two rounds of changes.
Go-live
Routing new cases; recorded 45-minute handoff; support starts.
| Option | Delivery time | Price |
|---|---|---|
| Standard | 20–30 working days | $4,400 |
| Express | 15–25 working days | $5,150 |
| Rush | 10–20 working days | $5,950 |
What you receive at handover
- The routing workflow running in the background on your Salesforce Service Cloud org
- Two-way Service Cloud connection with documented field mapping, plus up to one more system
- One workflow of up to twelve steps, including entitlement-aware routing
- Access through user invites or keys you control, with no keys sent by email
- Test report from 20 test runs on sandbox or sample records
- Admin guide, recorded 45-minute handoff session and 30 days of post-launch support
Expected benefits and how to measure them
- Cases can reach a queue that matches the customer's entitlement.
- Helps reduce the time cases spend waiting in a catch-all queue.
- Internal comments give managers a clear basis for tuning routing.
- Time to case assignment
- Build a Salesforce report on time from case creation to owner assignment. Compare four weeks before and after launch.
- Case ownership changes
- Use case history to count owner changes per case. Compare the month before and after launch.
- Entitlement milestone breaches
- Compare missed first-response milestones for the month before and after launch.
Before you start: Save a Salesforce report of assignment time, owner changes and milestone breaches for the month before work begins.
These are things to track, not promised results. Outcomes depend on your data, your team and your market.
Running costs
The build is paid once. Running it costs roughly $20 to $100 a month for the automation platform and AI model usage, billed in your own accounts and driven by case volume. Your Salesforce licenses remain separate and unchanged.
Usage during the test runs is billed to you as well.
Ask about running costsCustom requirements
Custom objects, fields outside the mapping, routing across several business units with separate rules, or a third system need a written Change Quote. Put it in a checkout note and expect the quote.
Request a custom versionKeep it running
Monthly maintenance covers monitoring, fixes, updates, a monthly health report and change hours for a new queue, a new entitlement level or revised priority rules. It starts after the post-launch support period, bills monthly and can be cancelled any month.
$249/mo (the minimum fee, includes 2 change hours)
Optional. Starts after the post-launch support period. Cancel any month.
How maintenance worksHow this compares
| Do it yourself with a SaaS tool | Hire a custom agency | Upmark Labs | |
|---|---|---|---|
| Price | Routing add-ons bill per user per month | A Salesforce consultancy quotes per engagement | Ours is one fixed price, shown on this page before you buy |
| Entitlements | Often ignored by content rules | Built if scoped | Ours weighs the entitlement alongside the content |
| Explanation | The case just changes owner | Depends on the build | Ours adds an internal comment with the reason |
| Delivery | Install is quick; rules are on your admin | Set per project | Ours has a fixed delivery time shown before you buy, with faster options |
Questions about this product
Does AI Ticket Routing for Salesforce Service Cloud work with our case assignment rules?
Yes. At intake we review your current assignment rules and agree whether the router replaces them for new cases or runs after them for the cases they leave unassigned. Either way only one of them decides each case, so owners never flip back and forth.
How does the Service Cloud router use entitlements?
It reads the entitlement linked to the case's account or contact and treats the support level as part of the route. If your map says premium customers go to a priority queue, an entitled customer's case lands there even when the wording looks routine. Entitlements themselves are never changed.
Which case fields can the Service Cloud router set?
Owner or queue, type, reason, priority and any other case fields named in the mapping, plus an internal comment with the reason. Fields outside the mapping, custom objects and your Service Cloud configuration are left alone. Your admin can review exactly what the Service Cloud user can reach.
Why does the Service Cloud routing edition cost more than the helpdesk editions?
Because the Salesforce Service Cloud connection carries a larger fixed uplift in our pricing than most helpdesk connections, reflecting the extra mapping and permission work. The scope itself matches the other routing editions: one workflow of up to twelve steps, twenty test runs, two rounds of changes and a recorded handoff.
What does Service Cloud routing cost with express or rush delivery?
One fixed price covers the whole build and is shown on this page before you buy, with express and rush delivery listed beside it at a set extra cost. Running costs of roughly $20 to $100 a month go directly to your automation platform and AI model providers.
Where do the Service Cloud routing test runs happen?
In a Salesforce sandbox if you have one, using copies of real cases, or on clearly marked test records otherwise. The twenty runs cover your common case types and a few awkward ones from the samples you send. You see the results and approve them before live cases are routed.
Guides on this topic
All guides Send each case to the queue its customer is entitled to.
Order the Service Cloud edition and new cases are routed by content and entitlement to the right queue or owner, with an internal comment showing why.
Works well with
Support Operations
AI Ticket Classification
Tags incoming tickets by topic, product, urgency and sentiment.
Support Operations
AI Escalation Agent
Detects tickets that need escalation and packages full context for the next tier.
Support Operations
AI Support Supervisor
Oversees AI and human support queues, SLAs and quality in one view.