All guides

Working the queue

Hand-offs and escalation

When a ticket needs to leave QueuePower, nobody should start from a blank page. Reassign to a named teammate with a note, or escalate into Zendesk, HubSpot, ServiceNow, Halo or any system by webhook, with the AI's summary of what has been tried.

5 steps · 4 min read

Before you start

  • For help-desk escalation: a connection set up by an admin under Settings → Integrations.
  1. 1

    Reassign to a teammate

    Choose a person and add a hand-off note. The ticket moves to them with its full history; the timeline records the change.

  2. 2

    Tell the customer, warmly

    When a ticket needs a person, the AI drafts a first-person message about what has happened for them: never a name, team or department, never a timeframe. You review and send it like any reply.

  3. 3

    Escalate to your help desk

    Choose Escalate and give a short reason. The ticket arrives in your help desk with an AI-written summary (the issue, what has been tried, where it stands), the attachments listed with a link to open them, your note, the original message and a link back to the full history.

    You’ll see: The help desk's reference appears on the ticket. Security, legal and data-protection tickets can go straight through; other tickets need some engagement first, so "send it on" can't become a habit.

  4. 4

    Let Full AI escalate for you

    In a Full AI category, tickets escalate automatically when the attempts run out or the customer asks for a person. Every hand-off is on the timeline with its reason.

  5. 5

    Close when someone else will follow up

    When a colleague says they will contact the customer directly, the AI proposes closing the ticket with the same warmth and the door left open: a reply reopens it, and no rating is asked for.

Good to know

  • Once a person has a ticket, it stays with people. Even in a Full AI category the AI keeps drafting but never takes it back.
  • Zendesk, HubSpot, ServiceNow and Halo are treated the same way: context is read in, tickets are escalated out, none is favoured.