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.
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.
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.
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.
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.
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.
Anything that speaks MCP. We use Claude Code and Codex. There's also a REST API and a small command-line tool for scripts.
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.
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.
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.
Tell us a little about your apps. We'll email you from hello@threadbase.app when there's a spot.
We'll email you when there's a spot.