Use Claude or Codex to review routing rules, owner capacity, SLA risk, and escalation paths before Sanka assigns work across teams.
Last updated: May 16, 2026
This guide shows how to use Sanka smart routing to assign the right owner before work stalls. Start by asking Claude or Codex to review the routing context and recommend a route, then confirm the rule before Sanka assigns or escalates work.
Claude/Codex
Review this incoming deal desk request and recommend a routing decision. Use region, product, deal amount, owner capacity, current SLA, out-of-office status, and escalation rules. Do not reassign it yet.
Preparing routing recommendationI recommended a routing path with primary owner, backup owner, SLA deadline, and escalation reason. Please review before assigning.
Ask for another routing check...
Before you start
Check that you have the following ready.
The records you want to route are available in Sanka, HubSpot, or Salesforce
Owner teams, roles, territories, capacities, and backup owners are defined
SLA rules and escalation paths are documented
Out-of-office or availability information is maintained
You have permission to update owners, tasks, approvals, and workflow assignments
Ask AI to recommend the route
Ask Claude or Codex to explain the routing decision before assigning work. This helps managers understand why a lead, deal, approval, ticket, invoice, or project moved to a specific person.
Sample prompt
/sanka Recommend the best owner for this record. Use territory, account tier, product, deal amount, workload, availability, SLA, and escalation rules. Explain the recommendation and keep the assignment pending.
Review:
Which rule matched the record
Why the recommended owner is eligible
Whether capacity or availability changes the assignment
SLA deadline and escalation path
Backup owner if the primary owner does not act
Apply routing rules
After review, apply the routing rule. For high-volume work, you can use the same logic for inbound leads, quote approvals, deal desk requests, onboarding kickoff, billing review, or support escalation.
Sample prompt
/sanka Apply the approved routing rule to these pending records. Show the assigned owner, backup owner, SLA deadline, and reason for each assignment before updating.
Common routing patterns include:
Inbound leads by territory, segment, account tier, and capacity
Quote approvals by discount, margin, product, or amount
Deal desk requests by legal, finance, delivery, or security review
Customer onboarding by region, language, product, and workload
SLA escalation when the owner does not act in time
Checkpoints
Use Sanka logs and tables to review the rule, assigned owner, backup owner, SLA deadline, and escalation history.
Search Sanka...
Review smart routing activity
Logs
Search logsAll actionsAll dates
ID / ActionDateTarget / ItemChangeActor
4SLA escalation prepared2026/05/12 16:50Acme security review / TaskPrepared backup owner because SLA is near breachClaude / Codex
3Owner assigned2026/05/12 16:20Acme security review / TaskAssigned to legal owner by product and amount ruleSanka routing
