The short answer
Write the manual rule before implementing the automation. Define the trigger, action, exceptions and evidence that the task completed correctly.
Before you start
- Map the enquiry from arrival through assignment, response, qualification and the next sales step.
- Collect representative successful, rejected and interrupted journeys with the relevant timestamps.
- Agree an owner and a fallback for every handoff that could otherwise leave a prospect waiting.
Put it into practice
01Define the starting point
Choose a narrow workflow such as assigning a new enquiry or reminding an owner about an unanswered request. Avoid combining many unrelated actions in the first release.
02Build the next step
Make repeated events safe. Forms, webhooks and retries can create duplicates. Use stable identifiers and document how existing records are updated rather than creating a new contact every time.
03Review the evidence
Build visibility and recovery. Failed actions need a log, alert or queue that someone actually checks. A silent automation is not reliable merely because it worked during the first demonstration.
A worked example
A mistake to avoid
Avoid sending automated customer messages without a clear purpose and appropriate permission. Internal efficiency does not justify confusing or unexpected outreach.
How to evaluate the result
Test the process with realistic exceptions, not just the ideal path. Include missing information, duplicate events, unavailable owners and a temporary integration failure. Confirm that the original enquiry remains recoverable and that someone can see unresolved work. Evaluate operational quality alongside conversion: response relevance, correct routing and consistent qualification all affect the commercial result. Use customer feedback and record review to explain failure reasons before automating more steps. A dependable manual process is a better starting point than a complex workflow nobody can inspect.
Apply this to your business
Specify one workflow using trigger, input, validation, action, duplicate handling, failure route and owner. Test both the expected path and the most likely interruption.
Your working notes
Copy these prompts into your project document. Keep observations separate from assumptions and give the next action an owner.
- Trigger, responsible person and next action
- Exception handling and recovery route
- Verified delivery, response and commercial outcome
Record what happened at the next review. If the evidence is incomplete, write down what would resolve the uncertainty instead of forcing a positive or negative verdict.