Elbuz sends your reply where the customer wrote, to the same email thread or chat, and moves the ticket to the right queue itself: no separate closing.
When you need this:
- Chat customer needs a document — “Email to …” emails them; their reply returns to the ticket.
- You replied and wait — it returns when the customer writes.
- A daily repeat question — a macro adds the customer's name and tracking number.
- A colleague or the warehouse knows — a note with an @mention or an email to the supplier, hidden from the customer.
Where to start: open a ticket, press R and type — where the reply goes.
What replying from a ticket can do
- Reply via the same channel — an email to the same thread, a message to the same chat; “Email to …” emails a customer who came from chat or a call.
- “Send as” — the status is set together with the reply, no separate closing needed.
- Macros — ready-made text with the customer's name, order number and number.
- Note and @mention — a message for colleagues that notifies whoever you mention.
- “Is replying” — you can see that a colleague is already answering this customer.
- Email to a supplier or the warehouse — the third party's reply arrives in the ticket.
- “Take next” — Elbuz gives you the ticket with the nearest deadline.
AI can draft the reply from the customer's orders and your knowledge base — the “AI draft” button or the G key (“AI in tickets”).
Where the reply goes
The field at the bottom of the ticket in “Reply” mode sends your text to the customer where they wrote from. Below the field you see exactly where: “The reply will go out via: Email”, “… Telegram” and so on. To send, click “Send” or press Ctrl+Enter.
| The ticket came in | Where the reply goes | What you'll see afterwards |
|---|---|---|
| By email | As a reply to the customer's last email in this ticket — in the same email thread | The email in Sent mail and in the ticket feed |
| Via website chat or a messenger | To the same chat. If you don't have access to the chat, Elbuz makes you its assignee | The message in the chat and in the feed |
| By phone | There's no reply via the channel: “Email to …” if the customer's email is known, otherwise only a note | — |
| From a marketplace, as a review, as a social media comment | To the marketplace, under the review or under the comment; for a comment there's also “Private reply” | See the articles on marketplaces, reviews, comments |
If the reply doesn't go out, Elbuz shows “Could not send”, and the ticket's status and assignee stay the same — you can send it again.
The customer wrote via another channel
The customer emailed, then wrote in Telegram while you were replying. No new ticket appears: the message joins the same ticket, and the feed shows “The customer wrote via another channel — the reply goes to: Telegram”. The caption under the field changes to “The reply will go out via: Telegram” — the reply goes where the customer is now.
This works when Elbuz knows the customer (they're linked to the ticket or were found by email or phone) and the ticket is open, with activity in the last 3 days. If you still want to reply by email, use “Email to …”.
What the feed shows
The feed above the field collects the whole conversation in time order:
- customer messages, your replies (“We” or the employee's name), AI bot replies in chat, internal notes and events — status and assignee changes, applied macros;
- emails — without the quoted earlier conversation, since it's already visible above;
- three or more system events in a row collapse into “Show N more events”; messages between them aren't lost;
- above the feed — “Open in Mail”, “Open in Chat” or “Open in the call log”; the “Ticket #N” link leads back from “Mail” and “Chat”.
“Email to …”
In a ticket from chat or a call there may be one more toggle above the field — “Email to customer@address”. It appears if the address is known: from the customer card, or from the ticket contact when that contact is an email. What happens:
- a new email goes out from your mailbox with the subject “Ticket #N: ticket subject”;
- the email is linked to the ticket even before sending, so the customer's reply to it arrives in this same ticket;
- the ticket channel doesn't change: the next “Reply” goes to the chat again.
When you need it: the customer left the website chat, and you need to reply with a document, a long text or an attachment, or the ticket came from a call and the customer asked for an invoice. When you don't: the customer is still in the chat — they'll see a chat reply sooner.
1
Reply mode tabs2
Reply channel hint3
Send as4
Macros- “Reply” goes to the customer, “Email to …” sends from your mailbox, an internal note is visible to colleagues only.
- Shows exactly which channel the reply will go through.
- The ticket status after sending; “Pending” by default.
- Ready-made texts with variables (hotkey M).
Which status to set after replying
Next to the “Send” button is the “Send as” list: “Open”, “Pending”, “On hold”, “Solved”. The default is “Pending”. The status is set only after the reply has gone out; if sending fails, the status stays as it was.
| Situation | “Send as” | What happens to the ticket |
|---|---|---|
| You replied and are waiting for the customer's reaction | “Pending” (leave as is) | Leaves “My open”, the deadline is paused; returns when the customer writes |
| You gave a final answer (“Tracking number such-and-such, have a nice day”) | “Solved” | Closes on its own after 4 days of silence |
| You promised to check with the warehouse or the supplier | “On hold” | Stays in your queues, the deadline keeps running — the ticket won't get lost |
| You sent an interim reply and keep working on it yourself | “Open” | Stays in progress |
Your first reply removes the “New” status. If the ticket had no assignee, the person whose reply reached the customer first becomes the assignee. When you reply in chat, you become the assignee of the chat itself before sending — otherwise Elbuz won't let the reply into the chat.
You can also change the status separately — with the chip in the ticket header (the S key). How statuses change from one to another is covered in “Working with tickets as an agent”.
How “Pending” pauses the deadline
Every ticket in progress has a deadline — a stopwatch chip in the list row and in the header. What the color means:
- gray “3 h 10 min left” — how much time is left;
- yellow “25 min left” — less than 30 minutes left;
- red “2 h overdue” — how long ago the deadline passed; the ticket is already in the “SLA breached” queue.
The chip tooltip tells you which deadline is nearest: “first reply”, “next reply” or “resolution”, and by what time. Deadlines are counted in business minutes according to the schedule set by the manager.
While a ticket is “Pending”, there's no chip: the deadline isn't shown and can't be breached. The business minutes spent waiting are added to the resolution deadline when the status changes. The “next reply” deadline starts over from the customer's message.
Example: the resolution deadline is 8 business hours. You replied after 2 hours and set “Pending”; the customer replied two business days later. The ticket returns to “Open”, and the same 6 hours remain until the resolution deadline.
“On hold” doesn't pause the deadline: while you wait for the warehouse or the supplier, the customer is waiting for you. How to set deadlines and escalation is covered in the article on SLA deadlines.
What happens after “Solved”
You set “Solved” yourself: via “Send as”, with the status chip or by dragging the card on the board. A chat ticket also becomes “Solved” when an agent closed the chat in the chats window and the customer hasn't written since.
| What happens next | What Elbuz does |
|---|---|
| The customer replied within 4 days | The ticket is “Open” again and unread; the feed shows “The customer replied — the ticket is open again”. The assignee stays the same |
| The customer just said thanks (“Thank you!”, “ok, got everything 👍”) | The ticket stays “Solved”, doesn't return to your queues; the feed shows “The customer said thanks — the ticket stays solved” |
| 4 days of silence | Elbuz sets “Closed” on its own |
| The customer wrote about a closed ticket by email or called | A new ticket, with “Follow-up of ticket #N” in its feed |
| The customer wrote about a closed ticket in chat | A new ticket, if the chat needs a person; a conversation handled by the bot doesn't become a ticket |
Elbuz treats a short message (up to 80 characters) with no question mark and no words like “but”, “more”, “doesn't work” as thanks: “Thanks, but it's the wrong parcel” reopens the ticket like a normal reply. Without this, every “thanks” would put the ticket back in progress and restart the deadline.
If the manager has turned on customer ratings, switching to “Solved” sends the customer a request to rate the reply — once per ticket. Ratings are off by default (“Reports and customer ratings”).
Setting “Closed” manually rarely makes sense: you only take away the 4 days during which the customer's reply returns to the same ticket.
How to reply with a macro
A macro is a ready-made reply text plus the status it's sent with. To open the list: the “⚡ Macros” button, the M key or “/” in an empty reply field. The most frequently used macros are at the top of the list.
What choosing a macro does:
- the text goes into the reply field; if something is already there, the macro is added below after a blank line;
- variables are replaced with the ticket's data;
- the macro's status is set in “Send as” — the ticket changes status only when you send the reply;
- nothing is sent automatically: you can edit the text before sending.
Macros moved from Zendesk and other systems can also have actions — change priority, assignee, department, add tags. These actions run as soon as you choose the macro, even if you don't send the reply afterwards.
| Variable | What it's replaced with |
|---|---|
| {CUSTOMER_NAME} | The first word of the customer's name: from the ticket, or from the customer card if the ticket has none |
| {TICKET_ID} | The ticket number |
| {AGENT_NAME} | Your name |
| {LAST_ORDER_NUMBER} | The number of the customer's last order |
| {LAST_ORDER_STATUS} | The status of that order |
| {LAST_ORDER_TTN} | The tracking number of that order |
Order variables take the customer's latest order by date; invoices and returns don't count. In a ticket without a customer these variables are empty. If the customer asks about an older order, take the tracking number with the “Add tracking to reply” button in the right panel (customer orders).
Your own macro
Type the text in the field, choose “Send as” and click “Save the text as a macro” in the macros menu. It keeps the text with variables and the status. By default a macro is personal: only you see it. The “For all employees (otherwise only yours)” checkbox makes it shared. Don't share macros containing a specific customer's data.
“Delete macro” is a submenu with the list, with confirmation; a deleted macro can't be restored. A macro can be edited or deleted by its author; a shared one also by an employee with the “Management” right on the window.
1
Macro2
Save the text as a macro3
Delete macro- Clicking a macro inserts its text and sets the status in “Send as”; nothing is sent.
- Saves the field text together with its status; by default only for you.
- Deletes the macro with no way to restore it.
How to call in a colleague with a note
The “Internal note” toggle (the N key) above the field turns your reply into a message for colleagues. The customer doesn't see it: a note isn't emailed or posted to the chat, and the feed marks it with an “Internal note” badge. The button changes to “Save note”, and “Send as” disappears: a note doesn't change the status.
To call in a colleague, type @username in the note — the login they use to sign in. Case doesn't matter. The colleague gets the notification “Name mentioned you in ticket #N” with the first 160 characters of the note and an “Open” button that opens this exact ticket. Mentioning yourself, disabled employees or AI employees doesn't send a notification.
When you need a note: you're handing over a ticket and explaining what's been done; you're asking a colleague in accounting to check a payment; you're leaving yourself a reminder. When you don't: to write to the customer — use “Reply” mode for that.
How to avoid two people replying to one customer
In the ticket header, next to the channel and date, you see markers for colleagues who have opened the same ticket: “Name is viewing” or “Name is replying”. Elbuz updates them every 15 seconds and shows those who were in the ticket within the last 40 seconds.
“Is replying” appears when a colleague was typing a reply to the customer within the last 20 seconds, and can stay for another half minute after they stop. Typing a note isn't shown to colleagues.
If you click “Send” while someone “is replying”, Elbuz asks: “Name is replying to this ticket right now. Send yours anyway?”. This is a warning, not a lock: “Send” sends your reply, and the customer may get two. It's safer to click “Cancel” and agree with your colleague in a note. The warning doesn't apply to notes.
How to ask a supplier or the warehouse
The customer asks about an out-of-stock product, the warranty or a wrong item — the supplier or the warehouse knows the answer. You don't need to write to them separately from “Mail”: the “⋯” menu in the ticket header → “Write to a supplier / warehouse”.
In the form, find the contact (the search shows only those with an email) or enter the address in “To (email)”. The default subject is “[Ticket #N] ticket subject”; you can change it. What happens after “Send”:
- the email goes out from your mailbox; the ticket feed shows “Email to supplier” and the event “name: email to a supplier / warehouse (address)”;
- when the supplier replies in the same thread, the reply arrives in this ticket on its own with a “Supplier reply” badge, and the ticket assignee gets the notification “Ticket #N: reply from …”. A ticket without an assignee sends no notification;
- the customer doesn't see this conversation: it isn't sent to them and doesn't go into the AI reply draft;
- the ticket's status and deadline don't change. If you're waiting for the supplier's reply, set “On hold” yourself.
The reply is linked by the email thread. If the supplier sent a new email rather than a reply, it takes the normal mail route — into the “Suppliers” category or wherever the rules put it.
How to take the next ticket when yours are done
When the “My open” queue is empty, instead of the list you see “No tickets in this view” and the “Take next” button. Among “New” and “Open” unassigned tickets, it finds the one with the nearest deadline (overdue ones first), makes you the assignee and opens it right away.
- It searches the tickets “Data scope” lets you see, from any department.
- The feed shows the usual assignment event.
- If there's nothing to take, Elbuz says “No unassigned tickets — all taken”.
Why: you don't have to open “Unassigned” and decide where to start — the button takes the ticket where the customer risks waiting longest.
Scenarios
“Where is my order?” by email
On the right, “Recent documents” shows the order and its status. Click “Add tracking to reply”, write the text around the number, choose “Solved” in “Send as” and send. The email goes to the same thread, and the ticket closes on its own after 4 days if the customer doesn't reply.
A question the warehouse answers
The customer asks whether the product comes in another color. Reply to the customer “checking” with “Send as” — “On hold”. Then “⋯” → “Write to a supplier / warehouse”. When the warehouse replies, you get a notification, and the reply appears in the feed. Write to the customer — this time with “Solved” or “Pending”.
A website chat customer asks for an invoice
The ticket is from chat, and the customer has an email. Choose the “Email to …” toggle, write the text and send: the customer gets an email with the subject “Ticket #N: …”, and their reply arrives in the same ticket. The next normal reply goes to the chat again.
Check a payment with accounting
The customer says they've paid, but the order shows no payment. Write the note “@olena please check the payment from 12.10” and reply to the customer “checking” with “On hold”. Your colleague gets a notification with the note text and replies with a note in the same ticket.
A typical question for the tenth time today
Save the reply as a macro with the {CUSTOMER_NAME} and {LAST_ORDER_TTN} variables and the “Solved” status, with the “For all employees” checkbox. After that — “/” in the empty field, choose the macro, Ctrl+Enter.
What to do when a reply didn't go out or went wrong
| What you see | Why | What to do |
|---|---|---|
| “Could not send” | The channel didn't accept the message: the mailbox didn't send the email, the chat is unavailable; an email ticket has no customer email at all | Check the channel in “Mail” or “Chat”. The status hasn't changed — send again (where the reply goes) |
| No “Reply” mode, only a note | The ticket came from a call, and the customer's email is unknown | Call back or link a customer who has an email — “Email to …” will appear (linking a customer) |
| The customer got two replies | Two agents replied at the same time and confirmed the “is replying” warning | Use “Take it” before replying; click “Cancel” on the warning (avoid replying twice) |
| The customer replied — and the chip is red right away | The ticket was waiting in “On hold” or “Open”, not “Pending”: the resolution deadline kept running all that time | After replying to the customer, leave “Send as” on “Pending” (deadline) |
| A colleague didn't react to a ticket | They missed or dismissed the assignment notification | Mention them in a note with @username — a second notification arrives, with the note text (note) |
| The macro inserted the wrong order number | Order variables take the customer's last order, but the customer is asking about an earlier one | Check the number in “Recent documents” and take the tracking number with “Add tracking to reply” (macros) |
FAQ
Why did the ticket disappear from “My open” after I replied?
By default a reply goes out with “Send as” — “Pending”, and such tickets live in the “Pending” queue. When the customer replies, the ticket returns to “Open” and to “My open”.
Will the customer see an internal note?
No. A note goes neither by email nor to the chat and is marked in the feed with an “Internal note” badge. The customer doesn't see the conversation with the supplier from the ticket either.
How do I reply by email to a customer who wrote in chat?
Choose the “Email to …” toggle above the field. It's there if the customer's email is known from the customer card or from the ticket (details).
The macro inserted an empty name. Why?
The name is taken from the ticket, or from the customer card if the ticket has none. A ticket with no name and no linked customer leaves a blank. Link the customer in the right panel and apply the macro again.
The customer wrote “thanks” in a solved ticket, and it didn't reopen. Is this a bug?
No. A short thank-you without a question keeps the ticket “Solved” (what happens after “Solved”). In “Pending”, any message, including thanks, returns the ticket to “Open”.
Can I call the customer from a ticket?
No, a ticket accepts an email reply or a note. Call from the customer card or the call log; Elbuz counts an answered incoming call as a reply on its own.
Can I stop a colleague from replying while I'm replying?
No, Elbuz only warns that someone “is replying”. Use “Take it” before replying so colleagues see the assignee (avoid replying twice).
Where it is and who has access
- Menu
- Organizer → Tickets → a ticket in the list → the field at the bottom
- Other ways in
- the “Ticket #N” link in the header of an email in “Mail” or of a chat
- Access right
- the “Tickets” window in “Group permissions”; a ticket that “Data scope” allows you to see
- Prepare
- a connected mailbox — for “Email to …” and emails to suppliers
Related topics
- If you need the big picture of the workspace — “Working with tickets as an agent”.
- Not sure which ticket to open next — “How to work through the ticket queue”.
- The reply depends on the customer's order — “Customer and orders in a ticket”.
- Want AI to prepare the draft — “AI in tickets”.
