↑↓ selectEnter openEsc close

    1. Elbuz

    Tickets: customer emails, chats and calls in one queue

    4 min readUpdated

    The helpdesk for online stores in Elbuz turns customer emails, chats, messages and calls into tickets: one queue with a number, assignee and reply deadline. Replies go out through the customer's channel.

    When you need this:

    • Everyone thinks a colleague answered the shared inbox — Elbuz assigns the ticket to an agent.
    • A customer emailed, then used Telegram, then called — one ticket, one reply.
    • A customer has waited two days — the overdue ticket goes to the “SLA breached” queue, notifying the assignee and their manager.
    • The manager can't see who replies how — the report shows deadlines and ratings per person.

    Where to start: the first-run checklist.

    What “Tickets” can do

    What a ticket is

    A ticket isn't a copy of an email or a chat — it's a card on top of them. It stores the number (#125), customer, channel, status, priority, assignee, department, tags and reply deadline. The messages themselves stay where they arrived: an email in “Mail”, a conversation in “Chat”, a call recording in the call log.

    The “Tickets” window shows them in one timeline, together with colleagues' internal notes and events: who changed the status, who the ticket was handed to, when the customer replied. An email you answered in “Mail” appears in the ticket automatically. You can't delete a message from a ticket — it lives in its own channel.

    A ticket has six statuses: “New”, “Open”, “Pending”, “On hold”, “Solved” and “Closed”. Your reply moves “New” to “Open”; a customer reply moves “Pending” and “Solved” back to “Open”; and “Solved” with no customer reply becomes “Closed” after 4 days. How to work with statuses: “Replying to a customer”.

    The Tickets window: queues on the left, ticket list in the middle, open ticket on the right
    1Queues
    2Ticket row
    3Ticket timeline
    4Reply box and Send as
    1. Queues — switch between views such as My open, Unassigned, SLA breached and All tickets.
    2. Ticket row — number, subject, customer, status and deadline chips; the selected ticket is open on the right.
    3. Timeline — the customer's message, an internal note and system events in one feed.
    4. Reply box — choose Reply or Internal note, and the status to send as.

    Where tickets come from

    A ticket is created from an email sent by a person (not a newsletter or a supplier email), a chat that needs a human, and a call, including a missed one. There's nothing to turn on: a connected channel is enough, and on the first run Elbuz picks up messages from the last 14 days.

    A message from a known customer on any channel is added to their open ticket that had activity within the last 3 days, and the reply goes to the channel they last wrote in. Marketplace messages, reviews and comments on posts are turned on separately. More details: “Ticket channels”.

    What changes in your work

    What happens without a queueWhat “Tickets” doesLearn more
    An email sits in a shared inbox, and everyone thinks a colleague has repliedFrom day one, a new ticket goes to the least busy agent in the department with the notification “Ticket #N is assigned to you”Assignment
    A customer got three different replies on three channelsA known customer's channels merge into one ticket, with one replyChannels
    A customer couldn't get through, and nobody called backA missed call becomes a ticket with “High” priority, and your outgoing call counts as a replyChannels
    A customer waits two days for a replyA deadline in business hours, a “40 min left” / “2 h overdue” chip, the “SLA breached” queue and notificationsDeadlines
    A regular customer waits in the general queueA customer whom Elbuz rates as VIP based on their orders gets tickets with “High” priority and the vip tagVIP
    Two managers gave one customer different answersThe ticket shows “is viewing” and “is replying”; before sending, Elbuz warns you that a colleague is already replyingReplying
    “Where is my order?” twenty times a dayA macro fills in the number, status and number, and AI drafts a reply from the knowledge base and the customer's ordersAI assistant
    The manager doesn't know how many tickets are pendingQueue counters and a report for any period: first reply, deadlines and customer ratings for each assigneeReports

    Where to start

    The order in which you get the window ready for work. Each step links to an article that covers it in detail.

    First run of “Tickets”

    What to read next: by role and company type

    Whose tickets an employee sees

    Inside the window, the department's “Data scope” setting applies — the same one that limits customers. If the department may see only its own data or its subordinates' data, an employee sees tickets assigned to themselves or their subordinates, plus unassigned tickets.

    Other people's tickets don't appear in queues or search, and Elbuz won't let you open or change such a ticket from a direct link. Bulk changes also skip tickets the employee can't see. How to set up departments: “Access rights”.

    Scenarios

    A shared inbox and three managers

    Email is already connected, so customer emails turn into tickets automatically, and each one goes to the least busy manager in the department. The manager in charge watches the “SLA breached” queue and the report instead of asking who replied.

    Customers write on Viber and call

    With a messenger and telephony connected, a chat that needs a human and a missed call become tickets, and messages from a known customer merge into one. The manager replies from one window — on Viber or by email.

    A store sells on Rozetka and gets reviews

    On top of email and chats, you get Rozetka buyers' questions with their own reply deadline and 1–2 star reviews with an AI draft. You turn on both channels in “Autonomous support” → “Channels and proactive” (marketplaces, reviews).

    What to do when the window is empty

    What you seeWhyWhat to do
    There's no “Tickets” shortcut The window is open only to the “Management”, “Sales” and “Customer service” departments Ask your manager to grant access (access rights)
    All queues are empty No channel is connected in Elbuz Connect email, chat, a messenger or telephony (what to connect)
    Colleagues see more tickets than you do Your department may see only its own data or its subordinates' data If needed, ask your manager to change the department's “Data scope” (whose tickets)
    A customer's email is in “Mail”, but there's no ticket The email is in the suppliers, partners or system category, or in your own folder Troubleshooting by channel — “What to do when a message didn't become a ticket”

    FAQ

    Do I need to turn anything on for tickets to start coming in?

    No. A connected channel is enough: email, chat, a messenger or telephony. Tickets are collected in the background every 5 minutes, and every minute while the window is open.

    Does “Tickets” replace the “Mail” and “Chat dialogs” windows?

    No, they stay. “Tickets” is for whoever handles customers across all channels; the chat is handier for a live chat agent, and “Mail” is for emails that didn't become tickets.

    Does the customer see the ticket number?

    In an email sent from a ticket that started in chat or from a call, the subject is “Ticket #N: subject”. Replies on the same channel don't include the number automatically; you can insert it with a macro.

    A manager from another department can't see any tickets. Why?

    The window is open to the “Management”, “Sales” and “Customer service” departments. A manager grants access to others in access rights.

    Does AI reply to customers on its own?

    Only if you've turned on autonomous support — it's off out of the box. Without it, AI only prepares drafts and ticket summaries (autonomous support).

    Where to find it and who has access

    Menu
    Directories → Contacts → Tickets; Organizer → Tickets
    Other ways in
    the “Tickets” shortcut on the desktop; a signal in “My Day”; the “Ticket #N” link in an email or chat
    Access
    the “Management”, “Sales” and “Customer service” departments; a manager grants access to others
    Support settings
    the window's gear icon — “Management” department only
    Prepare
    at least one channel: email, website chat, a messenger or telephony

    The “Tickets” shortcut is part of the default role set for the “Sales” and “Customer service” departments. The “Tickets: new to me and overdue” signal in “My Day” counts your open tickets that are unread or past their deadline; click it to open the ticket. To learn what else “My Day” shows, see “First sign-in”.

    Desktop with the Tickets shortcut
    1Tickets shortcut
    1. Tickets shortcut — opens the Tickets window from the desktop.

    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