Tickets

Tickets on the same desk as chat and help

Widget threads already have owners, notes, and history. Customers request a 30-minute email link, then list tickets, reply, and file a new one. Agents still work the same inbox.

A ticket is the same thread

Open, pending, resolved, spam. Customers open a portal with an email link to read the thread, reply, and file tickets. Use the shared inbox. SLA clocks live in Settings. Switch to Cove when tickets should be conversations behind a branded messenger.

  • What ships. Inbox states, assignment, quick replies, snooze, SLA clocks, CSAT after resolve, and a customer portal at /portal/{workspace}.
  • How customers get in. They enter the email they used in chat. Cove sends a short-lived link. No password to remember.

A portal without a second login product

Customers request a 30-minute email link at /portal/{workspace}. They read the thread, reply, and file a new ticket. Agents still work the live chat widget and the shared inbox. Resolve ends the visitor thread. CSAT can fire after. That is the ticket model — a conversation with states, plus a portal.

FAQ

Frequently asked questions

Portal, states, assignment, and CSAT live on the thread.

Yes. Visitors write in the live chat widget or open /portal/{your-workspace} and request a link. Threads live in the shared inbox.

Open, pending, resolved, spam, plus a Snoozed filter. Resolve can ask for CSAT.

If you wanted a conversation queue behind a website messenger — with a portal and SLAs — Cove is the switch. See Cove vs Zendesk.

Blog

Why teams switch the desk

Try it on a live inbox.

Fourteen-day trial. Card required. Cancel before day 14. Paste one script. Set the look.