↑↓ selectEnter openEsc close

    1. Elbuz
    2. Autonomous support

    How AI handles customer order requests on its own

    6 min readUpdated

    Elbuz order management software handles typical order requests without staff: AI spots the request, the system checks the order against your rules, the customer replies “Yes”, and the order changes.

    When you need this:

    • “Cancel my order” in the evening: an unpaid order with no waybill is cancelled after “Yes”.
    • Another Nova Poshta branch: AI finds it from the message and updates the order.
    • A lost or damaged parcel: the warehouse gets an unposted order copy and a shipping task.
    • Fear of fraud: confirmation comes from a contact on the order or a one-time code.

    Where to start: set action types and limits on the “Policy” tab of “Autonomous support”.

    What AI can do with an order

    There are five action types. Each one is turned on separately and has its own article:

    • Order cancellation before shipping: an unpaid order is cancelled; for a paid one, a draft “Cash payment” is prepared for an employee.
    • Product return within the return period: an unposted return request, instructions for the customer, separate rules for defects.
    • Nova Poshta branch change before shipping, including re-creating the .
    • Reshipment of a lost or damaged parcel at the store's expense.
    • Compensation promo code for the next order after a delay or damage.

    What all types share is described here: customer confirmation, identity check, limits and undoing an action. AI never moves money: refunds are always issued by a person. Separately, you can send the order status to a marketplace.

    How an action runs: from request to result

    AI only chooses which action to offer. The amount, items, branch, deadlines and limits are calculated by the system from the order and the policy.

    1. The customer writes in a ticket: “cancel order 1234”, “I want to return the headphones”.
    2. The AI responder recognizes the request and passes the action type, the order and the reason to the system.
    3. The system runs the checks. If one fails, AI briefly tells the customer that an employee will review the request, or what is missing (city and branch number, photos).
    4. In “Test” mode everything stops here: “Test: would do” appears in the “AI actions” block, and nothing goes to the customer.
    5. In “Live” mode the customer gets a separate message asking “Yes” or “No”, and the ticket moves to the “Pending” status.
    6. After “Yes”, a confirmation code is sent if required.
    7. The system checks the order again: it may have changed while waiting.
    8. The action goes to “Pulse”. If the “Act on its own” trust is turned on there for this type, it runs at once (when AI acts on its own). Otherwise it waits for an employee's decision, and the “AI actions” block shows “Waiting for a decision in Pulse”.
    9. The customer gets the outcome: “Order #… has been cancelled”, the return request number, the new waybill.

    Every AI message is signed “Answered by the store's AI assistant” (how to change the signature). You can rewrite the questions and outcomes in “Chat settings” → “Automatic message texts”, in the rows starting with “Tickets:”. An empty field means the default text.

    What the system checks before asking the customer

    Checks run one by one until the first one fails. The list with marks is shown on the “Review” tab as “Check trace”.

    Action checks
    CheckFails if
    Modethe type is off, “Autonomous mode” is off, or the breaker of the type has tripped
    Support agent is on“AI · Support” is off or out of budget
    This customer's orderthe order belongs to another customer, it is not a customer order, or its source is not allowed
    Identity confirmed, or there is a channel for the codea code is needed but there is nowhere to send it
    Action conditionsspecific to each type: waybill, deadline, stock, markup
    Limitsthe order total or number of actions exceeds the limit
    Not a repeatthe same action for the order is already waiting or done
    The reason is not “people only”the customer mentions court or a legal claim, makes threats, or fraud or a payment dispute is suspected
    Test run checka money-related type in “Live” without a passed test run and without the “Enable without verification” checkbox

    The customer does not see reasons or thresholds: AI says an employee will review the request, or asks for what is missing, such as photos or a branch number. The employee sees the reason in the “AI actions” block as a “Reason: …” line. A refusal because the type is off is not recorded, so the ticket stays clean.

    How the customer confirms with “Yes” or “No”

    The question arrives as a separate message in the same channel the customer used: “Cancel order #1234 (Headphones +1, 2 450 UAH)? Reply “Yes” or “No”. This request is valid until 18.10 18:30.” The system parses the reply, without AI.

    How the system reads the reply
    Customer wroteWhat happens
    “Yes”, “yes, I confirm”, “+”, “так”the action is confirmed
    “No”, “no need”, “ні”“OK, order #… stays as it is”, the action is closed
    More than three wordsit is a new message: AI replies, the question keeps waiting
    Another order numberthe question is closed, AI handles the new request
    “Yes?”, “yes, but…”, anything unclearone follow-up asking to reply with one word; after a second unclear reply, it goes to an employee

    In an email, the question is followed by “Or confirm via the link”. The link opens a page with a “Yes, cancel the order” button (each type has its own). The customer can also reply “Yes” in the first line of the email.

    Deadline, reminder and a late “Yes”

    • The request is valid for 24 hours. To change this, go to “Autonomous support” → the “Action types” card → the “Wait for the customer's answer, h” field: from 1 to 168 hours.
    • Halfway through, the customer gets one reminder, unless it is quiet hours.
    • When the deadline passes, the action is closed and the customer gets a message that the request has expired. During quiet hours, no message is sent.
    • A “Yes” after the deadline does nothing: the customer gets the question again with the current amount and order state.

    One ticket, one question. A new action closes the previous wait, and so does an employee's reply to the customer.

    How the system checks that the order owner is writing

    Each type has an “Identity check” level. If the ticket channel provides less than required, the customer gets a one-time code after “Yes”.

    Identity check levels
    LevelWhat counts as confirmation
    “L0: no check”nothing: at this level AI only answers about the parcel status
    “L1: contact from the order”an email from the address on the order or the customer card; Viber or WhatsApp from the number on the order or card (the last 9 digits match)
    “L2: one-time code”the customer entered a code sent to the contact on the order or card, not to one given in the chat

    Telegram, Facebook, Instagram and website chat do not provide L1: there, an action with level L1 or L2 needs a code. By default, cancellation, return and promo code require L1; branch change and reshipment require L2. For a branch change, an email from the order address is enough for L1.

    Confirmation code

    • 6 digits, valid for 10 minutes, 3 attempts. No more than 3 codes per day to one address or number.
    • The customer sees where the code went: the email with asterisks or the last 4 digits of the number.
    • The channel is set by the “Identity confirmation code” list on the “Policy” tab: “By email” (default), “SMS only”, “SMS when possible, otherwise email”.
    • SMS is sent by the service selected in “External services and integrations” → “Рассылка SMS” (SMS sending), to the phone on the order or card. If the SMS fails, the code goes by email and an event appears in the ticket.

    A wrong code three times, an expired code, or no email and no phone: the request goes to an employee, and the customer gets “We have passed your request… to a store employee”.

    How to limit what AI does on its own, and how often

    Where: “Autonomous support” → the “Policy” tab → the “Action types” card.

    Each type has its own fields. A number above the system ceiling is cut down when you click “Apply”. Limits are counted by the system from the log of completed actions, not by AI.

    Default limits
    TypeAmount and countIdentity
    “Order cancellation”orders up to UAH 3,000; 5 per hour, 30 per dayL1
    “Return”up to UAH 2,000; 14 days from receipt; 2 per customer in 90 daysL1
    “Nova Poshta branch change”20 per day; more expensive delivery: UAH 0L2
    “Reshipment”up to UAH 1,500; 1 per order; 1 per customer in 90 daysL2
    “Compensation promo code”up to UAH 200 and up to 10%; 1 per customer in 90 daysL1

    There is also an overall limit: 40 completed actions of all types per hour. Exceeding it switches the type to “Suggest” (breaker).

    Order sources

    The “Order sources” field limits which orders a type works with: “Created in Elbuz”, “From chat”, “From the website”. The “Marketplaces (Rozetka, Prom, Epicentr)” option exists only for cancellation and is not selected by default: returns and delivery of marketplace orders are handled by the marketplace itself.

    How to monitor AI actions and undo an action

    Every action is shown in the “AI actions” block in the right panel of the ticket: what, for which order and in what state. The steps (question, code, confirmation, result) also appear as events in the ticket feed.

    Action states
    StateWhat it means
    “Waiting for “Yes” until …”the question was sent, the customer has not replied yet
    “Waiting for the code until …”the customer said “Yes”, the code is awaited
    “Waiting for a decision in Pulse”the customer confirmed, an employee must accept the action
    “Completed”the order was changed, the customer got the outcome
    “Passed to an employee”, “Error — passed to a human”a person takes it from here; the reason is on the line below
    “Declined by the customer”, “Confirmation expired”the customer replied “No” or did not reply
    “Paused: autonomy is off”“Autonomous mode” was turned off; the customer's “Yes” will go to a person
    “Test: would do”the type is in “Test” mode, nothing was sent to the customer
    The “AI actions” block in the ticket's right panel with one order cancellation waiting for “Yes” and one already done
    1Waiting for “Yes”
    2Done
    3Undo action
    4Take over
    1. Waiting for “Yes” — the customer has not confirmed the cancellation yet; the offer expires at the time shown.
    2. Done — the customer confirmed and the AI cancelled the order.
    3. Undo action — reverts the completed action.
    4. Take over — a person takes the ticket from the AI.

    “Undo action”

    The button reverts a completed action: the previous order status, deleting the unposted draft, disabling an unused promo code. Before reverting, a question shows exactly what will be reverted. An undone action automatically gets a “Bad” rating on the “Review” tab.

    You cannot undo if the order was changed after AI, the document is already posted or the promo code has been used. In that case you see what to do manually, for example “The refund order is already posted — undo manually”.

    “Take over”

    The button stops all AI waits in the ticket without notifying the customer and pauses AI in this ticket's chats. From then on, an employee handles the ticket. An employee's reply to the customer also closes the AI wait.

    How to send the order status to a marketplace

    Turn on “Send order status to the marketplace”. Then every status change of a Rozetka, Prom, Epicentr, EVA or Kasta order in Elbuz, whether by an employee, a flow or AI, goes to the marketplace in the background. The switch is off by default.

    Where: “Autonomous support” → “Channels and proactive” → the “Marketplace messages” card.

    • The marketplace status is taken from the status mapping of that marketplace's order import template.
    • API credentials come from the same import template.
    • If the marketplace already has the same status, it is not sent again.
    • An AI cancellation of a marketplace order always goes to the marketplace, even with the switch off (cancellation).

    The result of each transfer is recorded in the order history:

    Entries in the order history
    EntryWhy
    “Status sent to the marketplace: …”the marketplace accepted the status
    “Status not sent to the marketplace: “…” is not mapped to a marketplace status”this Elbuz status has no pair in the mapping
    “…the marketplace import template has no credentials”the template is turned off or has no key or login
    “Status … not sent to the marketplace: the marketplace requires a waybill for it”Rozetka does not accept “передано в службу доставки” (handed over to the carrier) without a waybill on the order
    “Status … not sent to the marketplace: …”the marketplace returned an error; its text follows the colon

    Scenarios

    A careful start

    What to do. Turn on “Order cancellation” in “Test” mode, and leave the trust in “Pulse” at “Suggest”.

    What you get. For a week AI only records “Test: would do”, and you compare it with employees' decisions on the “Review” tab. After switching to “Live”, customers confirm on their own, but an employee cancels the order with one button in “Pulse”.

    Customers write in Telegram

    What to do. Set “Identity confirmation code” to “SMS when possible, otherwise email” and choose a service in “External services and integrations” → “Рассылка SMS” (SMS sending).

    What you get. Telegram does not confirm identity, so after “Yes” the customer gets an SMS with a code to the phone on the order. Anyone without access to that phone cannot change the order.

    Large orders: people only

    What to do. In “Order cancellation”, set “Order total up to, UAH” to 1000.

    What you get. AI cancels orders up to UAH 1,000 after “Yes”; more expensive ones go to an employee with the reason “amount above the policy limit”.

    What to do when AI passes a request to an employee

    Reasons for handover to a person
    What you seeWhyWhat to do
    “no email for the confirmation code”the order and the card have no email (and for SMS, no phone or service)carry out the action manually; add the contact to the customer card
    “the order changed after confirmation”the status, amount or delivery changed between “Yes” and executioncheck the order and carry out the action manually, or ask the customer to write again
    “the answer is unclear after asking again”the customer twice replied with neither “Yes” nor “No”reply to the customer yourself
    “an employee rejected it in Pulse”the action was rejected in “Pulse”explain the decision to the customer
    “the breaker of this action tripped”errors in a row, the hourly limit, or “Bad” ratingsgo through the “Review” tab and restore the type on the “Actions and trust” tab
    ““AI · Support” is off or out of budget”the agent was turned off or its daily budget ran outturn the agent on or increase the budget

    FAQ

    I turned on an action type, but AI does nothing. Why?

    An action starts only when “Autonomous mode” is on, the policy is applied, and the mode is “Live” at the general, type and channel level. The lowest of them applies (modes).

    Can AI refund a customer?

    No. For a paid order, only an unposted draft “Cash payment” is prepared, and only an employee can post it (cancellation).

    The customer replied “Yes”, but the order is not cancelled. Where is it?

    Most often the action is waiting in “Pulse”: the “Act on its own” trust is not turned on for the type. The state is shown in the “AI actions” block (action flow).

    Can I change the 24-hour deadline for the customer's reply?

    Yes: “Autonomous support” → the “Action types” card → “Wait for the customer's answer, h”, from 1 to 168, then “Apply”. The deadline applies to all types; the reminder comes halfway through (deadlines).

    What does the customer see if the action cannot be carried out?

    A short AI reply without thresholds or internal rules: an employee will review the request. The reason for the employee is in the “AI actions” block.

    Can I change the text of the “Yes/No” question?

    Yes: “Chat settings” → “Automatic message texts”, the rows starting with “Tickets:”. An empty field restores the default text.

    Where to find it and who has access

    Menu
    Directories → Contacts → Tickets → the “Support desk settings” gear → “Autonomous support”
    Actions in a ticket
    the ticket card, right panel, “AI actions” block
    Access right
    the “Autonomous support” window in group permissions; decisions in “Pulse” need the right to “Pulse”
    Prepare
    “Autonomous mode” turned on and the policy applied (autonomous support)

    Actions are carried out by the virtual employee “AI · Support”. If it is turned off or its daily budget is used up, no action starts: the request goes to a person.

    Policy tab, “Action types” card: identity confirmation code and the first action type, “Order cancellation”
    1Identity confirmation code
    2Action type mode
    3Order total limit
    4Identity check
    5Order sources
    1. Identity confirmation code — how the customer receives the one-time code (by email, SMS, or SMS with email fallback).
    2. Mode chips (Off / Test / Live) of this action type.
    3. Order total limit: AI cancels only orders up to this amount.
    4. Identity check — the level of customer verification required before the action (none, contact from the order, one-time code).
    5. Order sources — which orders AI may touch: created in Elbuz, from chat, from the website.

    Related topics

    Was this article helpful?

    Missing a feature? Tell us.

    We will add it for free if other users need it too.

    If only you need it, we will agree on it separately.

    Article contents

    Suggest an improvement

    Try Elbuz free