Help Desk

Overview

Manage customer support tickets and conversations from a central help desk.

Documentation Index

Fetch the complete documentation index at: /llms.txt

Use this file to discover all available QwryAI pages before exploring further.

The QwryAI help desk is the support workspace for customer conversations that need human attention. Agents can review tickets, search customers, manage assignment, respond publicly, leave internal notes, and keep the original chatbot conversation connected to the support record.

QwryAI help desk dashboard
Use the help desk to review ticket status, assignment, customer context, and the conversation thread.
  • Start with Your Inbox, Mentions, All, Unassigned, and Solved.
  • Open the ticket detail panel before replying so you understand the requester and previous tickets.

Tickets Inbox

The inbox is organized around queues and ticket ownership. Use Your Inbox for tickets assigned to you, Mentions for internal notes that tagged you, All for every ticket, Unassigned for new work without an owner, Solved for resolved tickets, and Conversations for chatbot conversations that may not have become tickets yet.

AreaWhat it shows
RequesterThe customer who submitted the ticket, including available profile fields such as name, email, external ID, and phone number.
AssigneeThe teammate responsible for the ticket. Assignment can be manual or automatic.
ThreadCustomer replies, agent replies, internal notes, and system events for assignment or status changes.
Details panelTicket ID, status, subject, submission date, customer context, previous tickets, notes, and the link back to the original conversation.
Ticket status examples
StatusWhen to use it
OpenThe issue needs an agent response or investigation.
On YouThe ticket is assigned to you and waiting for your next action.
On CustomerThe team has replied and is waiting for the customer.
On HoldThe ticket is paused because of an external dependency. Add an internal note explaining why.
SolvedThe customer issue is resolved or intentionally closed.

Replying to Tickets

  • Reply sends a public message to the customer.
  • Note saves an internal-only message for your team.
  • @mentions are available in notes and notify the mentioned teammate.
  • Attachments should be checked for sensitive data before sending.
  • AI Compose can help draft a response, but the agent should review it before sending.

Recommended Ticket Workflow

  1. A customer request creates a new ticket.
  2. An agent opens the ticket and checks the customer context.
  3. The ticket is assigned manually or automatically.
  4. The agent replies publicly or adds an internal note.
  5. After replying, set the status to On Customer when waiting for the customer.
  6. Use On Hold only when you are waiting on an external dependency and add a note explaining why.
  7. Close the ticket only after the customer issue is resolved.