The helpdesk for online stores in Elbuz turns customer emails, chats that need a human, and calls into tickets in one queue and replies through the same channel.
When you need this:
- A customer emailed, wrote in Telegram, then called — it all joins their open ticket; the reply goes where they wrote last.
- Website form requests come from no-reply@ — the “Reply-To” address becomes the customer and gets the reply.
- A customer couldn't get through — the missed call becomes a “High” priority ticket.
- A buyer writes on a marketplace, posts a bad review or a comment — that's a ticket too.
Where to start: connect your customers' channels.
What ticket collection does
- Collects tickets from all connected channels — email, website chat, Telegram, Viber, Facebook, Instagram, WhatsApp and telephony; marketplaces, reviews and comments are turned on separately.
- Filters out what isn't a customer question — newsletters, supplier emails, conversations the bot handles.
- Merges one customer's channels into one open ticket instead of creating three.
- Recognizes website form requests and makes the “Reply-To” address the customer.
- Turns a missed call into a ticket with high priority and counts your callback as a reply.
- Sends the reply through the same channel — into the email thread, the same chat, the marketplace, under the review or comment.
What to connect for each channel
You don't need to turn ticket collection on. A channel connected in Elbuz is enough: tickets start appearing on their own, and on the first run Elbuz picks up messages from the last 14 days. Marketplace, review and comment channels, on the other hand, stay off until you turn them on.
| Channel in the ticket | What to connect | Details |
|---|---|---|
| Email, including website form requests | a mailbox in the “Mail” window | Connecting a mailbox |
| Website chat | the chat widget on your website | Live chat for your website |
| Telegram, Viber | a bot in “Chat settings” → “Set up channels” | Support bots: connection |
| Facebook, Instagram, WhatsApp | a channel via Meta sign-in in the same place | Instagram, Facebook Messenger and WhatsApp |
| Call | telephony | Telephony: connection |
| Rozetka, Allegro, Prom | the marketplace import template with credentials + a switch in “Autonomous support” | Marketplace messages |
| Review | “Live” mode in the “Negative reviews → tickets” card | Low-rated reviews |
| Facebook comment, Instagram comment | a switch in the Facebook or Instagram channel card | Comments on posts |
The label in the first column is what you'll see in the ticket's channel field and in the list filter.
When a message becomes a ticket
A ticket is a question a person needs to handle. A newsletter, a supplier email or a conversation the website bot handles on its own doesn't get into the support queue. Each channel has its own rules — email, chat, call.
One rule is shared: if the conversation already has an unclosed ticket, the new message is added to it instead of creating a second one. If the conversation is new, Elbuz looks for an open ticket of the same customer in other channels — see the next section.
- Start or end
- Action or result
- Decision: the path depends on the answer
“Problem order” is a separate channel: such a ticket is opened by Elbuz, not by the customer, when something is wrong with an order — the parcel isn't picked up, the payment failed, the supplier didn't ship. Customer messages aren't added to it. More details: Problem orders.
How one customer's channels merge into one ticket
An email, chat or call from a known customer is added to their open ticket if that ticket had activity within the last 3 days. A known customer is one Elbuz found among your contacts by chat, email or phone. No new ticket is created in that case.
The reply goes through the channel the customer used last. The ticket timeline shows the event “The customer wrote via another channel — the reply goes to: Telegram”, and the ticket's channel field changes.
Elbuz doesn't merge an unknown customer. If someone writes in Telegram without a phone number or email, Elbuz can't tell it's the same customer as in the email — you get two tickets. An agent merges them with the “Merge” button in the “Other tickets of the customer” block (how to merge).
To turn merging off, clear the “One customer — one open ticket” checkbox on the “General” tab of the support settings. Tickets from a review or a comment on a post are never merged: the reply is published under the review or comment, not in the customer's chat.
Which emails become tickets
An incoming email from a person in the “Inbox” folder becomes a ticket. Elbuz skips:
- emails from robots and newsletters — service notifications, emails from no-reply@ addresses, auto-replies;
- emails from colleagues (addresses on your domain) and senders on the ignore list — Mail marks them as automated on arrival;
- emails sorted into the “Suppliers”, “Partners & offers” or “Automated” categories, or into your own folder.
An email with no category, or in the “Sales” or “Customer service” category, becomes a ticket. Tickets from “Sales” go to the “Sales” department, all others to “Customer service”. The priority comes from the AI analysis of the email if the analysis set one; otherwise it's “Normal”.
If automatic AI analysis is on in Mail, an email waits up to 10 minutes for the analysis and only then becomes a ticket. This way an email that AI assigns to suppliers doesn't get into the support queue first. How Mail sorts emails: “Mail sorting”.
A customer's reply in the same email thread goes into the same ticket. Your reply sent directly from “Mail” also appears in the ticket: “New” changes to “Open”, and Elbuz records the first response time.
Website form requests
A website contact form usually sends the email as the website itself — from no-reply@ or an address on your domain — and puts the customer's address in the “Reply-To” field. Elbuz treats it as the customer's email: the Reply-To address becomes the ticket's customer and gets the reply, not no-reply.
The swap works only when the sender itself is an automated address and Reply-To holds a real external address. An email from an ordinary person with someone else's Reply-To stays that person's email: otherwise anyone could pose as your customer and get their order details in an AI reply.
Website chat and messengers
Only chats with customers count — the website widget, Telegram, Viber, WhatsApp, Facebook, Instagram. Internal staff messages in chat are ignored. A chat becomes a ticket when it needs a human. Elbuz decides so in three cases:
- the bot handed the chat over to an agent;
- an employee has already written in this chat;
- the bot never replied in this chat — for example, the AI consultant isn't turned on for the website.
A conversation the bot handles on its own doesn't become a ticket. As soon as the bot hands the chat to a human, the ticket appears — even if the customer hasn't written anything since the handover. The ticket subject is the customer's first question, up to 120 characters. Department — “Customer service”.
If an agent closes the chat in the “Chat dialogs” window, the ticket becomes “Solved” — provided the customer hasn't written anything after it was closed. How the bot hands a conversation to a human: “The “Chat dialogs” window: working as a manager”.
Calls: answered and missed
An incoming call, including a missed one, is added to the same customer's open ticket if it changed within the last 3 days. If the customer isn't in your contacts, Elbuz looks for a ticket with the same number. Nothing found — it creates a new one.
| Call | Subject of the new ticket | Counts as |
|---|---|---|
| Answered | the first sentence of the AI call summary: “Wants to change the delivery address for order 1452”; until there's a summary — “Call from +380…” | a reply: “New” changes to “Open”, the first response deadline is met |
| Missed | “Missed call from +380…”, “High” priority | a customer question that still needs a reply |
| Your outgoing call | doesn't create a new ticket | a reply in the open ticket of the customer or number changed within 3 days; otherwise it stays only in the call log |
The subject “Call from +380…” is replaced with the gist of the conversation automatically once telephony produces the AI summary — if that happens within the ticket's first 3 days. The summary itself becomes the message text in the timeline. This way the list shows what the customer wanted without replaying the recording.
What happens when the customer writes again
It depends on the ticket status:
| Ticket status | Customer writes by email or chat | Customer calls |
|---|---|---|
| “New”, “Open” | The message is added, the ticket becomes unread | Added if the ticket changed within 3 days |
| “Pending”, “On hold” | Added, the ticket is “Open” again — the timeline shows the event “The customer replied — the ticket is open again” | Added and reopened if the ticket changed within 3 days |
| “Solved” | Added, the ticket is “Open” again. A short “thanks” with no question doesn't reopen the ticket: the timeline shows the event “The customer said thanks — the ticket stays solved” (details) | New ticket |
| “Closed” | Email — a new ticket, the timeline shows “Follow-up of ticket #N”. Chat — the same, but only if the chat needs a human | New ticket |
New messages don't reopen a closed ticket: a new ticket arrives with a link to the old one. You can change a closed ticket's status manually — the status menu offers all six.
Where a reply from a ticket goes
A reply written in a ticket goes through the same channel the ticket came from and lands where the customer expects it. The ticket has no separate copy of the conversation: the timeline shows emails, chats and calls from their own windows.
| Ticket channel | Where the reply goes |
|---|---|
| as a regular email into the same thread; the email is saved in “Sent” | |
| Website chat, messenger | into the same chat; if you don't have access to the chat, Elbuz makes you its assignee |
| Call | you can't reply with a call from the window; if the customer's email is known — by email, otherwise a note and a status change |
| Rozetka, Allegro, Prom | into the marketplace conversation via its API — details |
| Review | as a reply under the review — details |
| Facebook comment, Instagram comment | under the comment or in a private message — details |
From a chat or call ticket, you can email the customer if their email is known. The subject of such an email is “Ticket #N: subject”. How to write a reply or a note and set the status: “Replying to the customer”.
Tickets are linked to “Mail” and “Chat” both ways. The header of an email or chat that belongs to a ticket shows the “Ticket #N” link. In the ticket itself, above the timeline, there are the “Open in Mail”, “Open in Chat” and “Open in the call log” buttons.
1
Ticket #1 link- Ticket #1 — a link in the sender line that opens the ticket created from this email.
If you assign someone to a chat ticket, they also become the assignee of the chat itself. The “Ticket #N” link is visible only to users whose department “Data scope” setting gives them access to that ticket.
How quickly a new ticket appears
A background task collects tickets every 5 minutes. While the “Tickets” window is open, it also checks for new messages every minute and updates the queue counters. The list you're working in isn't redrawn so you aren't interrupted mid-task: new rows appear when you switch to the queue or click “Refresh”.
An email reaches Elbuz when Mail has downloaded it, so the mailbox check interval adds to these intervals. Elbuz polls marketplace messages every 30 minutes; comments on posts arrive from Meta right away.
Scenarios
A customer emailed, and an hour later wrote in Telegram
The customer is in your contacts with email and phone, and the Telegram chat is linked to them. The Telegram message joined the email's ticket with the event “The customer wrote via another channel — the reply goes to: Telegram”. One reply from the agent reaches Telegram. Chat unlinked? Click “Merge” in “Other tickets of the customer”.
Website form requests come from no-reply@
The form sends the email from the website's address and puts the customer's address in “Reply-To”. The ticket is created for the Reply-To customer, and the reply goes to them. If the ticket is assigned to no-reply@, the form doesn't fill in Reply-To — that's set up on the website side.
A call was missed in the evening
The “Missed call from +380…” ticket with “High” priority is at the top of the queue. In the morning, the manager calls back through telephony — the outgoing call is added to this ticket as a reply, “New” changes to “Open”, and the first response deadline is met.
The store sells on Rozetka and on its own website
Email, website chat and messengers are collected automatically. To have Rozetka buyers' questions go into the queue too, with their own reply deadline, turn on Rozetka in the “Marketplace messages” card — how to do it.
What to do when a message didn't become a ticket
| What you see | Why | What to do |
|---|---|---|
| The customer's email is in “Mail”, but there's no ticket | The email is in the “Suppliers”, “Partners & offers” or “Automated” category or in your own folder, or AI analysis decided it isn't from a customer | Move the email to “Inbox” or “Customer service”, or pin the sender to the right folder (which emails become tickets) |
| The email arrived a few minutes ago, and there's no ticket yet | The email waits up to 10 minutes for AI analysis, and tickets are collected every 5 minutes (every minute while the window is open) | Wait or click “Refresh” in the queue (how quickly) |
| A customer is writing in chat, but there's no ticket | The bot is handling the conversation and hasn't handed it to a human | Write in the chat yourself or wait until the bot hands the conversation over (chat) |
| A website request became a ticket from no-reply@ | The form doesn't put the customer's address in Reply-To, or the email was marked as automated before the form rule applied | Set up the website form to write the customer's address in Reply-To (website form requests) |
| A customer wrote by email and in chat — two tickets | Elbuz didn't recognize the customer in the chat, the first ticket is solved or has had no activity for over 3 days, or “One customer — one open ticket” is off | Click “Merge” in the “Other tickets of the customer” block and link the customer to the ticket — further messages will merge automatically (channel merging) |
| The customer replied in an old thread, and a new ticket appeared | The old ticket is already “Closed” — closed tickets don't reopen | Nothing: the new ticket links to the old one with the event “Follow-up of ticket #N” (customer writes again) |
FAQ
Do I need to turn anything on for tickets from email and chats to start coming in?
No. A connected channel is enough: email, chat, a messenger or telephony. Only marketplaces, reviews and comments on posts need to be turned on separately (channel table).
Why didn't a supplier email become a ticket?
That's by design: a ticket is created from a customer email. Emails in the “Suppliers”, “Partners & offers” and “Automated” categories and in your own folders don't get into the support queue.
Does the customer see the ticket number?
When you email a customer from a chat or call ticket, the email subject is “Ticket #N: subject”. Replies through the same channel don't include the number automatically; you can insert it with a macro.
Can I reply to a customer in Viber from a phone ticket?
No, the reply goes through the ticket's channel. From a call ticket, you can send an email if the customer's email is known. When the customer writes in Viber themselves, the message is added to their open ticket, and the reply goes to Viber.
What happens to the ticket if I close the chat in the chat window?
The ticket becomes “Solved” if the customer hasn't written anything after the chat was closed. After 4 days with no reply from the customer, it closes automatically.
Will old emails and chats be pulled in?
On the first run — only messages from the last 14 days. Older history stays in “Mail” and “Chat”. To bring history over from another support system, use “Move to Tickets”.
Where it is and who has access
- Menu
- Directories → Contacts → Tickets; Organizer → Tickets
- Channel merging
- the window's gear icon → “Support desk settings” → “General” tab
- Access
- the “Tickets” window; support settings — “Management” department only
- Prepare
- at least one channel: email, website chat, a messenger or telephony
Related topics
- For an overview of the support desk — Tickets: overview.
- If buyers write on Rozetka, Allegro or Prom — Marketplace messages in tickets.
- If a ticket is already in the queue and needs a reply — Replying to the customer.
- If one customer's tickets don't merge or you need to change deadlines — Support desk settings.
