Elbuz tells customers where their parcel is from the carrier's live status and notifies them itself when it reaches the branch or will soon return to the sender — no emails from staff.
When you need this:
- Half your tickets are “where is my order” — AI answers with status, branch and date from the carrier.
- Parcels aren't picked up — an “arrived at the branch” notice and a reminder 2 days before return.
- Don't wake customers — no notices during quiet hours.
- Know what went to whom — a notice log with each one's status.
Where to start: “Autonomous support” → “Channels and proactive” → “Proactive notices”.
What it does
- Answers “where is my order” with the live parcel status.
- Notifies that the parcel is waiting at the branch and sends a reminder before the return.
- Writes where the customer talks to you: to the messenger of the latest chat, otherwise by email.
- Limits the number of notices per day and respects quiet hours.
- Keeps a log of the last 50 notices.
- Asks for a review a set number of days after delivery.
How AI answers “where is my order”
When asked “where is my order”, “when will it arrive” or “has my parcel come”, AI first checks the parcel status. It takes the number from the customer's message, or, if there is none, looks among this customer's orders.
- The status comes from tracking if it was updated within the last 30 minutes. Otherwise Elbuz queries the carrier directly and keeps the answer for 5 minutes.
- The reply includes the parcel state, the carrier's status text, the branch, the expected date and how long the parcel is stored before the return. Nova Poshta provides the storage period.
- AI does not disclose the recipient's phone number or address.
- No waybill yet — AI replies that the parcel has not been shipped yet.
AI searches only the orders of the customer who wrote: by contact card, email or phone. For someone else's order number, AI replies that no such order was found among theirs. The reply goes out as a draft for an employee or as an auto-reply, depending on trust in “Pulse” (how AI prepares a reply).
Which notices the customer gets automatically
| Kind in the log | When it is sent | Text |
|---|---|---|
| “Waiting at branch” | within the last 24 hours the parcel moved to the “awaiting pickup” state | “Your order #… has arrived at the branch: …. Waybill: ….” and “Free storage until ….” if the storage period is known |
| “Return soon” | the parcel has been at the branch for 1 to 14 days and no more than “Remind” days are left until storage ends | “Reminder: order #… is waiting at … (waybill …). If not collected by …, it will be returned to the sender.” |
| “Review request” | a set number of days after delivery | see below |
- One notice of each kind per order.
- Elbuz checks orders every 30 minutes, together with the “Tickets” update.
- The “awaiting pickup” state is set by delivery tracking based on carrier statuses. Without tracking there will be no notices.
- The reminder needs the storage period, so it works with Nova Poshta.
- Texts are templates in the customer's language, with no AI. You change them in “Chat settings” → “Automatic message texts”, in the lines “Tickets: “parcel at the branch”” and “Tickets: reminder before return”.
If the customer never picks up the parcel, a manager may get a ticket “parcel is waiting at the branch, not picked up” — along with other order problems: refusal, non-payment, supplier delay. Learn more in Problem orders.
Where the notice goes
To the messenger of the customer's latest chat: Telegram, Viber and other channels connected to Elbuz. The website chat is not used. No chat — an email to the address from the order with the subject “Order #…”. Neither chat nor email — the log shows the “Error” status.
The language is the language of the customer's chat; for an email, the order language. If the customer has an open ticket, the notice appears in it as an event, so the employee sees that the customer has already been messaged.
How to set up proactive notices
Where: “Autonomous support” → “Channels and proactive” → the “Proactive notices” card. Changes take effect after you click “Apply”.
| Field | Default | What it sets |
|---|---|---|
| “Notice mode” | “Off” | “Test” — log entry only, “Live” — sending. The lower of this mode and the global mode applies |
| “Remind, days before return” | 2 | 0 — no reminder; up to 14 |
| “Per day, at most” | 200 | all proactive notices within 24 hours, up to 500 |
| “Quiet hours from … to …” | 21:00–09:00 | no proactive notices are sent during these hours, they go out afterwards; the same start and end time means no quiet hours |
| “Ask for a review, days after delivery” | 0 | 0 — don't ask |
During quiet hours the check is skipped, and notices go out with the first check after them. The daily limit also counts test entries.
1
Notice mode2
Remind, days before return3
Quiet hours- Notice mode — Off, Test or Live; in Test the log only records what AI would send.
- Remind, days before return — how many days before the parcel goes back the customer gets a reminder (0 means no reminder).
- Quiet hours — from and to times during which AI does not write to customers first.
How to check that notices went out
The “Notice log” card on the same tab shows the last 50: order, kind, channel, status and text.
| Status | What it means |
|---|---|
| “Test: would send” | “Test” mode, nothing was sent to the customer; the “Text” column shows what would have been sent |
| “Sent” | the notice was delivered to the messenger or the email was sent |
| “Error” | no contact, or the messenger or mail server refused; the reason is in the “Text” column |
| “Sending” | the entry has just been created |
A notice that failed is not resent: one notice per order and kind.
Review request
Set “Ask for a review, days after delivery” above zero. The customer gets “Thank you for your purchase! Order #… has been received — how do you like it? We would appreciate an honest review.” plus the link from “Where to leave a review”, if filled in. Marketplace orders are skipped. Next steps: reviews in tickets.
Scenarios
See what will be sent first
What to do. Set “Notice mode” to “Test” for a few days.
What you get. The log fills with “Test: would send” rows with ready texts. You can see whether branches and dates are correct and how many notices a day there will be, while customers receive nothing.
Fewer parcels returned
What to do. “Live”, “Remind” — 2.
What you get. The customer gets a notice on the day the parcel arrives and another one 2 days before free storage ends.
Branches open at 8:00
What to do. Set quiet hours from 22:00 to 08:00.
What you get. For parcels that arrived overnight, the customer sees the notice first thing in the morning, not at 3 a.m.
FAQ
I turned on “Live”, but no notices are sent. Why?
You also need “Autonomous mode” on, the policy applied, and the global mode set to anything but “Off”. Check delivery tracking too: without the “awaiting pickup” state there is nothing to notify about (conditions).
Can notices be sent by SMS?
No. Notices go to the messenger of the customer's latest chat or to the email from the order (channel).
Does AI write the notice texts?
No, these are templates without AI. You can change them in “Chat settings” → “Automatic message texts”.
Can AI see other people's orders if the customer gives an order number?
No. AI searches only among the orders of the customer who is writing, and for someone else's number it replies that the order was not found (AI reply).
The customer got a notice twice?
There won't be two identical ones: one of each kind per order. Two different ones — “arrived at the branch” and the reminder before the return — are intended.
Where to find it and who has access
- Menu
- Tickets → gear icon → “Autonomous support” → “Channels and proactive”
- Access rights
- the “Autonomous support” window
- Prepare
- delivery tracking in orders: the and carrier statuses
You don't need to turn on the “where is my order” answer: it always works in the AI responder in “Tickets”. Proactive notices require “Autonomous mode” to be on and the policy to be applied (autonomous support).
Related topics
- If you haven't turned on autonomous support yet — Autonomous support: how AI resolves typical tickets on its own.
- If the parcel isn't picked up and a manager is needed — Problem orders: a ticket for an order that needs a person.
- If the parcel is lost — How AI arranges an order reshipment.
- If the customer wants a different branch — How AI changes the Nova Poshta branch in an order.
- If the customer left a review — how to work with reviews in tickets.
