The short answer
The workflow writes a draft within fixed rules and from fixed sources. It never sends. An employee reads, adjusts or rejects and sends it themselves. That is deliberate: a wrong draft costs a minute, a sent mistake costs a customer.
The concrete problem
Someone starts from a blank page every time. In the rush, the text promises a time, a rate or a credit note that has not been checked yet. The expensive part is not the typing. The expensive part is the commitment you then have to take back.
Who this is for
Decision-maker
You want to respond faster without AI promising anything on behalf of the company.
The person writing the email
You want a draft that uses the facts from the source, with the forbidden sentences already taken out, so that you only add tone and decision.
Now versus after
| Now | After delivery |
| Start blank, look up the facts again | Draft with source, missing fields and regime |
| A price or date is sometimes already in the first sentence | Those sentences are out by default. You may put them in |
| Unknown who sent what | Approval is logged before anything goes out |
What you receive
- Baseline measurement of volume, minutes until the reply is sent, and how often a draft is reversed.
- Draft text per agreed email type, with forbidden commitments in code.
- Approve, adjust or reject before anything is sent.
- Test on real emails and a final measurement.
- Handover to whoever handles the inbox afterwards.
Where you can see the working example
The four enquiries on inbox and email show the draft per regime: fault report without a time, maintenance without a price, credit note without a commitment, spam without a reply.
Systems
The mailbox the reply has to come from, plus the records or system that hold customer status and rates. Sending via SMTP or the software only happens after approval, or not at all if that integration falls outside the scope.
Data and human control
The model may only see the text of this email and the fields the rule needs. It may not search for additional customer files on its own. Sending remains a human action. See security.
One process working in ten working days
From the agreed start and complete information: baseline and design, followed by build, testing, final measurement and handover within ten working days. This is one process. If you combine it with inbox sorting or case-file preparation, that is a second process of €1,500, or the AI Operating System of €4,500 where everything comes together. The route is on the how it works page.
Limits
No autonomous sending. No marketing copy or cold outreach. No second language or second channel in the same assignment, unless agreed in the diagnosis. Reading attachments is document checks.
Price
€1,500 excluding VAT, ten working days, one process. You pay half at the start and half at delivery. If it does not work as agreed, I fix it or you get your money back. The choice is yours. Check the numbers in the calculator.
Frequently asked questions
Does the workflow send the draft itself?
No. The draft waits until an employee approves, adjusts or rejects it.
May the draft mention a price or date?
No, unless you explicitly allow it in the rules. In the standard set-up the model may not commit to a price, delivery date or credit note.