Each customer call becomes a request in the “Tickets” queue: missed — with “High” priority and a callback deadline, answered — with the call's gist as the subject. The dispatcher tracks it by status until the visit.
When you need this:
- A customer couldn't get through — the missed call becomes a request with a callback deadline.
- A third call today — calls join the same request.
- The visit is in five days — the request isn't overdue meanwhile.
- The owner asks which dispatcher falls behind — the report shows each one's first reply and overdue requests.
Where to start: connect telephony, then set the crew's schedule and deadlines.
What request tracking does
- Collects calls, messengers and ad comments into one dispatcher queue.
- Moves a request through statuses — from the call to the site visit and “Solved”.
- Counts deadlines by the crew's schedule and doesn't count the time spent waiting for the visit date.
- Hands the request over to a technician — with a note in Elbuz or by email.
- Merges a customer's repeat calls into one request and shows their history.
- Shows the owner callback speed and overdue requests for each dispatcher.
Which channels to connect
The main channel for a service company is the phone. Calls from the telephony call log reach “Tickets” on their own and appear in the queue within a few minutes:
- Missed incoming call — a new request “Missed call from …” with “High” priority.
- Answered incoming call — a new request with the first reply already counted. If your telephony transcribes calls, the subject is the gist of the conversation from AI: “Boiler doesn't heat after sensor replacement”.
- Your outgoing call — counts as a reply in the customer's request; it doesn't create a new one.
If the customer already has an open request changed in the last 3 days, the call is added to it. An unknown number also becomes a request, and “Create a customer from this contact” in the right panel creates a card. Learn more: answered and missed calls.
What else to connect:
- Messengers and website chat — customers send photos of the fault. Learn more: website chat and messengers.
- Facebook and Instagram comments — people ask about prices under your service ads. Learn more: comments in tickets.
- Website reviews — a bad rating becomes a request with an AI draft reply. Learn more: a negative review as a ticket.
Dispatchers will find it handy to set up their own queue: “My queues” → “New queue”, channel “Call”.
1
Calls queue2
Missed call ticket3
Overdue SLA chip- The Calls queue under My queues shows only tickets that came in by phone.
- A missed call becomes a ticket with the High priority chip and a first-reply deadline.
- The red SLA chip states in words how long the deadline has been overdue.
How to take a request from the call to the site visit
- Start
- State
- End
- The system creates a request from the missed call and assigns it to a dispatcher by the assignment rules.
- The dispatcher calls back. The outgoing call counts as a reply: the status becomes “Open”.
- The dispatcher arranges the visit, writes a note with the date, the address and the technician's
@username, adds thevisittag and sets the status to “Pending”. - The technician writes a note about the completed work in the same request after the visit.
- The dispatcher sets “Solved”. After 4 days with no new messages, the request closes on its own.
A request from a call has no “Reply” mode: you call the customer back or write with “Email to …” if the card has an email address. Set the status after the conversation — otherwise the resolution deadline keeps running. Learn more: “Email to …”.
Why “Pending” until the visit. In this status the resolution deadline is paused, and the request doesn't sit in “My open”. “On hold” keeps the request in the queue, but the deadline keeps running — use it while waiting for a spare part, when it matters not to forget. Learn more: how statuses affect deadlines.
1
Hint for tickets created from a call2
Email to the customer3
Status: Open- Hint: call the customer back or write to them by email; here you can leave a note and set the status.
- The Email to... switch appears because the customer card has an email address.
- The status chip shows the ticket is Open.
Which deadlines fit the crew's schedule
Deadlines are set in business minutes on the “Hours & SLA” tab of the support settings. Set the crew's schedule: if it works Mon–Sat 08:00–18:00, a business day is 600 minutes. Then:
| Priority | First reply | Next reply | Resolution | Used for |
|---|---|---|---|---|
| Urgent | 15 | 30 | 600 (same day) | emergency: a leak, sparks, no heating — you set it manually |
| High | 30 | 60 | 1800 (3 days) | missed call — set automatically |
| Normal | 120 | 240 | 3000 (5 days) | a regular repair or installation request |
| Low | 240 | 600 | 6000 (10 days) | scheduled maintenance, suggestions |
The first reply is the dispatcher's callback; it doesn't depend on the crew's queue. If spare parts take long to arrive, increase “Resolution”, not the first reply. Learn more: support desk SLA.
How to hand a request over to a technician
- The technician can sign in to Elbuz — mention them in a note with
@usernameor make them the assignee. Their department needs access to the “Tickets” window. - The technician has no sign-in but has email — “⋯” → “Write to a supplier / warehouse”: the technician's address goes in “To (email)”, the request details in the text. Their reply arrives in the same request.
The customer sees neither notes nor emails with the technician. “Tickets” has no visit calendar: keep the date in a note and a tag, and visits as tasks in the organizer. Learn more: how to bring in a colleague with a note.
What happens when a customer calls again
| When they call | What happens |
|---|---|
| The request is open and changed within 3 days | the call is added to it; “Pending” or “On hold” becomes “Open” |
| The request hasn't been touched for over 3 days | a new request |
| After “Solved” or “Closed” | a new request; an email or chat message in the same thread after “Solved” reopens the old one |
So the day before the visit, leave a reminder note in the request: it extends the 3-day window. The history is in the right panel, “Other tickets of the customer”. If the new call is about the same fault, merge the requests. Learn more: how to merge two tickets.
1
Other tickets of the customer2
Earlier closed ticket with its date- Other tickets of the customer — earlier requests from the same person, so the agent sees the history before replying.
- An earlier ticket with its status (Closed) and date; a click opens it.
Which AI features a service company should turn on
- Call summary — if your telephony transcribes calls, AI writes a short summary under the call and in the request subject. The dispatcher schedules visits without listening to recordings.
- AI draft for messengers and email — a reply from your knowledge base: prices, schedule, warranty terms. The dispatcher sends it. Learn more: AI draft reply.
- AutoQA — AI rates closed conversations, calls included, and shows the worst ones. Learn more: quality control.
Autonomous support is off by default. A service company doesn't need its order actions and parcel notifications — keep them off. Turn on messenger auto-replies in “Test” first to see what AI would write. Learn more: auto-replies in chats.
What the owner should check in reports
- “First reply” — the median time to a callback, email or message.
- “SLA met” — a low figure in a service company usually means dispatchers don't set the status after a conversation, or the resolution deadline is shorter than the visit queue.
- By channel — how many requests came by phone and how many from messengers.
- By assignee — first reply and overdue requests for each dispatcher.
Learn more: support desk reports.
1
First reply2
SLA met- First reply — median time to the first answer, calendar time from ticket creation.
- SLA met — share of tickets within SLA, with the number of breached ones next to it.
Scenarios
Missed call — site visit in five days
What to do. Call back, arrange the visit, set “Pending”. What you get. The first reply is done, and the 5 days of waiting aren't added to the resolution deadline: after the request returns to “Open”, almost the whole deadline is left for resolution.
Emergency call
What to do. After the conversation, set the request priority to “Urgent”. What you get. Deadlines are recalculated right away: resolution is due the same business day, and the request is at the top of the queue sorted by “Nearest deadline”.
Waiting for a spare part
What to do. Set “On hold” and add a note that the part is ordered. What you get. The request stays in your queue. The resolution deadline keeps running, so a week of waiting lands in “SLA breached” if the resolution deadline is shorter.
Warranty repeat call
What to do. A new request after “Solved” is assigned by the general rule. Hand it over manually to the technician who did the repair and mention them in a note. What you get. The technician sees the history in “Other tickets of the customer”.
FAQ
We called back from a personal mobile. Will the reply count?
No. Elbuz only sees calls from the call log of the telephony connected to Elbuz. Set the status manually and leave a note.
How do I make emergency calls get “Urgent” right away?
A request from a call gets “High” only when it's missed, otherwise “Normal”. The dispatcher identifies an emergency from the conversation. An email about an emergency can get high priority right away from AI email analysis.
Does the customer see the note with the address and the technician's name?
No. An internal note is visible only to employees. Text reaches the customer only from the “Reply” mode or “Email to …”.
Will the customer get a request to rate the work after a call?
If customer ratings are on, the rating request for a request from a call goes by email, and only when the card has an email address. Learn more: customer ratings.
Will AI answer a new customer on Viber about how much a repair costs on its own?
“Tickets” auto-replies work only in chats linked to a customer. Price and advice questions from a new visitor are still handled by the chat widget's AI assistant. Learn more: what happens when a customer writes in the chat.
Where it is and who has access
- Menu
- Directories → Contacts → Tickets; Organizer → Tickets
- Support settings
- the window's gear icon → “Support desk settings”
- Access rights
- “Tickets” — “Management”, “Sales”, “Customer service”; settings — “Management”
- Prepare
- connected telephony, dispatchers in the “Customer service” department
Related topics
- If you need the big picture of “Tickets” — customer tickets: where to start.
- If calls don't reach the call log yet — telephony.
- If you're setting up assignment between dispatchers — ticket assignment.
- If you handle deals and service renewals — services: deals, payment, renewal.
