A good reply does not automatically resolve a request
An email can ask for information and require a decision at the same time. Generating a friendly response may leave the actual work untouched.
We developed a FRED email workflow that structures the case before drafting. It connects permitted information retrieval to an appropriate handling procedure and separates the draft from further actions.
What needs checking before the reply?
Illustrative example: a customer asks about an invoice and also requests review of a disputed case. Invoice information may answer one part. The disputed decision remains a separate task. This example is fictional.

One draft, several responsibilities
| Component | Purpose |
|---|---|
| Information | What is known from permitted sources? |
| Draft response | What can already be said to the sender? |
| Human task | Who still needs to decide or act? |
| Outcome evidence | Which step has actually been confirmed? |
A new message can supersede an earlier draft. The implemented handling therefore accounts for the relationship between the message state and the prepared result.

AI helps build the process and prepare the work
The solution goes beyond generating text: source access, procedure selection, preparation and outcome states were developed with AI. Permission to automate particular actions is defined separately.
This article does not claim blanket approval for automatic emails. It shows how AI can prepare a case people can review. Missing or conflicting information is part of that result too.
Which email repeatedly needs more than a reply in your organisation?
Sources.
- SolvraONE: own development and technical source reviewOwn source · As of



