Elbuz puts emails, chats, messengers, calls, marketplace questions and bad reviews into one queue; AI can close routine requests itself, by your rules.
When you need this:
- Half the questions are “where is my order” — the operator inserts the waybill in one click, or customers get the status unassisted.
- Customers write on Rozetka, Telegram and Instagram posts — one queue, assignee and deadline included.
- Cancellations and returns take time — AI processes them after the customer's “Yes”; a person handles refunds.
- A parcel is lost or delayed — reshipment or a compensation promo code that keeps the order profitable.
Where to start: connect channels, then assignment and deadlines.
What store support can do
- One queue from all channels — email, website chat, messengers, calls, Rozetka, Allegro, Prom, Facebook and Instagram reviews and comments.
- Assignment and deadlines — a new ticket goes to an operator automatically, overdue ones are shown in red.
- Macros — ready-made replies with the number, status and of the customer's last order.
- AI assistant — a reply draft, the waybill in the reply, the next order stage in one click.
- Autonomous order actions — cancellation, returns including defects and exchanges, branch change, reshipment, promo code.
- Reports — reply speed, overdue tickets, what AI closed, customer ratings.
Which channels to connect
Email, website chat, messengers and telephony become tickets on their own as soon as the channel is connected. Marketplaces, reviews and comments are turned on separately. A store should connect every place its customers write:
| Channel | What becomes a ticket | Where to turn it on |
|---|---|---|
| Email, website form | an email from a person; newsletters and supplier emails are filtered out | Ticket channels |
| Website chat, Telegram, Viber, Facebook, Instagram, WhatsApp | a chat that needs a person; a conversation the bot is handling does not | Ticket channels |
| Telephony | a missed call — with “High” priority; an answered call — with a call summary | Ticket channels |
| Rozetka, Allegro, Prom | customer messages, with the marketplace's reply deadline | Marketplace messages |
| Website and Rozetka reviews | a low-rated review you haven't replied to | A negative review as a ticket |
| Facebook and Instagram comments | a comment under a page post | Comments in tickets |
A customer who emailed and then wrote in Telegram ends up in one ticket with one operator, if the system recognized them. More: how channels merge into one ticket.
Instagram and Facebook comments are turned on with a toggle in the channel card, and they start arriving once Meta has approved comment access for Elbuz.
How to assign tickets and which deadlines to set
Assignment and deadlines are set in “Support desk settings”. For a store with a few people:
- Two or three operators always in the queue — the “Assignment” tab, “Least loaded in the department”: a new ticket goes to whoever has the fewest open ones.
- An operator plus an owner who steps in at peak times — “Manually”: everyone takes tickets themselves, and “Take next” gives the most urgent unassigned one.
- A newcomer on the team — fill in the limit of open tickets per employee.
A store with a separate support team should leave the “First — to the customer's account manager” checkbox off. Every new customer gets a sales manager automatically, so “where is my parcel” questions would go to salespeople. More: ticket assignment.
Deadlines are set in working minutes for each priority on the “Hours & SLA” tab. The default numbers assume Mon–Fri 09:00–18:00, and a person in the website chat won't wait four hours. For a store open Mon–Sat 09:00–19:00, this set works:
| Priority | First reply | Next reply | Resolution | What goes here |
|---|---|---|---|---|
| Urgent | 15 | 30 | 300 (half a day) | a complaint, raised manually or by a process |
| High | 30 | 60 | 600 (1 day) | a missed call, a VIP customer, a one-star review |
| Normal | 120 | 240 | 1800 (3 days) | emails and chats by default |
| Low | 240 | 480 | 3000 (5 days) | suggestions, an email AI rated as unimportant |
Three days for a normal ticket covers typical delivery: you have time to reply and wait for the parcel to be delivered. Marketplace messages also get the marketplace's deadline if it is shorter. More: support SLA.
Which macros to create
A macro inserts ready-made text and sets the “Send as” status. Variables fill in the customer's name and the number, status and waybill of their last order. Besides the four starter macros, a store should create four more:
| Name | Text | Send as |
|---|---|---|
| Order is still being packed | {CUSTOMER_NAME}, your order {LAST_ORDER_NUMBER} currently has the status “{LAST_ORDER_STATUS}”. As soon as we hand it over to the carrier, we'll send you the waybill number. | Solved |
| Return policy | {CUSTOMER_NAME}, we're processing a return for order {LAST_ORDER_NUMBER}. Please send the item complete with everything it came with and reply with the shipment's waybill number. | Pending |
| Warranty — sent for inspection | {CUSTOMER_NAME}, we've passed your question about order {LAST_ORDER_NUMBER} on for a warranty inspection. We'll write as soon as we get the result. Your ticket number is {TICKET_ID}. | On hold |
| Apology for the delay | {CUSTOMER_NAME}, sorry you had to wait. I'm {AGENT_NAME}, I'm personally handling your ticket #{TICKET_ID} and will write to you before the end of today. | Open |
“Pending” for a return stops the resolution clock until the customer has shipped the item. “On hold” for a warranty case keeps the ticket in the queue, but the deadline keeps running. More: how to reply with a macro.
1
Macros button2
Save the text as a macro3
Send as- Macros button — opens the list of ready-made replies.
- Save the text as a macro — turns the text typed in the reply field into a new macro.
- Send as — the status the ticket gets after the reply is sent.
How to answer “Where is my order”
A store's most common question can be closed in three ways, from manual to fully automatic:
- Operator with the AI assistant. AI finds the customer's order, the “AI suggests” block shows an “Add tracking to reply” button, and “AI draft” writes a reply with the status and carrier. The operator sends it. More: order actions from AI suggestions.
- AI replies by itself in messengers and website chat — with the status and waybill, when the policy and trust allow it. More: auto-replies in chats.
- The customer finds out before they ask. Proactive messages say the parcel has arrived at the branch and remind the customer before it goes back to the sender. More: parcel status and customer notifications.
AI takes the order number from the email, and without a number — the customer's last order. Check that the number on the button matches the order the customer is asking about. A customer's thank-you after the waybill (“Thanks!”) doesn't reopen a solved ticket.
1
Intent chip2
Tracking number into the reply3
Move order to the next stage4
Recent documents: Add tracking to reply- Intent chip — what AI recognised the question as (Order status).
- Tracking number into the reply — inserts the tracking number into the reply field without sending it.
- Move order to the next stage — AI proposal that changes the order stage; not pressed in this shot.
- Recent documents — the customer's order with the “Next” and “Add tracking to reply” buttons.
Cancellations, returns, defects and exchanges
The operator handles these requests with a button from the AI suggestion; with autonomous support, AI does it by itself after the customer says “Yes”. AI never moves money in any case.
| Request | What AI does by itself | What stays with a person |
|---|---|---|
| “Cancel my order” | cancels an unpaid order with no waybill; Rozetka, Prom and Epicentr orders — on the marketplace first | refund a paid order: AI prepares an unposted draft “Cash payment” document |
| “I want to return it” | checks the return period and items, creates an unposted return request, sends the customer the return procedure | receive the item, post the document, refund the money |
| “It arrived defective” | processes a return marked “Defect”, with a separate period; by default the store pays for delivery | the same as for a return |
| The customer wants a return, and you want to keep the sale | first offers an exchange in your words; if the customer insists, processes a regular return | — |
| “Deliver to another branch” | finds the Nova Poshta branch, changes it in the order, recreates the waybill if needed | approve the change if delivery became more expensive |
Mark non-returnable products (hygiene, cosmetics, made to order) in the category directory: clear “Returns allowed” in the category card. AI hands such returns to an employee, but processes defects. More: cancellation, returns and defects, branch change.
Without autonomous support, the operator processes the return: the “Create a return for …” button in the “AI suggests” block creates an unposted document with all order items. More: how to work with a customer's order.
Lost, damaged or delayed parcel
- The parcel is lost. The system treats it as lost only if it has had no movement in Nova Poshta longer than the set period. After the customer's “Yes”, the warehouse gets an unposted order copy with zero prices and a shipping task. One order is reshipped once; one customer, once every 90 days. More: reshipment.
- The parcel is damaged. A reshipment is processed once the customer has sent a photo. If the customer keeps the item, a promo code works instead.
- The parcel is delayed. AI offers a one-time promo code for the next order: by default 5% of the order total for a delay and 10% for damage.
A promo code won't push the order into a loss. First the system calculates the post-discount markup from the products' cost price. Below the threshold (15% by default) or with no cost price, an employee decides. The code is created in the built-in Elbuz storefront or on an OpenCart 3 website. More: how a promo code avoids a loss.
In what order to turn on autonomous support
Everything autonomous is off out of the box. Nothing goes to the customer until the “AI may act by itself under the policy” switch is on, the policy is applied and the action type is set to “Live”. This order works for a store:
- Policy. On the “Policy” tab, set action types and limits: order amount, how many actions per hour and per day. You can describe the rules in plain text and AI will fill in the form. Click “Apply”.
- A week of “Test”. Set “Test” for all types and for auto-replies in messengers and website chat. AI sends nothing and records what it “would do” in the “Review” queue. Rate the decisions 👍 or 👎.
- “Live” without money. First — cancelling unpaid orders and changing the branch, in one channel. Then auto-replies in messengers and proactive messages.
- A run for money-related types. Returns, reshipment, promo code and cancelling a paid order go “Live” only after a run on past tickets: at least 30 decisions, at least 90% agreement with people, and no dangerous ones.
- Trust. For types in “Live”, turn on “Act on its own” on the “Actions and trust” tab. Without it, AI only suggests the action to an employee.
AI messages to customers are signed with a line about the AI assistant — the “Sign AI messages to customers” checkbox on the “Channels and proactive” tab. The signature text is set in “Automatic message texts” in the chat settings. More: how to turn on autonomous support safely, test and run.
How to check that support is working
- Every morning — the “Right now” block in reports: who has how many open and overdue tickets. More: support reports.
- Every week — the “Review” queue of AI decisions and AutoQA results: the worst conversations with a hint on what to improve. More: quality control.
- Every month — “SLA met”, “Solved without a human” and “Orders after tickets”: how many questions AI closed and what support brought to sales.
- Customer rating — off out of the box. Turn it on if you want to know which operators reply poorly. More: customer rating.
Scenarios
A store launches support in one day
What to do. Connect email, website chat and Telegram; “Least loaded in the department”; deadlines from the table above; four macros. Don't turn on autonomous support yet. Result. Tickets get an assignee and a deadline right away, and “where is my order” is closed with the “Add tracking to reply” button.
A customer asks to cancel an order at night
What to set up. The “Order cancellation” type in “Live” with “Act on its own” trust, channel — messengers. Result. An unpaid order with no waybill is cancelled after the customer says “Yes”, and the reservation is released. A paid one waits for a person with a ready draft refund document.
The supplier decides on warranty
What to do. In the ticket, “⋯” → “Write to a supplier / warehouse”; to the customer — the “Warranty — sent for inspection” macro with “On hold”. Result. The supplier's reply arrives in the same ticket, and the customer doesn't see it; the operator passes the decision on. More: how to ask a supplier.
After a newsletter — 60 tickets in an hour
What to do. Switch the list to “Board”, keep the “Nearest deadline” sort, hand out tickets in batches via right-click. If the system spots a one-topic spike, save a bulk reply draft in the spike panel. Result. Those waiting longest get replies first; operators send all spike customers the same text. More: board, replying to a spike.
A third email from an angry customer
What to do. Take the ticket yourself, set “Urgent”, write a note to your manager with @login, reply with the “Apology for the delay” macro. Result. Deadlines are recalculated for the new priority right away, the manager gets a notification, and the customer doesn't see the note. AI never replies to complaints and returns by itself.
FAQ
The customer is asking about an older order, but the macro filled in the last one. What should I do?
Macro variables always take the customer's last order. For an older one, click “Add tracking to reply” next to the right document in the right panel. More: right panel.
Will AI refund a cancelled paid order?
No. AI prepares an unposted draft “Cash payment” document and tells the customer that the store will process the refund. An employee posts the document and refunds the money.
Why doesn't AI issue a promo code even though the type is on?
Most often the order's products have no cost price, or the markup after the discount is below the threshold. Then the decision goes to an employee. Another reason: the website is neither on the built-in Elbuz storefront nor on OpenCart 3.
A customer complained in chat and the bot replied by itself. Why is there no ticket?
A chat becomes a ticket when a person is needed: the bot handed the chat over to an employee, or an employee has already written in it. A conversation the bot handles by itself doesn't get into the queues. More: when a message becomes a ticket.
We work on Saturdays. How do I account for that in deadlines?
On the “Hours & SLA” tab, tick Saturday in working hours and enter public holidays in “Holidays”. More: working hours and holidays.
Can chats get a reply faster than emails?
There is no separate deadline per channel: deadlines depend on priority. Raise the priority of new chat tickets with a process on a ticket event. More: processes on ticket events.
AI processed a return by mistake. How do I roll it back?
Click “Undo action” in the ticket's “AI actions” block before the document is posted — the return request will be deleted. More: how to delete a return request created by AI.
Where it is and who has access
- Menu
- Directories → Contacts → Tickets; Organizer → Tickets
- Support settings
- the window's gear icon → “Support desk settings”
- Autonomous support
- the window's gear icon → “Autonomous support”
- Access rights
- “Tickets” — “Management”, “Sales”, “Customer service”; settings — “Management”
- Prepare
- email and website chat, operators in the “Customer service” department, articles about delivery and returns
Related topics
- If you need the overall picture of “Tickets” — customer tickets: where to start.
- If an operator is opening the queue for the first time — working as a support operator.
- If you're deciding what AI will do by itself — autonomous support.
- If you need to set up the store's order statuses — online store and pickup point.
