Every business runs on steps that live in people's heads: how to answer a refund question, which invoices need a manager's approval, when to call a customer back. An AI agent cannot guess these rules. Writing them down is the single most useful thing you can do before building one, and it helps new staff too.
Start with one process, not the whole business
Pick a process that happens often and follows a pattern, such as answering order status questions, booking appointments or processing supplier invoices. Write it for that one job before moving on.
Write steps, not paragraphs
- Number each step and start it with a verb: check, ask, look up, send, book.
- Say where the information comes from: which system, which field, which document.
- Keep one action per step. If a step has an "and", it is probably two steps.
Write the rules for exceptions
Most mistakes happen at the edges. List the cases where the normal steps do not apply and say exactly what to do.
- If the amount is above a limit, send it to a named person for approval.
- If the customer is upset or mentions a complaint, hand off to a person.
- If the information is missing, ask for it once, then pass the case on.
Define what done looks like
For every process, say what the finished result is: the booking in the calendar, the record updated in the CRM, the confirmation sent. This gives the agent a clear finish line and gives you something to check.
Add real examples
Include three to five real examples, with personal details removed: a typical case, a tricky one and one that must go to a person. Examples teach faster than rules, for agents and people alike.
Keep it alive
An SOP is never finished. Give it an owner, date each change, and review it whenever the agent hands off something it should have handled. Over a few weeks, the gaps close and the agent gets steadily more useful.



























