Back to Case Study
AGENT ROUTING & PRESENCE

Presence-aware routing that assigns conversations to the right active agent.

The routing engine prevents conversations from being sent to offline agents by combining heartbeat presence, capacity limits, workload rules, skill tags, priority queues, reassignment logic, and SLA escalation.

Default Queue
3 Waiting
Routing Engine
Presence Check
Capacity Limit
Skill Rule (Support)
SLA Tracker Initiation
Agent Pool
Agent A
Online
4/6
Agent B
Busy
2/3
Agent C
Away
Paused
Agent D
Offline
0/0

Presence State System

Ensuring messages are only routed to agents who are verifiably online and ready to assist.

Online

Accepting chats up to capacity

Busy

Accepting limited priority chats

Away

Temporary unavailable

Offline

No assignment. Session ended

Heartbeat Tracking

The agent panel continuously sends a background heartbeat to the routing engine. If the heartbeat stops (due to network drop, tab closure, or crash), the system automatically transitions the agent to Offline to prevent new customers from being routed to an unreachable agent.

Assignment Engine Workflow

The step-by-step logic that evaluates agent capacity, queues, and skills before assignment.

Inbound Convo
Default Queue
Presence Check
Capacity Check
Routing Rules
Assignment
Ownership Log
SLA Timer

Skill & Branch Logic

Advanced conditional routing rules allow admins to map specific inquiries to specialized teams.

Skill / Subject Matter
Geographic Branch
Language Preference
Customer Priority Tier
Business Hours Overlay
Automatic Escalation Paths
// Rule builder evaluation
IF channel == 'WhatsApp'
AND tag == 'complaint'
AND branch == 'north'
THEN route_to('complaints_team_north')

Queue Management

Segmenting inbound traffic into priority queues for immediate visibility and triage.

Active Queues

Search queues...
Default Triage
Normal
24
Avg Wait: 3m
VIP Priority
Fast
3
Avg Wait: 1m
Complaints
High Volume
8
Avg Wait: 4m
Escalation
Urgent
2
Avg Wait: 2m
Missed / Expired
Clear
0
Avg Wait: --
Reassignment
Pending
5
Avg Wait: 5m

SLA Escalation & Reassignment

Automated safety nets that reassign conversations if an agent fails to respond within the target SLA window.

SLA Active
Target: 5m 00s
Breach Risk
Remaining: 0m 30s
Team Lead Alert
SLA Missed
Reassigned
Escalation Queue
Reassignment History Log
Assigned to Agent A10:00 AM
SLA Breach Warning Triggered10:04 AM
System Reassignment: Escalation Queue
Reason: Non-responsive agent (SLA Timeout)

Operations Control Center

Providing supervisors with the tools to manage load, queues, and shifts manually if needed.

Agent Sessions Overview
Routing Rule Config
Manual Overrides
Shift Scheduling

Routing Efficiency

Daily metrics showing queue performance and assignment accuracy.

Online Agents
32
Avg Queue Wait
45s
Assignments
2,410
Reassigned
18
SLA Risk Count
4
Offline Prevents
142

Need smarter routing for your support team?

We design routing engines that prevent dropped conversations and ensure the right agent gets the right message, every time.