Elbuz finds orders where your store may lose money and opens tickets for them. Problem gone — the ticket resolves itself, and the order counts as “Rescued”.
When you need this:
- Customers don't pick up COD parcels — on day 4 the manager gets a ticket and can remind them.
- The supplier ships — order not passed on, no waybill, rejection: a ticket before the customer complains.
- Payment failed or no prepayment — a ticket after the hours you set.
- Showing results — “Orders rescued: N, worth …” per month.
Where to start: “Autonomous support” → “Channels and proactive” → “Problem orders” → “How many in the last 30 days”.
What it does
- Shows in advance how many tickets you would have had over the last 30 days — before you turn anything on.
- Detects eight order problems: from a parcel waiting at the branch to a question in the customer's comment.
- Watches the supplier in dropshipping: order not passed on, rejection, delay, no .
- Keeps one ticket per order and resolves it on its own when the problem goes away.
- Puts everything you need to act in the ticket: the order, the supplier order, the waybill, an email to the customer, an AI draft.
- Counts rescued and lost orders for the month and their total amount.
How to turn it on without flooding the queue
Everything is off until you turn it on. It's best to go in three steps: look at the numbers, run it in “Test” for a while, then switch to “Live”.
- Numbers. Set your thresholds in the “When” column and click “How many in the last 30 days”. The “30 days” column shows how many orders from the last 30 days would have hit each problem; the hint below shows the total. Nothing is saved: recount with other thresholds freely. Over 500 shows as “500+”.
- Test. Turn on the problems you need, set the mode to “Test” and click “Apply”. The system checks orders exactly as in live mode but creates no tickets: the “Notice log” card on the same tab shows rows with the “would do” state.
- Live. When you're happy with the number in the log, set the mode to “Live” and click “Apply”. Tickets start appearing from the next check.
Changes in the card take effect only after “Apply”: each click creates a new version of the autonomous support policy that you can go back to (versions and rollback).
Two limits
| Field | Default | What it sets |
|---|---|---|
| “New problems per run” | 20 | how many new problems the system takes per check, up to 100. The rest go to the next check, 30 minutes later |
| “Orders not older than, days” | 30 | orders created earlier aren't checked, up to 90. So old orders won't pop up on the day you turn it on |
The check runs every 30 minutes together with the “Tickets” update. Orders in final statuses — canceled, returned, done — are never checked.
1
Mode2
New problems per run3
When4
30 days5
This month- Mode — Off, Test (only records what would be done) or Live (creates tickets).
- New problems per run — the limit of new tickets created in one pass.
- When — how long the parcel waits at the branch before it counts as a problem.
- 30 days — how many orders would have been caught over the last 30 days.
- This month — orders rescued and lost this month, with their value.
Which problems the system detects
Each problem is turned on separately. “When” is how long the condition must last for a ticket to appear.
| Problem | Default “When” | How the system knows |
|---|---|---|
| Parcel is waiting at the branch, not picked up | 3 days | the delivery status “awaiting recipient” lasts longer than the threshold |
| Parcel refused / returning to sender | at once | the delivery status “Refused” or a Nova Poshta status about a refusal or return |
| Cash on delivery not received after delivery | 5 days | payment by cash on delivery, the parcel was received, but the order isn't paid |
| Prepaid order is not paid | 24 h | the payment method isn't cash on delivery, cash or credit; counted from when the order was created |
| Payment failed | 2 h | the payment status “Failed” or the order status “Failed payment” |
| Order not shipped (no waybill) | 48 work h | no waybill and the order isn't shipped; with prepayment — counted from payment; pickup orders aren't checked |
| Parcel stuck in transit — no movement | 3 days | the parcel is in transit, but tracking shows no movement for longer than the threshold |
| The customer asks a question or wants a call in the order comment | at once | an order comment from the website or a marketplace looks like a question; AI makes the final call, once per order |
“Work h” means working hours under the “Tickets” schedule: an order placed on Friday evening won't become a problem over the weekend. Delivery problems work only if carrier statuses are updated in orders: without a waybill and tracking, nothing is known about the parcel.
AI draft
The “AI draft” toggle in a problem row: when a ticket opens, AI prepares a draft message to the customer in the ticket's AI block. A person sends it — AI never writes to the customer itself and changes nothing in the order.
Dropshipping: problems with the supplier
The “Dropshipping: supplier order” group appears in the table when dropshipping is selected in the documents “Working scheme”. Without it, a hint below the table tells you where to turn it on. The system finds the supplier order created from the customer order and watches it.
1
Dropshipping: supplier order2
Order not passed to the supplier3
How many in the last 30 days- Dropshipping: supplier order — a separate group of problems for orders passed to suppliers.
- Order not passed to the supplier — its 30-day count shows how often it would have fired.
- How many in the last 30 days — the preview button; it changes nothing.
| Problem | Default “When” | What happens |
|---|---|---|
| Order not passed to the supplier | 2 work h | the order is already in progress (status past “Confirmation”), but there is no supplier order |
| Supplier rejected the order or it is “Pending approval” | 4 h | a canceled supplier order — at once; an unread one “Pending approval” — after the threshold |
| Supplier has not shipped on time | 1 day | the shipping date in the supplier order has passed, and it isn't posted |
| No waybill from the supplier | 24 h | the supplier order exists, but there is no waybill in it or in the customer order |
| Supplier order not paid on time | at once | the payment due date of the supplier order has passed |
| Parcel refused — it will return to the supplier | at once | the customer refused a parcel for an order the supplier shipped |
Supplier problems go into the same ticket as customer order problems. When on, they take over their cases from the general ones: a refused supplier-order parcel is “it will return to the supplier”, not the general “parcel refused”; no waybill is “not passed to the supplier” or “no waybill from the supplier”, not “not shipped”.
What happens to the ticket next
- Start
- State
- End
- One ticket per order. The subject is “Order #…: problem”. A new problem with the same order doesn't open a second ticket — it appears as an event in the first one, and the ticket becomes unread again.
- The problem is gone — the ticket resolves itself. The parcel was picked up, the payment arrived, a waybill appeared — the feed shows a “resolved” event, and once the ticket has no open problems left, it moves to “Resolved”. No rating request is sent to the customer. After that, the usual “Tickets” auto-close applies.
- Closed by hand — it won't come back. If a manager set “Resolved” or “Closed” or merged the ticket while the problem was still open, this problem never shows up again for this order. Another problem with the same order opens a new ticket.
- The problem came back. If a problem resolved itself and then the condition came back, it “needs attention” again — in the order's open ticket or in a new one.
- You turned off a problem or the mode. No new tickets appear; existing ones stay as they are.
How to work with the ticket
The ticket channel is “Problem order”. Below the subject is the “Order problems” block: each problem with its state (“needs attention”, “resolved”, “closed”) and the date it started. Below that are the action buttons.
- “Order #…” — opens the customer order.
- “Supplier order #…” — opens the supplier order, if there is one.
- “Waybill … in reply” — inserts the waybill number into the reply text.
- “Return to supplier” — appears when the customer refused the supplier's parcel: opens the supplier order, where you create the return via “Based on”.
You can reply by email to the address from the order (“Email to …”) or leave an internal note. No messenger reply here: the system created the ticket, not the customer. If the customer writes in chat or by email, the message goes to its own ticket; you can merge them by hand.
1
Order problems2
needs attention3
Order #358774
Waybill in reply5
Email to the customer- Order problems — the block with the order's current problems.
- needs attention — the problem is still there.
- Order #35877 — opens the order from the ticket.
- Waybill … in reply — puts the waybill number into the reply.
- Email to … — the channel the reply will go through.
Tickets in the order list and order card
In the document list, an order with an open ticket has a “Ticket #N” chip — click it to open the ticket. When the ticket is resolved or closed, the chip disappears.
1
Ticket chip- Ticket #9346 — the chip shows the order has a ticket; orders without a problem have no chip.
The customer order card has a “Ticket” tile: with a number if there's an open ticket, or “Create”. “Create” opens a ticket for this order by hand, without any problem: this way a manager keeps the conversation about the order in one place. The tile is visible to users who have the “Tickets” window.
How to tell an order was rescued
In “Tickets” → view button → “Reports”, above the report is the “Orders rescued: N, worth …” tile for this month, lost orders below. Click to list orders with outcome and problems; the number opens the ticket. The “Problem orders” card shows it as “This month: orders rescued…”. The tile appears once the month has an outcome.
1
Orders rescued2
Lost orders3
rescued4
lost- Orders rescued — how many problem orders were saved this month and their total value.
- Lost — how many problem orders were canceled, returned or refused, and their value.
- The “rescued” label marks an order whose problem went away while the ticket was open.
- The “lost” label marks an order that was canceled, is returning or was refused.
| Outcome | When |
|---|---|
| “rescued” | the problem went away (parcel picked up, payment arrived, supplier shipped, waybill added), and the order isn't canceled or returning |
| “lost” | the order was canceled, is returning, or the parcel was refused |
| “would rescue (Test)” | the same for “Test” mode records, counted separately |
- The system counts this itself, without AI.
- It counts only if the ticket was already open when the problem went away. Anything that resolved itself before a ticket opened doesn't count as “rescued”.
- Questions from comments and manually created tickets are never counted as “rescued” — only as “lost” if the order was canceled.
- An order with several problems counts once: “lost” if at least one of them was lost.
- The amount is the order total in the base currency; the month is by the outcome date.
- A ticket closed by hand also gets an outcome: the system keeps watching for 60 more days to see how the order ended.
Scenarios
Fewer unclaimed cash-on-delivery parcels
What to do. Turn on “Parcel is waiting at the branch” (3 days), “Parcel refused” and “Cash on delivery not received” (5 days), with “AI draft” for the first one. Combine it with a customer reminder from proactive notices.
What you get. The customer gets an automatic “parcel at the branch” notice, and if they don't pick it up within 3 days, the manager gets a ticket with a ready email draft. A refusal is visible on the day it happens; unpaid cash on delivery reaches accounting after 5 days.
The supplier ships the goods
What to do. Select dropshipping in the documents “Working scheme”; in the card, turn on “Order not passed to the supplier”, “Supplier rejected the order”, “No waybill from the supplier” and “It will return to the supplier”.
What you get. A forgotten supplier order shows up after 2 working hours, a rejection — at once, and both the customer order and the supplier order open from one ticket.
Prepayment and payment failures
What to do. Turn on “Prepaid order is not paid” (24 h) and “Payment failed” (2 h) with an AI draft.
What you get. The manager writes to the customer while they still remember the purchase — with a draft suggesting another payment method. Once the payment arrives, the ticket resolves itself.
Estimate the workload first
What to do. Click “How many in the last 30 days”, then run a week in “Test”.
What you get. You see how many tickets a day will be added. Turn off a problem that produces too many, or raise its threshold before switching to “Live”.
FAQ
I turned on “Live”, but there are no tickets. Why?
Check that you clicked “Apply” and turned on the problems themselves, not just the mode. The check runs every 30 minutes and only takes orders no older than “Orders not older than, days” (limits).
Will the customer get anything from the system?
No. The ticket is internal; a manager writes to the customer. Automatic parcel notices are a separate feature (proactive notices).
I closed the ticket, but the problem is still there. Will it reopen?
No, this problem won't show up again for this order. A new problem with the same order opens a new ticket (what happens next).
Why don't I see dropshipping problems?
They're shown only when dropshipping is selected in the documents “Working scheme” (dropshipping).
Can I reply to the customer in Viber or Telegram from this ticket?
No, only by email to the address from the order or with a note. If the customer writes in a messenger, reply in their ticket from that chat.
Why didn't a rescued order make it into the counter?
The problem went away before the ticket opened, or it was a question from a comment. Such cases aren't counted (how it's counted).
Where to find it and who has access
- Menu
- Tickets → gear → “Autonomous support” → “Channels and proactive”
- Other entry points
- the “Ticket #N” chip in the order list, the “Ticket” tile in the order card
- Access rights
- settings — the “Autonomous support” window; tickets — the “Tickets” window
- Prepare
- delivery and payment statuses in orders: waybills, carrier tracking
You don't need the global “Autonomous mode” switch for this feature: it has its own mode in the card. Tickets go to the “Customer service” department. The system sends nothing to the customer — a manager writes to them.
Related topics
- If you want the customer to learn on their own that the parcel is at the branch — Where is my order: parcel status and customer notices.
- If you need to set up policy versions and the global mode — Autonomous support: how AI resolves routine tickets by your rules.
- If you're curious where else tickets come from — ticket channels.
- If you need to assess all support work for the month — support reports.
