Elbuz gives every new ticket to an employee of its department and notifies them, so you don't hand out emails and chats manually.
When you need this:
- Tickets sit unowned — a new ticket goes to the least loaded or next operator.
- People drown at peak times — tickets over the limit wait for the first person who frees up.
- An operator has gone home — an unanswered new ticket moves to someone on shift.
- The customer is used to their manager — that manager gets their ticket.
Where to start: the gear in the “Tickets” window → “Support desk settings” → the “Assignment” tab.
What assignment can do
- Three options — manual, round robin, or the least loaded in the department.
- Assignment within a department — sales emails go to sales, everything else to customer service.
- Open ticket limit — above it, a person gets no new tickets.
- Only to people on shift — plus handover of a “New” ticket if the assignee left without replying.
- Customer's manager first — a ticket from a pinned customer goes to their manager.
- VIPs first — “High” priority and a shorter response deadline.
- Notifications — the assignee learns about the assignment right away.
Who gets a new ticket
The “Assignment” tab has the “Distribution of new tickets” block with three options. The default is “Least loaded in the department”. If you saved the settings before, the option you chose then stays: app updates don't change it.
| Option | What happens to a new ticket | When to choose it |
|---|---|---|
| “Manual — staff take them (“Unassigned”)” | The ticket stays in the “Unassigned” queue until someone clicks “Take it” or assigns a colleague. Nobody gets a notification about the new ticket. Exception: customers with an account manager, if “First — to the customer's account manager” is on. | One or two operators who watch the queue all day anyway; or you first want to see how many tickets come in. |
| “Round robin within the department” | The ticket goes to the next employee of the department on the list, in a circle. The app remembers who got the last one, separately for each department. How many tickets a person already has doesn't count. | Operators have similar experience, and tickets are roughly the same size. |
| “Least loaded in the department” | The ticket goes to whoever has the fewest open tickets. If several people tie, it goes to the one added to the app earlier. | Tickets can take long: one operator is stuck on three hard ones while another is free. |
Workload means tickets in the “New”, “Open” and “On hold” statuses. “Pending” doesn't count as workload: an operator with twenty tickets waiting for the customer's reply is free as far as the app is concerned.
Only live tickets are handed out: “New” and “Open” tickets without an assignee where the customer wrote within the last 3 days, up to 50 per pass. Emails the app collected from mail history on first launch stay in “Unassigned” and don't flood people with old questions. If such a customer writes again, the ticket is assigned automatically.
- Start or end
- Action or result
- Decision: the path depends on the answer
- Key step
How often assignment runs. Every time tickets are collected: in the background every 5 minutes, when the “Tickets” window opens, every minute while anyone has the window open, and after every reply to a customer. On a working day that's about once a minute; 5 minutes when nobody has opened the window.
Who learns about the assignment
The assignee gets the “Ticket #N is assigned to you” notification with the subject and a button that opens the ticket. The same notification comes with any assignment to someone else: manual, bulk action, macro or flow. For a ticket from a chat, the assignee also gets the chat itself, to reply from “Tickets”.
Which department gets the ticket
Assignment happens only within the ticket's department. The department is set when the ticket is created:
- an email that mail files under the “Sales” category (AI puts wholesale inquiries there, among others) — “Sales and claims department”;
- all other emails, chats and calls — “Customer Service Department”;
- a ticket without a department is assigned as a “Customer service” ticket.
Candidates are active employees who have this department in their card or belong to it, with access to the “Tickets” window. If the department has none, candidates are everyone with access to “Tickets”, from any department: in a small company where the owner still does everything, no ticket gets stuck unowned. AI employees don't get tickets.
To send, say, all calls to sales, change the ticket's department with a flow — see the “Calls go to sales” example. Assignment sees only the department: it ignores the ticket's language and the operator's skills; use a flow for that too.
How not to overload an operator: the limit
The “Max open tickets per person (0 — no limit)” field. An employee who already has as many open tickets as the limit doesn't take part in assignment. If everyone is busy, the ticket stays in “Unassigned” and goes to the first person who frees up: resolves a ticket, moves it to “Pending” or hands it to a colleague.
At peak times, the “Unassigned” queue grows on its own with a limit — a sign you're short of people. If it grows daily, raise the limit or add an employee to the department rather than turning the limit off. Manual assignment, bulk actions and flows don't check the limit: a manager can give a person tickets above it.
How not to give tickets to people who have gone home
The “Only to people on shift (online in chats)” checkbox. “On shift” means “online in chats”: an employee goes online when they open the “Chat dialogs” window and stops being online when they close it. There's also a manual status switch in the chat operator's profile. The app doesn't keep a shift schedule like a timesheet.
With this checkbox, operators who work only with email and never open the chat window won't get a single ticket. Turn it on when all operators in the department keep chats open throughout the day.
Someone left their shift without replying
With the checkbox on, the app takes a “New” ticket from someone no longer on shift and gives it to someone on shift — using the same assignment option and the same notification. Conditions:
- the ticket is still “New”, and nobody has replied to it;
- 10 minutes have passed since the last assignment;
- the app assigned it — assignment or a flow, not an employee.
Example: at 17:55 assignment gave an email to Olena, and at 18:00 she closed chats and left. On the first assignment pass after 18:05, the email moves to Andrii, who is on the evening shift. Without “Only to people on shift”, an assigned ticket doesn't move anywhere.
How to give a customer's ticket to their manager
The “First — to the customer's account manager” checkbox. If the customer is pinned to a manager (customer card → account manager) and the manager has access to “Tickets”, the manager gets the customer's new ticket — with any assignment option, even “Manual”. The limit doesn't apply here: the manager gets their own customer even above the limit.
The ticket follows the usual assignment if there's no account manager, the “Tickets” window is closed to them, or they're not on shift while “Only to people on shift” is on.
New customers who first write in chat, email or call get an account manager automatically: whoever took the call, or for chats and email, the least loaded sales manager. So with a separate support team, the checkbox sends “where is my parcel” questions to salespeople — leave it off. In wholesale, where customers expect “their” manager, turn it on.
How to put VIP customers first
The “VIP customers — High priority” checkbox on the “General” tab, on by default. What happens to a new ticket from a customer in the VIP segment:
- priority — at least “High”: “Normal” and “Low” are raised, “Urgent” stays urgent;
- deadline — by “High” priority: with the default deadlines, first reply within 1 business hour instead of 4, resolution within 16 instead of 40;
- the vip tag — use it to build your own queue or to filter tickets in reports;
- with the “Nearest deadline” sort, the ticket rises higher on its own thanks to the shorter deadline.
The app calculates the VIP segment itself from orders in the customer card: a “Regular” buyer whose total purchases are at least twice the store average. A customer who starts buying a lot joins the segment automatically, and one who stops leaves it.
The rule applies to tickets created after it's turned on, and only when the customer is recognized. An already open ticket doesn't change, and a priority an operator changed manually stays as they set it. Turn the checkbox off if all customers are equal to you or VIPs are already handled by their own managers.
What happens to a manually assigned ticket
Assignment doesn't touch a ticket whose assignee an employee set or removed: with a chip, bulk action or macro. If an operator removed themselves as assignee or a manager cleared the assignee, the ticket stays in “Unassigned” until someone takes it: the person decided this on purpose.
Assignments made by the app — assignment or a flow — don't block it: so a ticket given to someone who left their shift can move to someone else. The fastest way to clear “Unassigned” is “Take next” in the empty “My open” queue — it gives you the unowned ticket with the nearest deadline (working with tickets).
Assignment doesn't reassign tickets of someone on vacation: hand them over with the “Assignee” bulk action.
Scenarios
Online store with a separate support team
What to turn on. “Least loaded in the department”, limit 0, “First — to the customer's account manager” off. What you get. Delivery and return questions are split evenly among “Customer service” operators, and wholesale emails from the “Sales” category go to salespeople automatically.
Wholesale: every customer has their own manager
What to turn on. “First — to the customer's account manager”. What you get. The customer's email, chat or call goes to their manager even above the limit; a new customer without a manager goes to the least loaded one. More in the wholesale scenario.
Day and evening shifts in chats
What to turn on. “Only to people on shift”; operators keep “Chat dialogs” open. What you get. Tickets go to whoever is online now; an unanswered “New” ticket assigned to someone who left moves to the evening shift after 10 minutes.
Seasonal peak: operators can't keep up
What to turn on. A limit, for example 15. What you get. Nobody gets more than 15 open tickets; the rest wait in “Unassigned”. The manager sees that queue: if it grows every day, it's time to add people.
What to do when tickets aren't assigned
| What you see | Why | What to do |
|---|---|---|
| Assignment is on, but new tickets sit in “Unassigned” | The customer wrote more than 3 days ago; or “Only to people on shift” is on and operators don't open “Chat dialogs”; or everyone has hit the limit; or “Manual” is selected | Take old tickets manually; turn off “on shift” or raise the limit; check the option (assignment) |
| Calls and chats with price questions go to support operators | Chats and calls always go to “Customer service”; only emails from the “Sales” category go to sales | Change the department with a flow or manually (which department) |
| One ticket isn't assigned, though others are | At some point someone set or removed the assignee manually | Assign it manually (manually assigned) |
| Operators who work with email don't get tickets | “Only to people on shift” is on, and their “Chat dialogs” window is closed | Clear the checkbox or ask them to keep chats open (on shift) |
FAQ
Can tickets be assigned only during business hours?
No, assignment runs around the clock. To keep tickets from going to people who aren't there at night, turn on “Only to people on shift”.
Why did an operator get a ticket when they already have loads of work?
“Round robin” ignores workload, and tickets in “Pending” don't count as workload. Choose “Least loaded in the department” or set a limit.
Why are some tickets sitting in “Unassigned” after launch?
Only tickets where the customer wrote within the last 3 days are handed out. Old emails collected from mail on first launch are taken or closed manually.
An operator went home, but a new ticket was assigned to them just before. Will it wait until morning?
With “Only to people on shift” — no: after 10 minutes it moves to someone on shift, if it's still “New” without a reply and the app assigned it. Without the checkbox, it will wait.
Why did a ticket arrive with “High” priority and the vip tag?
The customer is in the VIP segment, and “VIP customers — High priority” is on in the “General” tab. If you don't need it, clear the checkbox (VIP).
Can tickets in English go to a specific operator?
Not through assignment — it sees only the department. Assign them with a flow on the ticket creation event (flows).
Where it is and who has access
- Menu
- Directories → Contacts → Tickets → gear → “Support desk settings”
- Tabs
- “Assignment” — option, limit, shift, manager; “General” — VIP
- Access right
- only employees of “Management” see the gear
- Prepare
- operators in the “Sales” or “Customer service” departments with access to “Tickets”
Other settings and who sees tickets are covered in “How to set up the support desk”.
1
Assignment tab2
Distribution mode3
Open tickets limit4
Only people on shift5
Account manager first- Distribution, limit, shift and account manager are all on one tab.
- Out of the box it is “Least loaded in the department”; only tickets where the customer wrote within 3 days are handed out.
- Whoever reaches the limit gets no new tickets; 0 means no limit.
- “On shift” means the Chat dialogs window is open.
- A customer with an account manager goes to that manager, even when distribution is set to Manual.
Related topics
- If you need the overall picture of the settings — How to set up the support desk.
- If tickets are assigned but replies come late — Business hours and response deadlines (SLA).
- If you need to understand how an operator takes tickets and replies — Working with tickets.
- If you want to see each assignee's workload — Support desk reports.
- If you're choosing a helpdesk for an online store — what it gives your store.
