# Your first follow-up workflow

A worksheet by Jason Mohab-Ali. This document helps design a workflow; it does not activate integrations or send messages.

## 1. Choose one trigger
- When does the workflow begin? For example: an enquiry through your website.
- What outcome should the person making the enquiry experience?
- Who owns the follow-up?

## 2. Map the steps
| Step | Input | Action | Outcome | Who checks? |
| --- | --- | --- | --- | --- |
| Enquiry | Name, contact details, question | Check completeness | Usable enquiry | |
| Record | Checked enquiry | Find existing contact and prevent duplicates | Contact with context | |
| Prepare | Question and available information | Create a suitable draft reply | Draft, not yet sent | |
| Follow up | Approved reply | Send and plan the next action | Follow-up with an owner | |

## 3. Agree on boundaries
- Which data is actually needed?
- Who has access and how long will you retain the data?
- Which step requires human approval?
- When should automation stop or ask for help?
- What happens with a missing field, duplicate contact or unreachable tool?

## 4. Test with fictional data
1. Process one complete test enquiry without sending real messages.
2. Repeat the same enquiry: does it avoid duplicate contacts or follow-up?
3. Test incomplete input and a failed integration.
4. Check the error message and whether you can safely resume processing.
5. Have the responsible person review the outcome before activating the workflow.

## 5. Evaluate
- Which action became simpler?
- Which errors still occurred?
- Which data or actions are unnecessary?
- What will we change before the next test?

Start with one reliable step. Expand once the implementation works.