A customer texts, emails or leaves a voicemail. Stet Desk reads it, opens the customer and the job, starts your process, and drafts the reply under your rules. You fix what you'd fix, and you press send. Nothing else does.
Built for service businesses of 1 to 50 people. Fence, HVAC, plumbing, landscaping, cleaning, consulting. It does not answer calls, schedule, or book appointments; it reads, opens, drafts and remembers.
Four steps, every job. The fourth one is where it learns.
Paste it, forward it, or let the inbox take it. Text, email or a voicemail transcript.
Customer, job, site, scope, the date they asked for, and the questions you'd want answered before quoting. The original message stays on the job.
From your approved template, given your standing rules for that step. It lists which rules it followed so you can check.
Edit the draft and say one sentence about what to learn. Said again on another job, it is a rule. You press send.
The parts of running a service business that happen at a desk, done at the desk, while you are not at one.
One place a customer's message lands. The assistant reads it and opens the job. If it cannot find a name, an address or a scope, it asks you rather than guessing.
Site visit, draft, review, approve, send. Each step has an owner: you or the assistant. The assistant only works at its own steps.
The quote email you approved is the skeleton. The draft fills it from the job and your rules and comes back for your review, never to the customer.
Every edit you make is remembered. The same lesson on a second job becomes a standing rule. One click makes it a rule sooner.
Paste your rates, your terms, the notes you give a new hire. The rules come out as candidates and you say yes or no to each.
One switch puts the assistant on a two-minute schedule inside the database. Drafts happen while you are on a roof. Switch it off and the key it used is revoked.
Not in the prompt. In the database, where a model cannot talk its way around them.
The four questions a lawyer tells you to ask any software vendor that added AI, answered flatly.
Nothing you or your customers write is used to train anything. The model vendor today is Anthropic, called per task, and that is a configuration row you can read.
Every draft is yours the moment it lands. It sits in your workspace, sealed under your key, and leaves only when you send it.
The assistant only works at the steps of your process you gave it. Adding a step is your action, in your audit log, with your name on it.
The ledger holds every model call: model, tokens, cost, latency, request id, which job, which rules it was given. The audit log holds everything else. Both export.
The big platforms are building the same loop for 500-person contractors. Read their pages, then ours.
Model calls are passed through at cost and shown on your ledger. The plan pays for the desk.
No. It drafts. The database refuses any sender but the owner, by a trigger, not a setting. When you press send, your name is on the audit row.
You fix the draft and tell it one sentence. That sentence is a lesson; said again on another job it becomes a rule the next draft is given. Wrong drafts get rarer in your own words, not ours.
Three places: what you fix in drafts, what you paste in from a price list or terms document and approve, and what you type as a rule. All three end up in the same manual, which you can read and export.
Today Claude Sonnet drafts and reads messages and Claude Opus extracts rules from documents. The model for each task is a configuration row, so it can change without changing your rules or your data.
Model calls are billed at cost and every one is a ledger row with its price. Measured today: $0.012 at most to read a message, $0.004 to draft a quote email. Your workspace has a monthly cap that is enforced before a call runs.
No. A hard monthly cap per workspace and per person is checked before any call runs, and a refused reservation never reaches the model. The cap is yours to set.
Yes, at rest, field by field, under a key that belongs to your workspace and lives in the database vault. The database does not hold a name, an email, a phone number, a message or a draft in the clear.
Remove the starter kit with one button, or close the workspace. Your rules, your ledger and your audit log export first. Nothing of yours stays in a model.
Stet Desk runs on Stet, your business's institutional memory, which Claude and ChatGPT can use as a remote MCP server with the same rules. The desk is the version with an inbox and a process.
Twenty minutes, your real voicemail. We paste it in together and you watch the job open, the draft land, and the ledger row appear. Then you decide.