Customer support for every app you ship, handled by your coding agent.

ThreadBase puts support email, in-app bug reports, feature requests and App Store reviews from all your apps in one inbox. Your agent reads each thread, fixes what it can in your repo and writes the reply. Nothing reaches a customer until you approve it.

Join the waitlist Invite-only for now.
A bug report in ThreadBase: the customer's message with diagnostics and a crash log, the agent's summary, and its reply waiting for approval
A bug report from an iOS app. The agent read the crash log, found the cause, linked the fix and wrote a reply. It's waiting for you to send it.

Why it exists

We make a handful of iOS and Android apps. Support used to live in several inboxes, App Store Connect and a spreadsheet of feature requests, and answering anything meant switching between all of them.

We already had a coding agent open all day, so we gave it the support queue too. ThreadBase is that setup, cleaned up: one place for every app, with the agent doing the first pass and us deciding what gets sent.

How a day with ThreadBase goes

1

Everything lands in one inbox

In-app support and bug reports come in through the iOS and Android SDKs, with device, OS and app version attached. Your support address forwards to ThreadBase, and App Store reviews are imported every half hour.

The ThreadBase inbox with support emails, a bug, feature requests and App Store reviews from four apps
2

Your agent works through it

Connect Claude Code, Codex or any MCP client. Copy a prompt from the inbox, and the agent goes through the threads one by one, in the repo it already works in.

Besides drafting, it can tag and prioritise threads, open attachments, leave notes, link commits and pick up tasks you write for it.

Use the ThreadBase MCP tools.

Work through Example Notes' open bug reports one at a
time, oldest first.

1. List them with list_threads: app "example-notes",
   type "bug", status "open", has_draft false.
2. Read the app's knowledge base with get_app.
3. For each one: read it with get_thread, open the
   logs with get_attachment, find the cause and fix it.
   Link the commit with link_thread, then write a reply
   with draft_reply. Don't send it: I approve drafts in
   the ThreadBase dashboard.
3

You read, edit and send

Every draft waits on the Approvals page next to the message it answers. Approve it, change a sentence, or throw it away. Replies go out from your app's own address, and App Store replies are posted to the review.

The Approvals page: a customer's question in Spanish and the agent's draft reply in Spanish

What's in it

All your apps in one place
One inbox, filtered by app or by type. Badges show what's waiting.
Bug reports with diagnostics
Device, OS, app version, logs and screenshots arrive with the report.
App Store reviews
Every review becomes a thread. Approved replies are posted to the App Store.
Replies from your own domain
Customers hear back from support@yourapp.com, the address they wrote to.
A public feature board
Merge duplicate requests to count votes, and publish the ones you plan to build.
Help pages in 17 languages
Contact, bug report and feature request screens that look native inside your app.
Tasks for agents
Write a task, an agent claims it, does it and hands it back with its commits linked.
You stay in charge of sending
Agent tokens can read, triage and draft. Sending needs a separate permission you rarely give.
App Store reviews in ThreadBase with star ratings and the reviewer's country
App Store reviews come in with their stars and the reviewer's country, ready for a reply.

Questions

Which agents work with it?

Anything that speaks MCP. We use Claude Code and Codex. There's also a REST API and a small command-line tool for scripts.

Can the agent send replies on its own?

Not unless you let it. By default agent tokens can read, update and draft; sending is a separate permission, and every draft waits for you on the Approvals page.

Do I have to change my apps?

Only for the in-app help pages: add the SDK and a small backend function that keeps the key off the device. Email and App Store reviews work without touching the app.

Why is it invite-only?

We're setting up a few teams at a time, with each of them, so we can fix what gets in their way. Join the waitlist and we'll write when there's room.

Join the waitlist

Tell us a little about your apps. We'll email you from hello@threadbase.app when there's a spot.

No newsletter. How we use this