Customer tickets
An email gets lost in the shared mailbox, a customer wrote on Viber and has been waiting for two days, two managers gave them different answers, and nobody ever called back after a missed call. “Tickets” collect emails, chats, messengers and calls into one queue on their own: every customer question gets a number, an assignee and a response deadline, and the reply goes out through the same channel the customer used.
When a deadline passes, the assignee and their manager get a notification. The manager sees how many tickets are waiting and how fast each employee responds. There is nothing to turn on: a connected mailbox, website chat or telephony is enough.
Start with the overview: what changes, the first steps and which article to read next. Worked examples for an online store, a wholesale company and a service business show what to turn on and what a normal working day looks like. If you currently use Zendesk, Freshdesk or Intercom, you can migrate your history.
Subsections
Working with tickets
How to handle tickets every day: queues, search, replying to customers, macros, notes and working with the customer and the order.
Ticket channels
Where tickets come from: email, website chat, messengers, calls, marketplace messages, reviews and social media comments.
Support desk setup
How to set up your support desk: who sees tickets, how they are assigned to employees, working hours and response deadlines.
AI and autonomous support
AI in tickets: draft replies for employees and autonomous support that resolves common customer questions on its own within your rules.
Articles in this section
- Tickets: customer emails, chats and calls in one queue
Customer tickets in Elbuz: emails, chats, messenger messages and calls in one queue with an assignee and a reply deadline. What the helpdesk does and where to start.
- How to read support reports
Support reports in Elbuz: who is overloaded right now, first reply, SLA compliance, solved without a human, orders after tickets, and breakdowns that open the ticket list.
- How to collect customer ratings (CSAT) after a reply
How to ask a customer to rate your reply after “Solved”: when to turn it on, what the customer gets, who learns about “Bad” and where to see ratings for each assignee.
- How to move tickets from another support system
How to move tickets, conversations, customers, macros and articles from Zendesk, Freshdesk, HelpCrunch, Help Scout, Zoho Desk, Gorgias and Intercom to Elbuz “Tickets” without duplicates.
- How to set up customer support for an online store
How to set up “Tickets” for an online store: channels including marketplaces and reviews, assignment and deadlines, macros, the AI assistant, autonomous support from “Test” to “Live”, and reports.
- How to set up support for wholesale customers
How a wholesale company sets up Tickets: a customer's tickets go to their account manager, VIP customers skip the queue, longer deadlines, who sees what, warehouse and accounting in a ticket, AI without money actions, flows.
- How to handle service company requests: from the call to the site visit
How a service company (repairs, installation, services) sets up Tickets: missed calls become requests, statuses from the call to the site visit, deadlines that fit the crew's schedule, technicians in the field, AI, reports.
