↑↓ selectEnter openEsc close

    1. Elbuz

    Working with tickets as an agent

    9 min readUpdated

    Elbuz collects customer emails, chats and calls in one “Tickets” window: each ticket has a number, a customer and a reply deadline, and replies go out through the customer's channel.

    When you need this:

    • Customers write by email, chat and messengers — everything is already in queues.
    • Unclear who has already replied — the ticket shows the whole conversation, colleagues' notes and who is typing.
    • A customer has waited longer than promised — the ticket turns red and stays on top.
    • A colleague is on vacation — one assignee change hands their tickets to someone else, with a notification.

    Where to start: an agent's morning in five steps.

    What the agent workspace can do

    • Work through a queue — standard and custom queues, search by number, sorting by deadline, the board, bulk actions, “Team” for managers.
    • Reply to a customer — through the same channel or “Email to …”, status together with the reply, macros, notes with an @mention, “Take next”.
    • Work with the customer and the order — link or change the customer, see their documents and other tickets, merge duplicates, “AI actions”.
    • Statuses — Elbuz reopens a ticket on its own when the customer replies and closes it after 4 days of silence.
    • Take or hand over — assignee, department and tags with one chip each, and your colleague gets a notification.
    • Keyboard shortcuts — a whole day in the list without the mouse.

    Where tickets come from and who sees them — see “Tickets: customer emails, chats and calls in one queue”.

    How the window is laid out

    The “Tickets” window has four parts, from left to right:

    PartWhat's in itDetails
    Queue railStandard queues with counters, “My queues”, and “Team” for managersqueues
    ListSearch, the view button (“List”, “Board”, “Reports”), the “⋮” menu with sorting; ticket rows with a deadline chiplist order
    TicketA header with status, priority, assignee, department and tag chips; the conversation feed; the reply boxreplying
    Right panelThe customer, “AI actions”, recent documents, the AI analysis, the customer's other ticketscustomer panel

    You can drag the borders between parts and hide the rail with the chevron. In a narrow window the rail collapses into icons, and the right panel opens with the “Customer” button (narrow window).

    While the window is open, Elbuz pulls in new tickets and updates the counters once a minute. A new customer message brings the ticket back to “My open” as a bold row, and an assignment or a colleague's @mention arrives as a notification.

    The Tickets window: queues rail, ticket list, open ticket and the customer panel
    1Queues
    2Ticket list
    3Ticket header
    4Timeline
    5Reply box
    6Customer panel
    1. Queues with counters, your own queues and the Team section.
    2. Search, view and sorting controls, and ticket rows with an SLA chip.
    3. Status, priority, assignee, department and tags change with one click.
    4. All correspondence, notes and events of the ticket.
    5. Reply through the same channel or leave an internal note.
    6. The customer, their recent documents and their other tickets.

    An agent's morning in five steps

    1. Open “Tickets”. The window opens on the queue you left yesterday (the first time — on “All open”). Tickets that came in overnight are already there.
    2. Start with the “SLA breached” queue. These are customers whose reply deadline has already passed — a red “2 h overdue” chip. If it isn't empty, reply to these customers first: with the default settings, the assignee and their manager have already been notified about each such ticket.
    3. Then “My open”. The list is sorted by deadline: the longest-overdue ones are at the top. An orange “waiting 3 h” instead of a date means the customer had the last word. J opens the next ticket, R puts the cursor in the reply box, G asks AI to prepare a draft (how it works).
    4. After replying, check “Send as”. “Pending” removes the ticket from your queue until the customer replies; “Solved” closes it after 4 days of silence; “On hold” is for when you're waiting on the warehouse or a supplier (which status to choose).
    5. Finally, “Unassigned”. This is what assignment doesn't hand out: tickets where the customer has been silent for more than 3 days, and all new ones when assignment is set to “Manually”. Cleared your queue to zero? Use “Take next”.

    Ticket statuses and what Elbuz does on its own

    The left side is your actions (“Send as”), the right side is what Elbuz does on its own: a customer reply returns the ticket to “Open”, and “Solved” becomes “Closed” after 4 days of silence
    customer message arrivesreply from the ticket, default“Send as”reply from “Mail” or “Sendas — Open”“Send as — Pending”“Send as — On hold”“Send as — Solved”customer repliedcustomer repliedcustomer replied4 days with no customerreplyNewOpenPendingOn holdSolvedClosedA closed chat sets “Solved”from any status except ClosedA new email becomes a new ticket,a chat — if a person is needed
    • Start
    • State
    • End
    • Note

    You change the status either with the chip in the ticket header (the S key) or together with the reply via “Send as”. Every change is logged in the feed as an event: who changed it and from which status to which.

    StatusWhat it meansWhat Elbuz does on its own
    “New”Nobody has replied yetThe first reply clears this status; so does an answered incoming call
    “Open”In progress: the customer is waiting for you—
    “Pending”You replied, the ball is in the customer's courtThe deadline doesn't run; any customer message returns it to “Open”
    “On hold”You're waiting on a third partyThe deadline keeps running; a customer reply returns it to “Open”
    “Solved”The issue is closed on your sideA customer reply within 4 days reopens it, a short “thank you” doesn't; 4 days of silence — “Closed”
    “Closed”FinalA new email or call from the customer becomes a new ticket

    How the deadline behaves in each status and what happens after “Solved” — see “How to reply to a customer in a ticket”.

    How to take a ticket or hand it over to a colleague

    “Take it” (the I key) in the header makes you the assignee. The button shows only when you aren't the assignee. You don't have to take a ticket before replying: if there's no assignee, whoever sends the first reply to the customer becomes one. Take it in advance when you don't want a colleague replying at the same time.

    To hand a ticket over to a colleague, use the “Assignee” chip (the A key) and pick a name from the list. What happens:

    • the ticket disappears from your “My open” and appears in theirs;
    • the feed shows the event “your name: assignee — colleague's name”;
    • your colleague gets the notification “Ticket #N is assigned to you”. A note with an @mention explains what has already been done;
    • if the ticket came from a chat, your colleague also becomes the assignee of the chat itself — otherwise they couldn't reply there.

    To remove the assignee (“Unassigned”), use the same chip. A ticket whose assignee was removed by hand is no longer handed out by automatic assignment — it waits in “Unassigned” until someone takes it. How assignment works — see the article on ticket assignment.

    The “Department” chip moves the ticket to another department. It affects automatic assignment and reports, but not who sees the ticket: that's decided by “Data scope”.

    Tags — the chip with the label icon. Separate them with commas: “delivery, return”. Elbuz lowercases them and removes “#” and duplicates. Tags are used for custom queues and reports; the customer doesn't see them. To tag several tickets at once, use the bulk actions bar.

    How to work from the keyboard

    The keys work when the “Tickets” window is active and the cursor isn't in an input field. Esc takes the cursor out of a field. The full list opens with “?” or the “Keyboard shortcuts” item in the “⋮” menu above the list.

    KeyWhat it does
    J / KNext / previous ticket in the list
    R“Reply” mode, cursor in the box
    N“Internal note” mode, cursor in the box
    MMacro list
    G“AI draft”
    I“Take it”
    A“Assignee” menu
    S“Status” menu
    P“Priority” menu
    /Cursor in search
    Ctrl + EnterSend (in the reply box)
    Ctrl / Shift + clickSelect several tickets
    ?Shortcut help

    Scenarios

    From an email to a solved ticket

    An email “Where is my order?” appears in “My open” with a deadline chip. Open it with J; on the right, “Recent documents” shows the customer's order. Click “Add tracking to reply”, write text around the number, set “Send as” to “Solved”, press Ctrl+Enter. The email goes to the same thread, and the ticket closes by itself after 4 days.

    Hand a difficult ticket to a senior colleague

    Write a note: what has been done and what the customer wants. Change the assignee with the chip — your colleague gets “Ticket #N is assigned to you” and sees the note in the feed when they open the ticket.

    The customer writes both by email and in a messenger

    If Elbuz knows the customer and the ticket is still open, the messenger message is added to it, and the reply goes where they wrote last. If not, a second ticket appears: link the customer and merge them (how to merge).

    An agent goes on vacation

    The manager opens their tickets in “Team”, selects them and changes the “Assignee” in the bulk actions bar. Each new assignee gets a notification (“Team”).

    FAQ

    Will my colleague know I handed them a ticket?

    Yes. Any assignment to someone other than yourself — by chip, in bulk, by macro, flow or assignment rule — sends your colleague “Ticket #N is assigned to you”. An @login mention in a note sends a second notification with the note text.

    Do I need to keep the window open for tickets to appear?

    No. New emails and chats become tickets in the background; an open window just refreshes the list and counters more often. Assignments and @mentions arrive as notifications.

    I replied from “Mail”, not from the ticket. Will the ticket see it?

    Yes, the email lands in the ticket feed, and a “New” ticket becomes “Open”. To set “Pending” or “Solved” right away, reply from the ticket.

    Who sees a ticket that has no assignee?

    Everyone with access to the “Tickets” window, regardless of “Data scope”. A ticket with an assignee is visible according to the department's “Data scope” rules.

    What's the difference between “Department” and “Data scope”?

    The ticket's “Department” affects assignment and reports. Who sees the ticket is decided by “Data scope” in the group permissions (settings).

    Where do I find a ticket that has already closed?

    In the “All tickets” queue — closed ones are there too. If you know the number, type it in search: the number is searched across all queues (search).

    Where to find it and who has access

    Menu
    Organizer → Tickets
    Other ways in
    Directories → Contacts → Tickets; the “Ticket #N” link in an email or chat
    Access right
    the “Tickets” window in “Group permissions”; you see what the department's “Data scope” allows
    Prepare
    access to documents — for order actions in the right panel

    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