Elbuz finds the customer by the ticket's email or phone and shows their orders and other tickets alongside: you can reply without opening contacts and documents separately.
When you need this:
- A customer asks about their order: recent documents, their stage and “Add tracking to reply” are on the right.
- An unknown contact writes in: search or “Create a customer from this contact” links the ticket; later messages join it.
- The same customer opened two tickets: “Merge” brings the conversation together.
- AI has already acted on an order: the “AI actions” block shows what; you can undo it.
Where to start: open a ticket and look at the right panel.
What the customer panel does
- Link a customer: by searching or by creating one from the ticket's contact, with no duplicates in contacts.
- Change the customer: “Change” if the wrong one was linked.
- Recent documents: the customer's five latest documents, “Next: stage” and “Add tracking to reply”.
- “AI actions”: what autonomous support did with the order, plus “Undo action” and “Take over”.
- Merging: two tickets from the same customer become one.
What the right panel shows
The panel follows the order in which an agent usually looks for an answer:
- “Customer”: name, email, phone, group, “Customer card” and “Change”. No customer: search and create.
- “AI asks” and “AI actions”: only when autonomous support has asked you a question or done something with an order (details).
- “Recent documents”: where the customer's orders stand.
- “AI · Support”: AI's analysis of the ticket: what it is about, the tone, what it relies on, what AI suggests doing (“How AI prepares a reply to a customer ticket”).
- “Other tickets of the customer”: the five latest; a click opens the ticket.
Once AI's analysis is ready, its gist in one line (with a magic wand icon) also appears in the header, under the ticket subject: you see what the customer wants before you read the message.
When the window is narrow, the panel hides and a “Customer” button appears in the header: it slides the panel out over the conversation, and a click on the conversation hides it again.
1
Customer card2
Change3
Other tickets of the customer4
Merge- Customer card — the full counterparty card with history.
- Change — link the ticket to another customer.
- Other tickets of the customer — the customer's latest tickets.
- Merge — moves the current ticket into that one, irreversible.
How to link or change the customer
Elbuz looks for the customer on its own, by the ticket's email or phone. If it finds no one, or finds two similar customers and doesn't guess, the panel shows “The customer is not in the contacts directory” and offers two ways:
- Search “Name, email or phone”: from 2 characters, a phone from 5 digits, up to 8 results. You only see the customers your contact list allows. A click on a name links the ticket right away.
- “Create a customer from this contact”: creates a customer with the ticket's name and email or phone. If a customer with that email or phone already exists, Elbuz links the existing one instead of creating a duplicate.
Linking reaches beyond one ticket:
- other tickets with the same contact and no customer yet are linked to that customer too;
- the event “name: customer — name” appears in the conversation;
- when the customer writes again from any channel where Elbuz recognizes them, the message is added to their open ticket instead of creating a new one (the customer wrote on another channel).
The wrong customer is linked
Click “Change” next to the customer and find the right one with the same search. The ticket moves to the new customer, and a new event “name: customer — name” appears in the conversation. Other tickets already linked to the previous customer don't change: change each of them separately.
1
Customer is not in the contacts directory2
Customer search field3
Search result- The program did not find the customer by the contact or found two similar ones.
- Search starts from 2 characters, a phone from 5 digits.
- Clicking a result links the ticket and the other tickets with the same contact.
How to work with the customer's order
“Recent documents” lists the customer's five latest documents of any type: number, amount, date, status. If there are none, you see “No documents”. A document can have two buttons under it:
- “Next: stage” moves the document to the next stage immediately, without confirmation, just like “Next stage” in the document itself, with all the triggers and flows set up for that transition. Click it only when you have actually done that step, for example shipped the order.
- “Add tracking to reply” inserts the number into the reply field (appended at the end). It sends nothing: write the text around the number yourself.
A click on the document number opens the document. “Customer card” opens the contact card with the full history.
In the “AI · Support” block, AI can suggest its own order actions: move to a stage, create a return, insert the tracking number. Unlike “Next”, they ask for confirmation before running. How they work is covered in “How AI prepares a reply to a customer ticket”.
What AI did with the order
With autonomous support turned on, AI handles typical customer requests itself: cancel an order before shipping, change the delivery branch, create a return. Everything it did in this ticket is listed in the “AI actions” block of the right panel. Autonomy is off by default, and then there is no block.
- A row shows what exactly (“Cancel order #…”), when, and a status badge: “Waiting for “Yes” until …”, “Done”, “Test: would do”, “Passed to an employee” and so on.
- “Reason: …” explains why AI didn't do it itself and handed it to a person, for example “has a waybill — handed to the carrier”.
- “Undo action” reverts what was done: Elbuz asks first and says what it will revert, for example “Return order #… to its previous status (the reservation comes back)…”.
- “Take over” is shown while AI waits for the customer's reply: it stops the waiting, you handle the customer yourself, and AI pauses in the customer's chat.
If AI needs a colleague's answer, “AI asks” appears above the block: the question, who it's for and the deadline, answer options as chips, and a “Your answer (up to 2000 characters)” field. After “Answer”, AI continues its reply to the customer. How to set up autonomous actions is covered in the article on autonomous order actions.
1
AI action row with status badge- What the AI did or was going to do, and at which step.
How to merge two tickets
Usually an email, a chat and a call from a known customer end up in one ticket on their own. You get two tickets when Elbuz didn't recognize the customer (for example, in Telegram without a phone or email), or when the first ticket is already resolved or has had no activity for over 3 days.
You don't need to look for such pairs yourself. When you open an unclosed ticket and the customer has another open one (if the customer isn't recognized, one with the same email or phone), a hint appears above the conversation: “Looks like the same question: the customer already has open ticket #N “subject”…”.
“Merge” moves the current ticket into #N; “Open #N” just opens the other one. If the questions are different, don't click anything.
Three more ways to do the same:
- in the right panel, under “Other tickets of the customer”: “Merge” next to an unclosed ticket (tooltip “Same question: move this ticket into #N”);
- the “⋯” menu in the header → “Merge into another ticket” → “Merge into ticket #N” or “Enter a ticket number…” for any ticket your “Data scope” lets you open;
- several tickets at once: the bulk actions bar in the list; they are merged into the oldest one.
Elbuz asks: “Emails, chats and calls of this ticket will move to #N and this ticket will be closed. Continue?”. What happens:
- emails, chats, calls, notes, supplier correspondence and history imported from another help desk move to the target ticket; the event “name: ticket #N merged in” appears there;
- other events (status and assignee changes, applied macros) stay in the old ticket;
- the old ticket becomes “Closed” with a “Merged into ticket #N” link and leaves the queues; a search by its number still finds it;
- if the target ticket had no customer, it takes the customer from the old one;
- the target ticket's assignee doesn't change; “Solved” or “Closed” becomes “Open”, since live correspondence has just arrived there.
When not to merge: the customer writes about two different orders. Two questions, two tickets, each with its own status and deadline.
Scenarios
One customer, two tickets
A customer wrote on Viber without a phone, then sent the same by email, and Elbuz created two tickets. Open the Viber ticket, link the customer by searching, then under “Other tickets of the customer” click “Merge” next to the email ticket. Reply from the email ticket: further Viber messages will go there on their own.
A new buyer writes for the first time
The panel shows “The customer is not in the contacts directory”. Click “Create a customer from this contact”: the customer appears in contacts with the ticket's name and contact, and their next tickets are linked automatically.
The customer asks when the order ships
The warehouse has just shipped the order, but in “Recent documents” it is still at the previous stage. Click “Next: …” with the next stage's name, then “Add tracking to reply”, finish the text and send it with “Solved”.
AI cancelled the wrong order
The customer writes that they asked to cancel a different order. In “AI actions”, next to “Cancel order #…”, click “Undo action” and confirm: the order returns to its previous status. Then handle the customer yourself.
What to do when the customer or ticket is wrong
| What you see | Why | What to do |
|---|---|---|
| The ticket is linked to the wrong customer | Someone linked the wrong customer by hand, or the ticket's email or phone is saved in another customer's card | “Change” next to the customer, then search for the right one (the wrong customer is linked) |
| The customer is in contacts, but the panel shows “The customer is not…” | The ticket's contact didn't match the card or matched two customers | Find the customer by name with the panel search (linking) |
| The customer search finds nothing | Fewer than 2 characters or 5 phone digits, or the customer is outside your contact list | Type more characters; if outside your list, ask a colleague with access |
| No “Next: …” button under the document | The document has no next stage | Open the document by clicking its number and change the stage there |
| Merging by number fails | Your “Data scope” doesn't let you open the ticket with that number | Ask a colleague who can see both tickets to merge them |
| The ticket disappeared after merging | It was closed, and its correspondence moved to the target ticket | Find it by number: the “Merged into ticket #N” link leads to the target ticket |
FAQ
Can I undo a ticket merge?
No. The correspondence moves to the target ticket and the old one is closed; there is no “unmerge” button (merging).
Will “Create a customer from this contact” create a duplicate?
No. If a customer with that email or phone already exists, Elbuz links the existing one.
I changed the customer. Why did the other tickets stay with the previous one?
“Change” applies only to the open ticket. Change the other tickets one by one.
Why doesn't “Recent documents” show all of the customer's orders?
The panel shows the five latest documents of any type. The rest are in the “Customer card”.
Can I cancel an order from a ticket?
Manually, in the document itself (click its number). AI cancels automatically if autonomous support is on; you can revert its action with “Undo action” (“AI actions”).
Where is the right panel? I only see the conversation.
The window is narrow, so the panel is hidden. Click “Customer” in the ticket header or widen the window.
Where to find it and who has access
- Menu
- Organizer → Tickets → a ticket in the list → right panel
- Narrow window
- the “Customer” button in the ticket header
- Access right
- the “Tickets” window; you see the customers your contact list allows
- Prepare
- access to documents, for “Next: stage” and order actions
Related topics
- For the big picture of the workspace, see “Working with tickets as an agent”.
- The customer is found and it's time to reply: “How to reply to a customer in a ticket”.
- Want AI to cancel orders and change branches on its own? See autonomous order actions.
- How the stages switched by “Next” work: “Processing customer orders”.
