Q-Director: call routing
Turn call routing on, set the countdown and the notes engineers owe, decide who counts as free and how the Who to try first list is ordered, and manage the sound library.
Last updated 18 days ago
The Call Routing tab of Q-Director Settings holds every number, switch and list behind Who to try first and the call offers that dispatchers send to engineers. Administrators and people with the Q-Director Configuration role use it. Nothing is routed unless a dispatcher selects Send a call: these settings decide how the list is ordered, how long an engineer has to answer and what they owe afterwards.
Before you start. The browser extension must be version 0.27 or later for the people who dispatch and for the engineers who receive. The list reads the phone system, the shift and lunch plan, the appointments in HaloPSA and each engineer's open tickets; where one of those is not connected, the list says so and does not guess. Q-Director Settings explains how to reach the page and its other tabs.
Open the tab
Open Q-Director Settings and select Call Routing in the column of tabs, or go straight to it with the address /qdirector-settings?tab=call-routing. The tab has its own Save changes button at the top right; the page's Save Changes button is hidden here. Defaults puts every value back to its default on the screen, and nothing is kept until you select Save changes. After a save, the page shows what was stored, with every value brought inside its limits, and the card says who changed it last and when, in UTC.
General
Countdown and delivery
The countdown starts when the card appears on the engineer's screen, not when the dispatcher sends it.
Where a call goes next
When an engineer declines or lets it ring out, the call moves to the next person on the list, or comes back to the dispatcher.
Notes and reasons
Only the dispatcher who sent the call, administrators and service desk managers can read a decline reason or a note. The rest of the dispatch team sees neutral words; see the call offer log.
Who to try first
The order comes from four parts, each worked out from 0 to 100 and weighted: whether the person is free right now (the tightest of phone, calendar, lunch and shift wins), how long since their last call, how few open tickets they have, and how well they know the client. The score is never shown to anyone: only the order and the sentence are.
If your PSA cannot be reached when the tab opens, a note under Who to try first says so and the lists show the teams and people QuantumOps already has.
A person who is blocked is still listed, under Cannot take a call now, with the reason. A dispatcher can still name a blocked person after confirming.
Limits
Sound
The sound library
Under Sound library, each row shows the sound's name, whether it is built in or from your library, and its length, with a play button. Add one with Add a sound (MP3, WAV or OGG, up to 1 MB and 10 seconds), give it a Name, and select Add to the library. The library holds up to 20. The file is checked by its contents, not its name. Select the bin icon to delete a sound from the library. If it was the default sound, the default goes back to Ring. The built-in sounds are Ring, Chime, Pulse, Urgent and Soft.
Notices
Where to see what happened
The call offer log lists every call, who it was offered to and what happened. Agent detail and profiles shows each person's offers, accept rate and response time over 30 days to everyone who can open the Agent Performance Hub. Only administrators and service desk managers also see how the other offers ended (declined, timed out, never shown) and the reasons for declining.
Related pages
- Who to try first, and sending a call: what the dispatcher sees.
- Call offers from dispatch: what the engineer sees.
- Q-Director Settings: the other tabs and how saving works.
Was this helpful?
More in Q-Director and AI settings
Q-Director SettingsQ-Director: AI ProcessingQ-Director: sentiment and categorizationQ-Director: triage and routingStill need help? Ask the team