bird support-tickets

Usage

bird support-tickets

Description

A ticket is opened once and then followed up on, so every later call addresses the existing ticket by id. A support agent's answer arrives asynchronously rather than in the response that prompted it, and --watch blocks an open or a read until one lands.

Reads return JSON. Mutations take flags and/or a --body-file JSON body (flags overriding); run --example to print the body shape or --dry-run to preview the request.

Procedure

Open a support ticket

Open a support ticket with Bird and send its first message. Use type support for a human request, ai for an automated answer, or feedback for product feedback. The reply arrives asynchronously, not in this response.

1. bird support-tickets create — Returns the new ticket with its first message. Next: bird support-tickets get or bird support-tickets reply

Read a support ticket and wait for a reply

Read a support ticket and its message history. The agent's reply arrives asynchronously, so a freshly opened ticket may have no reply yet.

1. bird support-tickets get — Returns the ticket and its messages, oldest first. A reply (automated or from a person) has arrived when a message with sender_type: agent is present that was not there before, or the ticket leaves OPEN; re-read until then, then judge whether it answers your question. Next: bird support-tickets viewed or bird support-tickets reply
2. bird support-tickets viewed — Call this after reading a ticket that has a new agent reply. Records that the reply has been seen and suppresses the notification email that would otherwise fire 30 minutes later.

Commands