Two things a manager needs from telephony: knowing who receives inbound calls, and giving a team a list to work through.
The rule for inbound
Everybody can make calls by default. Receiving them is narrower.
An inbound call rings only agents who are in the inbound rotation, available, and either within their hub's hours or clocked in.
Each part of that is a separate switch on the person: whether they can make calls at all, whether they are an agent, whether they take inbound, and whether they take outbound. Somebody can be a perfectly active agent whose phone never rings because the inbound flag is off, which is a legitimate configuration and a confusing one to diagnose from the outside.
Agents
A roster of everybody who can take calls, with a column that answers the question people actually ask.
Will this person get the next inbound call, and if not, why not.
Three states. On a call, so not available for another. Ringing, meaning the next inbound call reaches them. Or a plain-language reason they are not in the rotation right now.
That verdict is computed from real things rather than a status somebody set and forgot: duty flags, availability, whether they are clocked in, whether they are on leave, and working hours.
Why this matters
The classic failure in any phone system is inbound calls reaching nobody, with no way to find out why.
The answer is almost always mundane. Somebody is on leave. Somebody never clocked in. Somebody is outside their hours. Somebody set themselves unavailable on Friday and forgot. From the outside all four look identical, which is exactly why the column states which one it is.
Check it before assuming a routing problem. In most cases nothing is broken and the fix takes ten seconds.
Managing an agent
Opening a row gives you their duty flags, their availability and an hours override.
The override is the one to use sparingly. It is right for a genuine exception and wrong as a way of avoiding a conversation about somebody's actual schedule, which is HR's to hold rather than telephony's.
Presence
A live strip of who is available right now.
Useful before promising a customer a call back, and useful for noticing that a shift is thinner than intended while there is still time to do something about it.
Presence or agents, which to look at
They answer different questions and get confused with each other.
Presence tells you who is around right now. It is the one to glance at before promising something to a customer.
Agents tells you why the phone is or is not ringing for a particular person. It is the one to open when somebody says calls are not coming through.
If inbound is quiet and you only check presence, you will see plenty of people available and conclude nothing is wrong. Available and in the inbound rotation are two different things.
Call lists
A list of people to ring, worked through in order.
Making one
Three ways: upload a spreadsheet, paste in manually, or build from a saved segment.
Prefer the segment where it applies. A segment stays current; a pasted list is a snapshot that starts going stale the moment it is made.
Working one
Starting a list opens the preview dialler, which serves the next contact rather than making you choose one.
That removes the decision between calls, which is where the time actually goes in an outbound session. The caller sees who is next, the context, and the call button.
Every call placed from a list is stamped with the list, so progress is real rather than remembered and the activity ties back.
Outcomes decide what happens next
The dialler's outcomes split into two kinds.
Finished with that contact: connected, not interested, or do not call. The contact drops out of the list.
Try again: no answer, voicemail, busy, or callback. The contact requeues, and a callback takes the time you set.
That split is what makes a list finish. Every contact is either resolved or scheduled, and nothing sits in an ambiguous middle where somebody has to decide whether it has been done.
When it stops serving contacts
The dialler tells you why rather than going quiet, and the reasons are worth recognising.
| It says | It means |
|---|---|
| Outside your calling hours | Your department is not in its calling window |
| Outside their local window | The remaining contacts are, in their own time zone |
| Maximum attempts reached | Everybody left has been tried enough times |
| On the do-not-call list | The rest are excluded |
| Nothing queued | The list is finished |
Two of these matter more than the others. Local calling windows mean the dialler respects the recipient's time zone, not yours. And the do-not-call filter sits in the tool rather than in the caller's judgement, so somebody working quickly cannot accidentally ring somebody who opted out.
That is protection, not compliance. Calling rules differ by jurisdiction and by what you are calling about, and the platform enforces what it has been told about.
Running an outbound session well
Short lists. A hundred names is a session; a thousand is a backlog nobody ever feels progress on.
Record every outcome, including the failures. A list where only connections are marked cannot tell you whether it is worth continuing.
Work in blocks. Calling is tiring in a way that is easy to underestimate, and quality drops well before anybody admits it.
Review the list, not the callers. A list producing nothing is usually a bad list rather than a bad team, and the fix is upstream in how it was built.
What is not here
Automatic dialling of many numbers at once. One contact at a time, deliberately.
Call scripts. What to say is not modelled.
Skill or language-based inbound routing. Inbound is based on availability, not on matching a caller to a specialist.
Did this answer your question?
No, ask a person