Chirp

Shared support inboxes for modern teams.

  • $9 / mo / user
  • First-class Linear integration
  • First-class API
  • Keyboard-first navigation

Link each support thread to its Linear issue. When the fix ships, Chirp reopens the thread with a reply drafted for you to send.

Get early accessSee all features

Set up in 5 minutes. Your mail stays in Gmail, so there is nothing to migrate.

Bug reports go quiet after the issue is filed.

A customer reports a bug. You file it in Linear and promise to follow up. Three weeks later the fix ships, and the thread is still in someone's archive. The customer finds out from the release notes, if at all.

In Chirp, press i, pick the issue and leave "Snooze until done" checked. The thread leaves your list and comes back with a drafted reply when the issue is done.

The Issues view (g i) sorts linked issues by waiting customers, so you fix the bug with twelve people behind it first.

Set up in 5 minutes.

Four steps, and your team is working threads.

  1. Sign up

    Create your workspace. You are its first admin.

  2. Connect your inbox

    Sign in with Google to connect a Gmail or Google Workspace inbox. Chirp starts syncing right away.

  3. Connect Linear

    Open Settings, then Integrations. A Linear admin approves Chirp once.

  4. Invite your team

    Press ⌘I, enter their emails and pick a role. They sign in with Google.

Get early access

The rest of the inbox runs on single keys.

  • jkex

    Clear the queue without the mouse

    Move with j and k, archive with e, and set status, assignee or tag with s, a or t. Select a batch with x and the same keys apply to all of it. ⌘K finds every other command by name.

  • 1230

    Keep support@, billing@ and security@ in one list

    Each inbox keeps its own colour, From name and signature. Press 1 to 9 to see one inbox and 0 for all. Give security@ to your platform team, and only that team and your admins can open it.

  • 0 send actions

    Let rules sort the mail. You send the replies.

    Rules close, tag, assign and snooze threads, add notes and write drafts. They can't send email. A draft fills an empty reply box and never overwrites what you're typing.

  • ⌘Sg 1

    Type filters, then give the search a key

    Type filters like status:open or linked:open and each one becomes a chip. Press ⌘S to save the search as a view, and g 1 opens it from anywhere.

Safe to point at your real support inbox.

Chirp reads customer mail. These protections are always on.

  • Your mailbox stays the source of record.Chirp syncs Gmail or IMAP and sends through it. Nothing is moved.
  • No rule can send email.Automations write drafts and leave the sending to you.
  • Access is checked on the server.An inbox you cannot see never appears in lists, counts, search or attachments.
  • No automatic resends.If a send fails or its result is unclear, Chirp never retries it on its own.
  • Read-only Stripe key.The customer drawer needs only a restricted key, stored encrypted.

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.

# ENG-2204 shipped: find the customers waiting on it
GET   /v1/conversations?linked=ENG-2204&status=open

# tell each one, then close the thread
POST  /v1/conversations/{id}/replies   {"body": "The fix is live."}
PATCH /v1/conversations/{id}           {"status": "closed"}

The shortcuts you get on day one.

The bar at the bottom of the app lists the keys for the screen you are on, so you learn them as you work.

j / k
Next or previous thread
x
Select a thread (⌘A selects the list)
e
Archive the selection
s a t
Set status, assignee or tag
b
Snooze the selection
r n
Write a reply or an internal note
⌘↵
Send the reply or note
z
Undo a send while it waits
i
Link a Linear issue
u
Open the customer and their Stripe data
1-9 0
Filter to one inbox, or show all
g 1-9
Open a saved view
/
Search
c
Start a new conversation
⌘K
Find any command by name

Questions before you connect an inbox.

Does Chirp replace Gmail?

No. Your mailbox stays the source of record. Chirp syncs it and sends through it, so replies land in your Sent folder as usual.

Can an automation email a customer by mistake?

No. Rules have no send action. Replies come from your teammates, or from a script whose API key has the send scope.

How long does setup take?

About 5 minutes: sign up, connect a Gmail or Google Workspace inbox with Google sign-in, connect Linear, and invite your team.

Do we need Linear?

No. The inbox, keys, rules and search all work without it. Connect Linear in Settings when you want to link threads to issues.

Who can see each inbox?

Admins, plus the teams you choose. Open an inbox to everyone or to specific teams; the server enforces it on every list, count, search and attachment.

Does it work with Microsoft 365 or Outlook?

Not yet. Chirp supports Gmail, Google Workspace, and mailboxes with IMAP and SMTP access.

Is there an API?

Yes. A REST API lets Codex, Claude Code and your own scripts search and triage threads, add notes and send replies. Create a key in Settings, then API keys.

How much does Chirp cost?

$9 per user per month, with every feature included.

$9 per user per month

Every inbox and feature, for every teammate. No tiers, no add-ons, no hidden fees.

Get early accessFull pricing details