Help Desk Tickets in Call: Follow Up Callers Who Asked for a Person
How to use Call's ticket list to follow up every caller who asked for a person or a call back: statuses, assignment, notes, callbacks and a daily routine.
Every phone line produces requests that cannot be finished on the call itself: a caller wants a person who is not free, asks to be called back, or leaves a message. If those requests live in voicemail or in somebody's notebook, some will be lost. A ticket list solves that by giving each request an owner, a status and a place for notes.

This guide explains how tickets work in Call, how to run them day to day and how to write the replies that go with them. It pairs well with Using Callbacks and Voicemail in Your IVR, which covers how the requests get created in the first place.
What a ticket is and when one appears
In Call, the ticket list shows callers who asked for a person. A request appears when an AI agent could not or should not finish the call, when nobody answered, or when the caller asked to be called back. Each row shows the result of the call, such as asked for a person or nobody answered, what the caller said, and a mark if they asked for a callback. For a callback request it also shows a summary, the preferred time and the language.
The four counters at the top of the list
- OpenRequests nobody has picked up yet.
- In progressRequests someone owns and is working on.
- ResolvedRequests that are finished.
- Needs attentionRequests that still need a decision, such as an unassigned or old one.
Treat these four numbers as the health check of your phone service. Open and Needs attention should be small at the end of every day.
Handling one request from start to finish
The life of a ticket
- ReadOpen the request and read what the caller said and, if there is one, the call summary.
- Take or assignPress Take it to make it yours, or assign a colleague. The status moves to In progress.
- NoteWrite what you know, what you tried and what you promised.
- Call backCall from the line, using your own phone or the line's AI agent, or add the request to a callback queue for later.
- ResolveMark it resolved when the caller's problem is dealt with. Reopen it if they ring again.
You can open the whole conversation from the ticket to see exactly what the caller said before they were handed off, and open their contact record to see earlier calls. Reading the conversation before you phone back avoids the most annoying thing a callback can do: asking the caller to repeat everything.
Notes that help the next person
- Write facts, not feelings: what was asked, what was promised, by when.
- Record the outcome in one sentence so a colleague can pick it up without listening to the call.
- If you leave a voicemail or the line is busy, note the time of each attempt.
- Keep notes short; the call summary already holds the detail.
Who should pick up the call in the first place
Tickets exist because someone was not reachable. It helps to check, line by line, who would ring right now if a caller asked for a person. Call shows, for each line, whether it is within business hours, whether a call would be put through and which members and numbers would ring at once, each marked as in the browser, by phone or cannot be reached. Everyone chosen rings together; there is no rotation or priority built in, so the quality of your answer depends on choosing the right people.
A daily routine that keeps the list short
A ticket list stays healthy when the habit is small and fixed. Choose times rather than saying "when we can".
A simple daily routine
- Start of day: read Needs attention first, then Open
- Assign every request that has no owner
- Return callbacks that have a preferred time first
- Before lunch: update notes on anything still in progress
- End of day: nothing left unassigned; resolved items have a one-line outcome
- Weekly: look at the oldest unresolved ticket and ask why it is old
Callback wording that works
The words you use on a callback matter as much as how fast you make it. Open with who you are and why you are calling: "This is Sam from the clinic, returning your call from this morning." Confirm you are speaking to the right person before you share anything private. State what you can do, and end with what happens next.
Write two or three message templates for the cases that repeat: a first attempt, a voicemail when nobody answers, and a closing note. Message templates in Call shows where to keep them. Do not promise things a person has not agreed to, such as a firm time for an appointment, unless the person on the call can confirm it.
Ticket list vs a shared mailbox of voicemails
| Ticket list | Shared voicemail box | |
|---|---|---|
| Owner | Visible on every request | Unclear who listened |
| Status | Open, in progress, resolved | Heard or not heard |
| Context | Summary and full conversation | Audio only |
| Follow-up | Call back from the request | Look up the number and dial |
| Reporting | Counts by status | Hard to count |
Common problems and how to avoid them
Most ticket lists fail in the same few ways. The first is the ownerless ticket: everyone assumes someone else has it. The fix is a rule that nothing stays unassigned overnight. The second is the stale ticket, where a request sits in progress for days because the person who took it was moved onto something else. A weekly look at the oldest item catches this.
The third is the duplicate. A caller who has not heard back will ring again, and now there are two requests for one person. Before you create or assign anything new, check the contact record for earlier calls, and resolve the older ticket with a note pointing to the newer one. The fourth is the vague closure, a ticket marked resolved with no outcome. Insist on one sentence saying what was done.
- Assign by rule, for example by topic or by day, so nobody has to decide each time.
- Agree a target for how quickly a callback should happen and write it where the team can see it.
- Keep your callers informed honestly: if the target is the same day, do not promise within the hour.
- Review a handful of resolved tickets each month for quality, the way you would review calls.
Measuring how well you follow up
Count how many requests arrive, how many are resolved the same day and how old the oldest open one is. Those three figures show whether you have enough people for the volume. If you want to go further, callback completion rate explains a common measure, and repeat call rate shows whether callers have to chase you.
If the same question keeps creating tickets, fix the cause: add the answer to the knowledge base, change the greeting or add a menu option. A good ticket list should slowly shrink the reasons it exists.
Doing it in Call
In Call the list lives under Help desk, in Tickets. Easy mode calls the page ticket assignment. Choose a status filter, open a request with Details, take it or assign it, write a note, then call back through your line or add it to the callback queue. Voicemail left on a queue can be turned into a callback entry as well. Only managers can change who calls are put through to. SMS is off unless an operator enables it, so plan your callbacks around calls rather than texts.
Frequently asked questions
When does a ticket get created?
When a caller asks for a person or a call back, or when a call could not be handed to anyone. The list shows the result of the call and what the caller said.
Can I assign a ticket to someone else?
Yes. You can take a ticket yourself or assign it to a member, then add a note. Resolve it when it is done or reopen it if the caller rings again.
What is the difference between In progress and Needs attention?
In progress means someone owns the request. Needs attention is for requests that still require a decision or action, so it is the first thing to read each morning.
Can I see what the caller said before I call back?
Yes. Open the conversation from the ticket to read both sides of the call, and the contact record to see earlier history.
Does Call text the caller about their ticket?
No. SMS is off unless an operator enables it, so follow-up is by phone call or by whatever channel your team uses outside Call.
How many tickets are too many?
There is no universal number. Watch the trend: if Open and Needs attention keep growing, you need more people on the line or fewer reasons for callers to ask for a person.