Skip to main content
The helpdesk is where your team works the conversations the agent hands over. Each one becomes a ticket with the whole conversation attached: you reply from the ticket on the channel the customer used, assign it, set its status and close it, and the agent stays out of the conversation until you do. It is optional. If your team already runs Zendesk, Freshdesk, HubSpot, Intercom, Help Scout, Gorgias or Odoo, keep it: the agent can open tickets there instead. See Helpdesk tickets. The built-in helpdesk is for teams that don’t have one, or would rather work handoffs next to the agent.

Turn it on

The helpdesk is set per agent, and every agent starts with it off.
1

Open Handoff

Go to Agents → your agent → Handoff.
2

Switch on Helpdesk

In the In the Wiredesk helpdesk card, turn on Helpdesk. Open helpdesk takes you into it; so does Helpdesk in the console’s sidebar.
3

Let the agent hand over (optional)

Turn on A person in chat & email on the same page, so the agent can hand a customer to your team when they ask for a person. See A person in chat & email.
The helpdesk is an app of its own, with its own sidebar: your views, Analytics, Settings, and Dashboard to go back to the rest of Wiredesk. Every helpdesk setting is under its Settings (or Helpdesk settings on the Handoff card). Changing them needs the Admin or Owner role; any member can work tickets.

One place to answer

Once an agent’s helpdesk is on, its handoffs live only in the helpdesk. They leave the console’s Inbox and the dashboard’s Needs you, and its chat, email and WhatsApp conversations on the Conversations page show Worked in the helpdesk in place of the reply box: View ticket when a ticket holds the conversation, Takeover when none does yet. Its phone, web voice and Zendesk Messaging conversations keep their usual page. Agents with the helpdesk off work as before.

How tickets are opened

Tickets the agent opens and tickets you start run your Created triggers. The default one, Route to default team, puts those without a team on your default team. A takeover ticket is already assigned to you, so it skips the Created triggers and starts with no team until you, an Updated trigger, or an automation gives it one.

Who answers while a ticket is open

While a ticket is open, the agent doesn’t reply in that conversation; your team does. When the customer writes again, the ticket moves back to On you. Closing or cancelling a ticket hands a chat, email or WhatsApp conversation back to the agent, and the ticket is then locked: it takes notes only. To pick the customer up again, use Take over in this ticket or Take over in a new ticket on the locked ticket.

Statuses

Every status belongs to one of six categories, and the categories decide what the helpdesk does: You can add your own statuses inside each category under Settings › Ticket statuses, rename them, and pick the default one.

In this section

Working tickets

The inbox, views, replies, notes, files, merging and shortcuts.

Teams and assignment

Who gets which ticket, availability, shifts and ticket reuse.

Triggers and automations

Rules that act when tickets change, or when they have waited.

Custom fields

Details on a ticket, collected by the agent at handover.

Satisfaction surveys

A one-question survey after a ticket closes.

Helpdesk analytics

Volume, speed, resolution, satisfaction and your team’s time.

Helpdesk email addresses

Under Helpdesk → Settings → Email, Helpdesk email address lists the addresses the helpdesk uses as inboxes. Add your addresses first, with forwarding and DNS checked, on the agent’s Email channel page; then click Add email here and pick one per row. Addresses with issues can’t be picked.
  • Mail to a helpdesk address becomes a ticket, with no AI reply, even with the Email channel off. If the Email channel’s Reply addresses list the same address, the AI agent answers first instead, and hands over when a customer asks for a person.
  • A teammate’s reply leaves from the address the ticket came in on, if it’s in the list, otherwise from the first. With an empty list, replies leave from the agent’s own address. Trigger emails to the customer use the same list, or any address that can send if it’s empty.
  • When a reply fails or bounces, the ticket shows “This email was not delivered to the recipient.” with the reason, and the Deliverability alert contact gets an email.