Picture a small services team with a shared inbox. An inquiry arrives on Friday evening. Nobody owns it, so it waits. By Monday, someone reads it, forwards it, and asks a colleague what to do.
This is a hypothetical example, not a client story. It is a good one for a first workflow, because the stakes are low and the steps are easy to see.
What a simple intake workflow does
The workflow does a few small things when a message arrives:
- Reads the message and sorts it into a type, such as sales question, support request or something else.
- Looks up basic context in a read-only source, such as a public product list or an internal FAQ.
- Writes a draft reply and a short summary for a person to review.
That is the whole scope. The workflow does not send anything. It does not change records. It prepares work so a person can pick it up quickly on Monday.
What changes
The inquiry no longer sits as raw text. The person who opens it finds a label, a one-paragraph summary, the context the lookup found and a draft reply. They can edit the draft, send it, or throw it away.
The wait does not disappear. A person still answers. What changes is how much work is left when they sit down to do it.
The checks that matter
A workflow this small still needs checks. These are the ones I would start with:
- Can the lookup only read? Test it by trying a write and confirming it fails.
- What does the draft say when the lookup finds nothing? It should say so, not guess.
- Who sees the inbox contents, and where do copies of the messages go? Inquiries contain names and email addresses. Low risk is not no risk.
If the workflow connects to its tools through MCP, the permissions on that connection belong in the same review. If it does not use MCP, there is nothing extra to audit.
The handoff
The last piece is the handoff. Someone should be able to answer three questions in a minute: what does it do, what can it touch, and how do we turn it off?
Write those answers on one page. If a colleague can read it and run the workflow without asking you, the handoff works.
Starting point
Pick one inbox and one message type. Run the workflow in draft-only mode for a couple of weeks and compare its drafts with what people actually send. Change one thing at a time.
That is a bounded piece of work, and it can be reviewed from start to finish. It does not need a company-wide plan.
I'm Jonathan Melton. I run FusionAL, focused on reviewing and integrating lower-risk internal AI workflows, one bounded workflow at a time.
Top comments (0)