Support answered, bugs counted, users found.
A small team cannot answer every email, read every crash alert and look for users at the same time. Your office answers support from your own docs, turns bug reports into one ranked list, and finds people online who are asking for what you built.
Updated 15 October 2026
Support email, answered from your own docs.
Your office reads your website and help pages once and turns them into rules, which answer nobody until you have checked them. Your app's store links and your social pages are copied from your site exactly, so "where do I download the iPhone app?" gets the real link. Questions about plans, trials, refunds and data are answered from your rules; anything else comes to you, and your answer can become a rule with one tap.
A customer who asks for their data, or for it to be erased, is handled from their conversation: one file to send them, or one confirmed erasure.
Bug reports, counted and ranked.
Mail from your crash reporters (Sentry, Crashlytics, Bugsnag, Rollbar, Honeybadger, AppSignal, Airbrake, Raygun) is read by rules, and the same crash fifty times becomes one issue with fifty reports. A customer's "the export button does nothing" is recorded as written and matched to an issue already open. You see one list, ranked by how many people it affects and how serious it is.
An issue you marked fixed that is reported again reopens, and you are told at once. Your code is not touched.
Crash reporters it reads
- Sentry, Crashlytics, Bugsnag
- Rollbar, Honeybadger, AppSignal
- Airbrake, Raygun
- And your customers' own words
People asking for what you built.
Every day someone asks on Reddit, Hacker News, X, Bluesky or YouTube for a tool that does what yours does. Your office finds those posts, drafts a helpful reply from your own facts that says who wrote it, and leaves it with you. On Bluesky and YouTube it posts the one reply you pressed Send on; on X it opens the reply for you; on Reddit our browser extension writes it into the box you click. Nothing is posted on a schedule. Read our guide to finding customers on Reddit for the rules that keep you welcome.
Fits the tools you already run.
Invoices from your Stripe account are followed with a restricted, read-only key. Zapier, Make and n8n hear what happens in your office (a new customer conversation, a booking, a review) and can add a customer, a note, a to-do or a draft rule, never send or post. Customers can also write to your own Telegram bot.
The rules it starts with
- Plans and pricing
- Trial and cancelling, refunds
- Getting help, reporting a bug
- Your data: where it is, export and deletion
Asked before you start.
Does it learn from our docs?
It reads your website and help pages once and turns them into rules, which answer nobody until you have checked and switched them on. Your app's store links are copied exactly.
Will it fix bugs?
No. It gathers crash alerts and customers' reports into one list of issues, counts and ranks them, and tells you when a fixed issue comes back. Your code is not touched.
Where does it look for users?
In public posts on Reddit, Hacker News, X, Bluesky, YouTube and forums. Every reply is drafted for you and says who wrote it; you send it.
Read next
Set up your office in an afternoon.
Free to set up, no card needed. It reads your website, asks what it could not find, and nothing goes live until you have checked it.