How Chirp works.

Follow up with customers when the fix ships.

Press i in a thread to search Linear, create an issue or link one. A thread can link several issues, and the thread header shows each one’s state, checked every five minutes.

• Snooze until done: the thread wakes when every issue it waits on is Done or Canceled. By default it reopens with a draft that names the issue.
• Issues view (g i): linked issues sorted by how many customers are waiting.
• Search with linked:open, linked:none or an identifier such as linked:ENG-2204.

Work through the queue with single keys.

The list and the open thread use the same keys, so your hands stay on the keyboard. Select several rows with x, and the next key applies to all of them.

• j k move, r reply, n note, ⌘↵ send.
• s a t open the status, assignee and tag pickers.
• x selects, ⌘A selects the visible list, e archives, b snoozes.
• ⌘K finds any command or saved view by name.

Every inbox in one list, with access per team.

Connect Gmail and Google Workspace inboxes, or any IMAP and SMTP mailbox. Each inbox has its own name, colour, From name and signature, and every reply goes out from the address the customer wrote to.

• Three roles: Admins change settings, Agents work threads, Viewers read.
• Open an inbox to the whole workspace, or only to the teams you pick.
• The server checks access on every read, including counts, search, attachments and the customer drawer, so a hidden inbox stays hidden.
• Invite people with ⌘I. Invitations are valid for 14 days.

Automations can't email your customers.

Rules change status, assign, tag, snooze, add internal notes and write drafts. The rule engine has no send action. A rule’s draft waits in the reply box until a teammate sends it.

• Built-in rules per inbox: when you link an issue, when a linked issue closes, and when mail comes from certain senders (*@alerts.example).
• A builder for your own rules: a trigger, conditions (sender, subject, tag, inbox) and ordered actions.
• Apply to existing runs a rule over the threads it already matches. Press z to undo it.
• Each run adds a line to the thread that says which rule ran and what it changed.

Save a search and open it with g 1.

Press / and type. Each filter becomes a chip, and the menu suggests teammates, tags, inboxes and dates in your time zone. Press ⌘S to save the search. Your first nine views open with g and a digit, and all of them are in ⌘K and the mobile menu.

Check their plan without opening Stripe.

Press u to open the customer drawer. It shows the customer’s past threads and, from Stripe, their subscriptions and payments. Chirp matches the Stripe customer by the sender’s address, and you can set the customer ID by hand when it differs.

• Chirp needs only a restricted, read-only Stripe key, and stores it encrypted.
• j k move through the customer’s threads, ↵ opens one.

Notifications for your threads, with quiet hours.

Choose which events notify you in the app and on your desktop. In quiet hours, desktop alerts wait until quiet hours end; the in-app list keeps updating.

• Events: a thread assigned to you, an @mention in a note, a customer reply, a snooze that woke up, a linked issue that closed, and a customer waiting more than four hours.
• Quiet hours default to 19:00 to 08:30 on weekdays and all weekend, in your time zone.
• An admin can set an inbox to always notify, even in quiet hours. Use it for security@.

An API for your agents.

Codex, Claude Code and your own scripts can search and triage threads, add notes, start conversations and send replies through the REST API. A key acts as the person who created it, with the same role and inboxes, and read, write and send scopes. See the API reference.

Chirp is also careful with the mail it already holds:

• HTML and SVG attachments download instead of opening in the app, so a sender’s file cannot run script there.
• Non-English mail can be translated to English. The request asks the provider not to keep the data.