Elbuz sets each ticket a reply and resolution deadline by your working schedule and notifies the assignee and their manager when it passes, so nobody has to ask who's still unanswered.
When you need this:
- An email arrives Friday evening — nights, weekends and holidays don't count.
- A ticket awaits the customer's reply — the resolution clock stops while it's “Pending”.
- A deadline passed — the ticket turns red, sits in the “SLA breached” queue, the manager is notified.
- The customer wrote “Thanks” — a solved ticket doesn't reopen.
Where to start: gear in “Tickets” → “Support desk settings” → “Hours & SLA” tab → your working days and hours.
What deadlines can do
- Working schedule and holidays — deadlines count business minutes only.
- Three deadlines for each priority — first reply, next reply, resolution.
- Pause — “Pending” stops the resolution clock.
- Chip and the “SLA breached” queue — how much time is left and what's already overdue.
- Escalation — notifications to the assignee and their manager, one per breach.
- Auto-close — a solved ticket closes after 4 days, and a “thanks” doesn't reopen it.
How to set business hours and holidays
The “Business hours (SLA counts only these)” block sets the days of the week and the hours; the default is Mon–Fri, 09:00 to 18:00. Night hours, weekends and holidays don't eat into reply time. The schedule doesn't affect assignment: tickets are assigned at night too if there's someone to assign them to.
| What you set | How deadlines are counted |
|---|---|
| Any days, for example Mon–Sat or Mon–Thu | Strictly by the checked days. With Mon–Thu, an email on Thursday at 17:30 with a 4-business-hour deadline waits for a reply until Monday 12:30. |
| No day checked | Around the clock, seven days a week — as the hint says: “No days selected — 24/7.” |
| Start not earlier than end, for example a night shift from 22:00 to 06:00 | The settings aren't saved: the window stays open with the message “The working day must end after it starts. Overnight shifts (e.g. 22:00–06:00) are not supported: clear all days for 24/7 work.” |
| “Holidays (YYYY-MM-DD, comma-separated)” | These days are skipped, for example 2026-12-25, 2027-01-01. A date in another format (25.12.2026) is silently dropped on save. |
After saving, open the settings again and check that the holidays are there and the days haven't disappeared: this shows which schedule the app actually uses. There's one set of business hours for the whole support desk — no separate schedule per department or employee.
How to set reply and resolution deadlines
Every ticket has three deadlines, and each priority has its own. You set them in the “SLA targets, business minutes” table:
- First reply — from the moment the ticket appears in Elbuz to the first reply to the customer. An answered incoming call also counts as a reply; a missed one doesn't.
- Next reply — from a new customer message to our reply to it, after the first reply.
- Resolution — from ticket creation to the “Solved” status.
| Priority | First reply | Next reply | Resolution |
|---|---|---|---|
| Urgent | 30 min | 60 min | 480 min (8 h) |
| High | 60 min | 120 min | 960 min (16 h) |
| Normal | 240 min (4 h) | 480 min (8 h) | 2400 min (40 h) |
| Low | 480 min (8 h) | 960 min (16 h) | 4800 min (80 h) |
An empty field or zero isn't saved — the previous number stays. The priority of a new email is set by the AI mail triage, a missed call gets “High” right away, and everything else gets “Normal”. When an operator changes the priority, all three ticket deadlines are recalculated.
For conversations with Rozetka, Allegro and Prom buyers, the marketplace's own reply deadline in calendar hours also applies: if it's shorter than your schedule allows, the ticket gets that one. More: marketplace messages.
Example with numbers
Schedule: Mon–Fri 09:00–18:00. An email with Normal priority arrives on Friday at 16:30.
- First reply — 240 min: 90 min on Friday, the remaining 150 min on Monday. Deadline — Monday, 11:30.
- Resolution — 2400 min: 90 min on Friday, 540 min each Monday to Thursday, and 150 min more. Deadline — the next Friday, 11:30.
- Monday is listed in “Holidays” — the first reply moves to Tuesday, 11:30.
- The same email with “Urgent” priority — first reply by 17:00 the same Friday.
- An email on Wednesday at 22:15 with a 30-min deadline — reply by Thursday, 09:30: the countdown starts in the morning.
How statuses affect deadlines
| Status | What happens to the deadline |
|---|---|
| “New”, “Open” | The deadline runs: the chip is visible, and a breach goes to “SLA breached” and to escalation. |
| “On hold” | The deadline runs too. “On hold” means “we're busy with something else”, not “the clock is stopped”. |
| “Pending” | No deadline: no chip, queue or escalation. Business minutes spent in this status are added to the resolution deadline. |
| “Solved”, “Closed” | No deadline. |
Example: Normal priority, resolution — 40 business hours. The operator replied after 2 hours and set “Pending”; the customer stayed silent for six business days. When they reply, the ticket goes back to “Open” with the same 38 hours for resolution, not overdue. The next reply deadline counts from the customer's latest message.
“On hold” doesn't stop the clock. A ticket that waited a week for the warehouse in “On hold” comes out with an overdue resolution. Waiting for the customer — set “Pending”; waiting for a third party — “On hold”.
How to see overdue tickets
Each ticket row has a stopwatch chip: how much time is left until the nearest deadline — the smaller of “reply” (first or next reply) and “resolve”. The chip's tooltip says which deadline it is and when it's due, for example “SLA: first reply — due 20.10 14:30”.
- gray “2 h 15 min left” — more than 30 minutes left;
- yellow “20 min left” — less than 30 minutes;
- red “1 h 40 min overdue” — the deadline has passed, by that much.
1
SLA breached queue2
Overdue chip- All tickets with an overdue target.
- Overdue by ... — how long ago the target passed; the tooltip shows which target and its due time.
The “SLA breached” queue shows all tickets with a red chip. A ticket leaves it when the deadline itself goes away: the operator replied, or the ticket was moved to “Pending” or “Solved”. A reply to the customer doesn't clear an overdue resolution — it stays overdue.
Who gets notified about overdue tickets
The app checks deadlines together with assignment: about once a minute on a working day, and every 5 minutes in the background. So a notification may arrive one to five minutes after the deadline; the red chip appears at once. When a deadline passes:
- the ticket feed shows the event “SLA breached: first reply” (or “next reply”, “resolution”);
- flows listening to the “SLA breached” event start (flows);
- if “SLA breached — notify the assignee and their manager” is checked (it is by default), the notification “Ticket #N: SLA breached (first reply)” arrives.
The checkbox turns off only the notification: the feed event, the queue and the flows work without it.
Who the manager is
The notification goes to the assignee and their manager from the org chart. The app looks for the manager in this order:
- the employee the assignee reports to on the chart, or whoever has the crown in the assignee's unit (if the assignee has the crown, this step is skipped);
- the head with the crown in the sales department;
- the first active employee in “Management”.
For a ticket without an assignee, only the manager found from step two gets the notification.
How many times. One notification per overdue deadline, no hourly reminders. First reply missed — one; the customer wrote again and still no reply — another; resolution overdue — one more. A new deadline also appears after a priority change or after saving the settings: an overdue ticket with a new deadline will send one more notification.
Escalation only notifies; it doesn't hand the ticket over. To pass an overdue ticket to a senior colleague, use a flow, for example “Overdue urgent ticket goes to a senior operator”.
When a solved ticket closes and when it reopens
| What happened | What happens to the ticket |
|---|---|
| “Solved”, the customer is silent for 4 days | The status changes to “Closed” by itself. This period can't be changed. |
| The customer wrote a short thank-you in “Solved”: “Thanks!”, “Все отримав” (got everything), “ok 👍” | The ticket stays solved, and the feed shows the event “The customer said thanks — the ticket stays solved: “…””. |
| The customer wrote something else in “Solved” | The ticket is “Open” again, with a fresh next reply deadline. |
| The customer replied by email to a “Closed” ticket | A new ticket is created with the event “Follow-up of ticket #N”. |
A thank-you is a message of up to 80 characters with no question mark that contains words of thanks and no “but”, “not” or “still”. “Thanks, but the parcel still hasn't arrived” will reopen the ticket.
Scenarios
Support works weekdays during the day
What to set. Mon–Fri 09:00–18:00, holidays for a year ahead, default deadlines. What you get. An email on Friday evening won't be overdue on Monday morning; a Normal ticket needs its first reply within 4 business hours.
24/7 support
What to set. Seven days from 00:00 to 23:59, or no days at all. What you get. Deadlines count calendar time: an urgent email at 3:00 a.m. needs a reply by 3:30.
The reply depends on the warehouse or a supplier
What to do. While waiting for a third party — “On hold”; while waiting for the customer — “Pending”. What you get. Time spent waiting for the customer doesn't eat into the resolution deadline, and a warehouse delay shows up as a red chip.
The deadlines are unrealistic
What to do. After two weeks, open the reports. Most breaches are on resolution — raise the resolution deadline; customers complain about slow replies — lower the first reply. After saving, tickets that are already open get the new deadlines too.
What to do when deadlines are counted wrong
| What you see | Why | What to do |
|---|---|---|
| After “Save” the window doesn't close: “The working day must end after it starts…” | The business hours start is not earlier than the end, for example a night shift 22:00–06:00 | Set hours within one day; for 24/7 work, clear all days (business hours) |
| The holiday is in the settings, but a deadline still falls on it | The date wasn't written as YYYY-MM-DD, so it wasn't saved | Enter 2026-12-25 and open the settings again — check that the date is there |
| The customer replied — and the ticket is red right away | The ticket waited in “On hold” or “Open”, not in “Pending”: the resolution deadline was running all along | When waiting for the customer, set “Pending” (statuses) |
| The breached notification goes to the director instead of the department head | The assignee's unit has no crown, so the app moved on: to the sales head, then to “Management” | Give the crown to the unit head (who the manager is) |
| After saving the settings, repeat overdue notifications arrived | Saving recalculates deadlines of open tickets; an overdue ticket with a new deadline notifies again | Nothing — this happens once after saving (escalation) |
FAQ
I changed the SLA deadlines — will this affect only new tickets?
No, all of them except solved and closed ones: when you save, the app recalculates the deadlines of open tickets.
Does “Pending” stop the SLA timer?
Yes, for the resolution deadline: business minutes spent waiting are added to it. The next reply deadline counts again from the customer's message (statuses).
Who gets the SLA breach notification if there's no assignee?
The head with the crown in the sales department, and if there isn't one — the first active employee in “Management”.
Can I turn off SLA notifications but keep the red chips?
Yes. Clear “SLA breached — notify the assignee and their manager” — the chips, the queue and the flows will keep working.
Can I set a separate schedule for a department or an employee?
No, there's one set of business hours for the whole support desk. Shift-based assignment is handled by “Only to people on shift (online in chats)”.
Can I change the 4 days before auto-close?
No, this period is fixed. You can close a ticket earlier by hand with the “Closed” status.
Where it is and who has access
- Menu
- Directories → Contacts → Tickets → gear → “Support desk settings”
- Tab
- “Hours & SLA” — schedule, holidays, deadlines, escalation
- Access rights
- only employees of the “Management” department see the gear
- Prepare
- crowns for unit heads in the org chart — escalation depends on them
After “Save”, the app shows “Settings saved, open ticket deadlines recalculated”. The new deadlines apply to all tickets except solved and closed ones, not just to those that arrive after you save.
1
Business days2
Holidays field3
SLA targets table4
Escalation checkbox- Targets are counted only within the checked days and hours.
- Holidays only in the format 2026-12-25, otherwise the date is not saved.
- Business minutes for each priority; after saving, targets of open tickets are recalculated.
- Turns off only the notification — the timeline event and workflows stay.
Related topics
- If you need the overall picture of the settings — How to set up the support desk.
- If tickets sit unassigned and deadlines burn because of it — How to assign tickets to employees.
- If you need to see how often deadlines are breached — How to read support reports.
- If notifications go to the wrong manager — Org chart.
- If you're choosing a helpdesk for an online store — what it gives your store.
