Skip to main content
Use ticket and helpdesk commands to manage support tickets and their message threads. For REST details, see Helpdesk. Authenticate first — see CLI Auth. Most commands require an agent ID (-a agt_123) or a default agent.

​
Create a ticket

Open a ticket on behalf of a customer with a subject, description, and email:
Pass the full body as JSON instead of individual flags:
Use --customer-name when the email creates a new customer record. Set status, assignee, or team at creation time with -f or --data — see Create a ticket for assignment rules.

​
List and search tickets

List tickets for an agent, newest first:
Filter by status category, assignee, team, channel, or date range:
Search ticket message content:
Fetch every page as JSON:

​
Get a ticket and read messages

Show one ticket by its per-agent number:
List the ticket’s message thread:
Include internal notes or system events with --types:

​
Reply to a ticket

Post a customer-visible reply attributed to a team member:
The message body is GitHub-flavored Markdown. A 201 means the reply was recorded, not that it reached the customer — delivery is asynchronous.

​
Update status, assignee, or team

Look up valid status IDs and team IDs before you update:
Close a ticket by status category:
Assign to a team member or set a specific status ID:
Use statusCategory to resolve to that category’s default status, or statusId for a specific configured status. See Statuses and Update a ticket.

​
Look up teams and statuses

List helpdesk teams (including the default):
List configured ticket statuses with IDs and labels:
Use --json to pipe IDs into scripts.

​
Commands

For every flag, run chatbase tickets <command> --help or chatbase helpdesk <command> --help.