One settings form: new tickets go to operators in the right department, get a reply deadline from your schedule, and overdue ones aren't lost — the assignee and their manager are notified.
When you need this:
- Emails and chats sit unowned — the app assigns and notifies someone.
- Nobody knows who still awaits a reply — each ticket has a deadline chip; overdue ones share one queue.
- A customer writes by email and in Telegram — it all lands in one ticket.
- Operators see others' customers — the department's “Data scope” limits tickets too.
Where to start: what to set today — most values are set out of the box.
What the settings do
- Access — who can open the “Tickets” window and which tickets each department sees.
- Assignment — a new ticket goes to an operator on its own: round robin, to the least loaded, to the customer's manager; a per-person limit, only to people on shift.
- Business hours and SLA — first reply and resolution deadlines by priority, holidays, a pause in “Pending”, escalation to a manager.
- One ticket per customer — an email, chat and call from a known customer end up in one ticket.
- Customer rating — after “Solved”, the customer rates the reply “Good / Bad”.
- Flows — your own rules on ticket events: change the department, assignee, priority.
Who sees tickets
Window. “Tickets” is open to three departments: “Management”, “Sales and claims department” and “Customer Service Department”. To open it to, say, the warehouse, give the department access to the window in access rights — how to do it.
Shortcut. Employees of these three departments have the “Tickets” shortcut on the main desktop. New “Sales” and “Customer service” employees get it with their role's desktop, new “Management” employees with the starter desktop. A department you open the window to later won't get the shortcut on its own — add it manually.
Which tickets. The department's “Data scope” applies — the same setting that limits contacts and documents (how to set it):
| Department's “Data scope” | What the employee sees in “Tickets” |
|---|---|
| “All” | All tickets. |
| “Own and subordinates” | Their own, their subordinates' in the org chart, and unassigned tickets. |
| “Own only” | Their own and unassigned tickets. |
Unassigned tickets are visible in all three modes — otherwise the “Unassigned” queue would be empty and nobody would pick up new tickets. Contacts and documents follow a different rule: there, “Own only” hides records with no responsible person.
The limit applies everywhere: in queues and counters, in the ticket card (someone else's ticket won't open from a link), in bulk actions and reports. An employee in several departments gets the widest option. An employee with “Own and subordinates” who isn't in the org chart isn't limited.
What each tab sets
The “Support desk settings” form is split into tabs. Everything is saved with one “Save” button; after saving, the app recalculates the deadlines of all open tickets and shows “Settings saved, open ticket deadlines recalculated”.
| Tab | What's there | More |
|---|---|---|
| “General” | “One customer — one open ticket”, “VIP customers — High priority”, customer rating: a request to rate the reply after “Solved” and the request text | one ticket, VIP, rating |
| “Assignment” | Assignment option, open ticket limit per employee, “Only to people on shift”, “First — to the customer's account manager” | ticket assignment |
| “Hours & SLA” | Working days and hours, days off, deadlines for four priorities, SLA breach notifications | business hours and deadlines |
1
Tab strip2
One customer — one open ticket3
VIP customers — High priority4
Customer rating checkbox5
Save- Assignment and Hours & SLA are on the neighbouring tabs.
- An email, chat or call from a known customer goes into one ticket; the reply goes via the last channel used.
- A VIP customer gets priority of at least High and the vip tag.
- After “Solved” the customer is asked to rate the reply as Good or Bad.
- Saves all tabs and recalculates the deadlines of open tickets.
Where to start: what to set today
The values below suit a team of two or more operators working during the day. Most are already set out of the box; app updates don't change the values you've saved.
| Field | Set | When to choose otherwise |
|---|---|---|
| “Distribution of new tickets” | “Least loaded in the department” (out of the box) | One operator — “Manual”; short, similar tickets — “Round robin” |
| “Max open tickets per person” | 0 — no limit | People drown at peak times — set a limit |
| “Only to people on shift (online in chats)” | leave off | All operators keep “Chat dialogs” open all day |
| “First — to the customer's account manager” | retail — leave off | Wholesale and key accounts that expect a reply from “their” manager |
| “One customer — one open ticket” | keep (out of the box) | One customer often has parallel questions for different departments |
| “VIP customers — High priority” | keep (out of the box) | All customers are equal to you |
| “Business hours” | your days and hours, holidays a year ahead in 2026-12-25 format | 24/7 support — seven days from 00:00 to 23:59 |
| “SLA targets, business minutes” | leave as is | After two weeks, check them against the report |
| “SLA breached — notify…” | keep (out of the box) | Notifications get in the way — chips and the queue work without them |
| Customer rating | don't turn on yet | You've cleared old tickets and want to know who replies poorly |
Set up the support desk
After that, the window runs on its own; in a week, open the reports.
How to merge a customer's email, chat and call into one ticket
The “One customer — one open ticket” checkbox on the “General” tab is on out of the box. An email, chat or call from a known customer whose open ticket had activity in the last 3 days joins that ticket instead of starting a new one. The conversation stays with one assignee, and the customer doesn't get three different replies.
- The reply goes via the last channel. The customer wrote in Telegram after an email — the reply goes to Telegram. The feed shows the event “The customer wrote via another channel — the reply goes to: …”.
- A known customer is one the app found among your contacts by chat, email or phone. A Telegram message without a phone number or email becomes a separate ticket until an operator merges the tickets or links the customer (working with tickets).
- The three days count from the last action in the ticket, not from its creation. A solved ticket, or one with no activity for a week, doesn't pick up new messages.
Turn the checkbox off if one customer often has different questions for different people at the same time: the customer's accounting team writes about an invoice, and their buyer about a new order.
How to add your own rule: flows on ticket events
Whatever the settings don't cover, flows do. A flow starts with an “On event” block with the source “Ticket: event (created, status, assignee, customer reply, SLA breached…)” and changes the ticket with a “Ticket: update” block. You can build a flow in the “Flows” editor or describe it in words — create a flow from text.
| ticket_event | When | What's in old_value |
|---|---|---|
| created | the ticket was created | — |
| status, priority, assignee, department, tags | this field changed — by hand, by assignment, by a customer reply or by another flow | the previous value |
| customer_reply | the customer wrote in the ticket | the status before their message |
| sla_breach | a deadline was missed | first, next or resolve — which one |
| csat | the customer rated the reply | good or bad |
A flow also sees the ticket fields: status, priority, channel, assignee, department, tags, subject, AI reason, the customer and their order-based segment (new, repeat, regular, vip, sleeping, lost). “Ticket: update” sets “Status”, “Priority”, “Assignee”, “Department”, “Add tags (comma-separated)” and “Internal note (the customer does not see it)”. Empty field — “— keep —”. The block sends nothing to the customer.
Example 1. Calls go to sales
“On event” (Ticket) → “Condition (If)”: ticket_event = created and channel = phone → “Ticket: update”: department 9, tag “call”. A ticket from a call moves to the “Sales and claims department” before assignment. Use a reason condition at creation time only for emails: for chats and calls, the reason is still empty.
Example 2. Overdue urgent ticket goes to a senior operator
“On event” (Ticket) → “Condition (If)”: ticket_event = sla_breach and priority = urgent → “Ticket: update”: assignee — the senior operator, note “Overdue urgent ticket, taken over”. Escalation only notifies, while the flow actually hands the ticket over.
Example 3. A “Bad” rating goes back into work
“On event” (Ticket) → “Condition (If)”: ticket_event = csat and old_value = bad → “Ticket: update”: status “Open”, tag “bad-rating”, note “Customer unhappy — call them”. The assignee and their manager get a bad-rating notification even without a flow (how it works).
Flows run immediately, at the moment of the event. A flow that is currently running doesn't start a second time, so its own change to the ticket won't restart it. An error in a flow doesn't affect working with the ticket.
Scenarios
The owner still handles everything alone
What to do. Change nothing. What you get. Nobody is in the departments, so tickets go to anyone who can open “Tickets” — that is, the owner; deadlines and chips work out of the box. When you hire an operator, add them to “Customer service” — tickets will go to them.
An online store with a support team
What to do. Operators go to “Customer service” with “Data scope” = “Own only”, the manager to “Management” with a crown in the org chart. What you get. Everyone sees their own and unassigned tickets; the manager sees all of them and gets overdue notifications. More: tickets in an online store.
A wholesale company with account managers
What to do. “First — to the customer's account manager”, “One customer — one open ticket”. What you get. A customer's email, chat and call make one ticket with their manager. More: tickets in wholesale.
The warehouse needs to answer stock questions
What to do. Open the “Tickets” window to the warehouse department, add the shortcut manually, set “Data scope” = “Own only”. What you get. The warehouse sees tickets assigned to it and unassigned ones.
What to do when the settings don't apply
| What you see | Why | What to do |
|---|---|---|
| No settings gear | Only employees of “Management” see the gear | Ask your manager or add yourself to the “Management” department (access) |
| An operator can't see a colleague's ticket | Their department's “Data scope” is “Own only” or “Own and subordinates” | Change the department's mode (who sees tickets) |
| A customer wrote in Telegram and by email — you got two tickets | The app didn't recognize the customer in the chat, or the first ticket is already solved or has had no activity for more than 3 days | Merge the tickets or link the customer (one ticket) |
| The window was opened to a department, but there's no shortcut on the desktop | Only “Management”, “Sales” and “Customer service” got the shortcut automatically | Add the shortcut manually (shortcut) |
FAQ
How do I give the warehouse access to tickets?
Open the “Tickets” window to the department in access rights. Which tickets it sees depends on the department's “Data scope”; add the shortcut manually (scenario).
Why didn't a customer's new email become a separate ticket?
“One customer — one open ticket” is on: a message from a known customer with an open ticket is added to it. If you need separate tickets, clear the checkbox.
Will my settings change after an app update?
No. The default values apply until you save the form; updates don't touch the values you've saved.
I saved the settings without changing anything. What happens?
The app recalculates the deadlines of all open tickets using the current settings. Tickets that are already overdue may trigger a repeat notification (escalation).
Can different departments have different settings?
No, there is one set of settings for the whole support desk. Different behavior for a department, channel or customer segment is set up with flows.
Does an operator with “Own only” see unassigned tickets?
Yes, unassigned tickets are visible in every “Data scope” mode so that someone picks them up.
Where to find it and who has access
- Menu
- Directories → Contacts → Tickets; or Organizer → Tickets
- Other ways in
- the “Tickets” shortcut on the desktop
- Settings
- the gear in the header of the queues panel on the left → “Support desk settings”
- Access right
- the “Tickets” window in group permissions; the gear — only “Management”
- Prepare
- operators in the “Sales” or “Customer service” departments, manager crowns in the org chart
An operator from “Sales” or “Customer service” doesn't see the gear and can't change the settings, even if the window is open to them. The same gear menu has “Move from other systems”; see the article “How to move tickets from another system”.
Related topics
- If you need to decide who gets a new ticket — How to assign tickets to employees.
- If you need to set a schedule and reply deadlines — Working hours and reply deadlines (SLA).
- If the setup is done and you want to see the results — Support desk reports.
- If you need to open the window to a new department — Access rights.
