Use cases
What it does on your site.
What arrives depends on what the site is for. Here is what comes in, how it gets sorted, and the draft that comes back — for the kinds of sites people actually ship.
These are illustrations, not customer stories. When a real customer agrees to be named, we will publish that as a case study and say so.
A client site you built
Contact form on a contractor's marketing site
What arrives
- QuoteExterior and roof repaint, 1990s timber frame. Wants to start next month.
- QuestionCan the family stay in the house during the work?
- SalesSEO agency offering a free audit.
The draft you get
Hi Dana,
Thanks for getting in touch — a 1990s timber frame with the roof included is exactly the kind of job we take on.
I have looked at the photos you sent. To price it properly we need to see it in person: would [proposed dates] work for you?
- ·You are not the one answering. Build it, then hand the workspace over — the client becomes the owner and billing moves with them.
- ·The snippet on the site never changes, so a handover is not a redeploy.
- ·Real quote requests stop being buried under agency cold mail.
A product you shipped alone
Landing page for an indie SaaS
What arrives
- QuestionIs there a self-hosted option? Asking for a 40-seat team.
- QuoteWants annual invoicing and a signed DPA before purchasing.
- SalesOutbound pitch for a lead-gen tool.
The draft you get
Hi Marcus,
Thanks for asking. Self-hosting is [not something we offer today / available on the enterprise plan] — I would rather tell you straight than string it out.
For a team of 40 the practical difference is [pricing detail], and I am happy to walk through it if useful.
- ·Every question you answer once becomes an FAQ entry, and the next draft already knows it.
- ·The model leaves anything it was not told as a blank, so it cannot promise a feature you do not have.
- ·Sales pitches are classified and never notify you — the phone only buzzes for things that need a reply.
A small SaaS support inbox
Contact link in the docs, plus support@ forwarded in
What arrives
- QuestionWebhook retries stopped after a 502. Attached the request ID.
- OtherFeature request: filter the export by date range.
The draft you get
Thanks for the request ID — that helps.
Retries stop after [retry policy], which lines up with what you are seeing. I have pulled the delivery log for that ID and will follow up with what it shows by [timeframe].
- ·Forward support@ into the same inbox so form and email are one list, sorted the same way.
- ·Summaries are one line, so you can triage a morning's queue from a lock screen.
- ·Attachments — logs, screenshots — are read by the model before it drafts.
A store or a booking page
Order questions, stock, delivery
What arrives
- QuestionDoes this ship to Germany, and what is the lead time?
- OtherWants to change the delivery address on an order placed yesterday.
The draft you get
Hi,
We do ship to Germany. Delivery usually takes [lead time] once the order leaves us.
On the address change: your order is still [status], so we can update it — could you confirm the full new address?
- ·Shipping regions, lead times and the returns policy live in the FAQ, so replies stay consistent.
- ·The reply is written in the language the inquiry came in, while summaries stay in one language for scanning.
- ·Nothing sends automatically — an address change is confirmed by a person.
A hiring page
Applications and questions about the role
What arrives
- QuestionIs the backend role open to candidates outside the EU?
- OtherApplication with a CV attached; asking about interview slots.
The draft you get
Thanks for applying — the CV came through fine.
We can offer interviews on [candidate slots]. Let me know which suits you, and I will send an invite.
- ·CVs arrive as PDFs, stored privately with links that expire after ten minutes.
- ·Applications are classified as questions, so they never mix into the sales pipeline.
- ·One form per purpose keeps hiring and customer inquiries visibly separate in the inbox.
Building for someone else?
Set up a workspace per client, configure it while you are still in the code, and transfer it when you ship. They become the owner and billing follows them. The snippet on the site does not change, so nothing needs redeploying.