Turn Chats Into Support Tickets.

When a request needs more than one chat, make it a ticket. Your team owns it until it’s done, and the customer can follow along.

  • Created by your team or the AI agent
  • Assign, prioritize and track every ticket
  • Customers follow and reply from a private link

Ticket T-1042, "Bulk order discount", in progress with high priority and assigned to Sarah, with Maya Chen’s chat attached and the private link she uses to follow it.

What tickets do.

Each ticket keeps the chat it came from, so nobody asks the customer to repeat themselves.

  • Three ways to create one

    Write one by hand, convert a chat, or let the agent raise one mid-chat. Each ticket shows how it started.

  • The chat stays attached

    The conversation behind the ticket is on the ticket. Whoever picks it up starts with the full story.

  • Assign and prioritize

    Status runs from open to closed, priority from low to high. Assign it to a teammate or leave it unassigned.

  • Customers can follow along

    Messages you send reach the customer by email, with a private link to read the ticket and reply. No account needed.

  • Internal comments

    Leave notes the customer never sees. If they’re still in the chat, send a comment to the conversation.

  • Alerts you choose

    Get notified when a customer replies, a ticket changes hands, or the AI raises one. In the app, by email, or both.

From chat to ticket in three steps.

  1. 01

    Turn on ticketing

    An owner or admin switches it on for each agent that needs it. Your other agents aren’t affected.

  2. 02

    Create a ticket

    Convert a chat, write one by hand, or turn on the ticket action so the agent can raise one itself.

  3. 03

    Work it and close it

    Set the owner and priority, message the customer, and mark it resolved when it’s done.

Tickets in detail.

When to use a ticket

Live chat works while the customer is still in the widget. A refund that takes two days, a bug that needs an engineer, or anything that should outlast the chat needs a ticket.

A ticket gives the work an owner, a status and a number your team can find later. It doesn’t replace live chat: when a customer needs a person right now, use human handoff.

Use the inbox while the customer is waiting. Use a ticket when the work will outlast the chat.

Built in, not a HubSpot sync

These tickets are AssistLoop’s own, kept on each agent. They are not copies of tickets in another CRM.

If you already run support in HubSpot, the agent can file tickets there instead, through an action. Built-in tickets are for teams who want the queue next to the inbox.

Each agent files its tickets in one place, AssistLoop or HubSpot, so they never split across two systems.

Built-in tickets live on the agent. HubSpot tickets live in HubSpot. Each agent files into one of them, not both.

How a ticket starts

There are three ways. By hand: a teammate writes one from scratch. From a conversation: a teammate converts a chat they’ve read. By the AI: the agent raises one mid-chat, open and unassigned, with the conversation attached.

Every ticket records how it started. An AI ticket stays marked as raised by AI even if you later change its linked conversation, so you can tell what a person chose to file from what the agent filed.

Each agent numbers its tickets in order: T-1, T-2, T-3. A deleted ticket’s number is never reused.

A ticket is created by hand, from a conversation or by the AI, and it always shows which.

The customer can follow along

When you message the customer from a ticket, they get an email with a private link. It opens the ticket’s subject, status and messages, and they can reply there without an AssistLoop account.

Anyone with the link can read the ticket, so treat it like a password. The page is kept out of search engines, and analytics and marketing scripts don’t run on it.

Internal comments never reach the customer. If they’re still in the chat, you can send a comment to the conversation instead.

Customers read and reply from a private link, with no account needed. Internal comments stay internal.

Plans and settings

Tickets are included on paid plans, not the free plan. See pricing for what each plan includes.

Ticketing is also switched on per agent, by an owner or admin. Turning it off keeps your existing tickets, and they come back when you turn it on again.

Tickets need a paid plan, and each agent has its own on/off switch.

Frequently asked questions.

Still stuck?

[email protected]

No. These tickets are AssistLoop’s own, kept on the agent. Filing a ticket in HubSpot is a separate agent action. Each agent files into one of the two.

Use handoff while the customer is waiting in the chat. Use a ticket for work that continues after they leave, like a refund or a bug. The conversation stays linked either way.

Yes. With the ticket action turned on, the agent can raise a ticket mid-chat. It starts open and unassigned, with the conversation attached, and stays marked as raised by AI.

By email. When you message them from the ticket, they get a private link where they can read it and reply, without an AssistLoop account.

Yes. Assign a ticket to any teammate with access to that agent, or leave it unassigned. You can filter by assignee and update up to 50 tickets at once.

No. Tickets need a paid plan. Ticketing is also turned on per agent, so you can use it on a support agent and leave it off on a sales one.

Get started

Start tracking support tickets.

Let the agent answer what it can, and turn the rest into tickets your team can close.