Choose the work before choosing the tool
For one week, note where you copy the same details, check whether somebody has replied or remind a colleague to take the next step. Pick a task that happens often enough to matter and has a clear beginning and end.
Describe it as: when this happens, check these conditions, then take this action. Include the person responsible if it does not work. “Automate admin” is too broad to scope or test; “create a follow-up task for a new website enquiry, unless a call is already booked” is specific.
Do not begin by connecting every app. An unclear manual process can become an unclear automated process that runs faster and is harder to notice. Sometimes a better form, a shared checklist or a simpler handover is the right first change.
1. Route a new enquiry to an owner
Trigger: an enquiry arrives through an agreed form. Action: save the useful details, assign the responsible person and create the next task. The notification should explain what happened and where to find the record.
In a hypothetical home-services business, the owner might see the service requested, broad area and customer’s preferred contact route. If a call is already booked, the task could be to prepare rather than chase the customer to arrange one.
Exception to test: the same person submits twice. Decide whether to update their contact and preserve a single open opportunity, or create a separate job when that is genuinely what they requested. Repeated alerts and duplicated tasks can make the system less useful.
2. Confirm bookings and remind the right people
Trigger: a valid appointment is confirmed in the chosen calendar. Action: send the appropriate operational confirmation and prepare the staff member with the available notes.
Agree the time zone, duration, buffers, working hours and cancellation route. Tell the customer whether the appointment is by phone, video or in person, and who initiates it. Keep reminders proportionate to the service and the customer’s communication preferences.
Exception to test: the customer reschedules or cancels after a reminder has been queued. The old appointment should not continue producing misleading reminders. Check the new time, staff availability and opportunity stage through the actual booking journey.
3. Prompt quote follow-up without pestering people
Trigger: a proposal is recorded as sent. Action: create a task for the owner to check whether the customer has questions at an agreed point.
A personal task is often a sensible first version. It lets the owner see the latest conversation, account for an agreed decision date and avoid sending a generic chase to somebody who has already replied.
Exception to test: the quote is accepted, declined or replaced. The previous follow-up should stop or change. If you later automate messages, assess the recipient, purpose, permissions and applicable messaging rules before enabling them. A contact entering the CRM is not blanket permission for promotional sequences.
4. Request feedback after a completed service
Trigger: a genuine service has reached the agreed completion point. Action: invite appropriate customer feedback through a supported route.
Decide whether the business first needs a human check that the work is complete and the recipient is correct. Keep the request clear, avoid pressure, and do not invent or rewrite a customer’s review. Treat complaints as work to resolve, rather than designing a process that only asks happy customers for a public rating.
Exception to test: a completed job is reopened, the customer has already responded, or a duplicate completion event arrives. The process needs a way to avoid repeatedly asking the same person. Any platform-specific review or messaging requirements need checking for the actual route.
5. Prepare onboarding after acceptance and payment checks
Trigger: the defined acceptance and payment gate is met. Action: create the project checklist, assign the owner and request the agreed inputs through an appropriate channel.
For a website project that might mean a brief, approved branding, image rights, reference websites and a list of existing accounts that need access. Use secure access methods rather than asking the customer to paste passwords into an ordinary questionnaire.
Exception to test: a repeated payment event, an unpaid invoice, a refund or an acceptance that has not actually been recorded. An email saying “paid” is not itself a verified payment record. Keep the human gate until the billing connection and reconciliation rules have been properly tested.
Write a short test plan before switching it on
| Decision | What to record |
|---|---|
| Trigger | The exact event and which account it belongs to |
| Conditions | Who qualifies, and when the action should not happen |
| Owner | The person responsible for the result and exceptions |
| Duplicate handling | What happens if the event arrives twice |
| Failure route | How a failed action becomes visible and is resolved |
| Stop rule | Acceptance, cancellation, response or another ending condition |
Use authorised fictional records and supported test facilities. Rehearse the ordinary journey, a missing field, a repeat event, a cancellation and a failure. Check the destination record and notification instead of assuming a green connection badge proves success.
Record any platform, seat, message or phone costs, and set appropriate usage controls. Agree who checks the workflow after launch and how it is paused safely. Automation needs an operating owner, even when a provider runs the underlying service.
When custom software is the better conversation
Supported tools are usually worth assessing first. A custom internal tool becomes a separate option when a defined process cannot be handled cleanly by the existing platform: for example, a specialist quoting calculation, a job-specific staff view or a single-business customer request portal.
Custom work needs its own discovery, access and recovery decisions, ongoing cost estimate and relevant independent review. It is not an unlimited addition to a website package. See our business software service for the assessment route.
For a first project, bring one repetitive task and a real example with private details removed. We can discuss whether a form, CRM process, supported automation or custom tool is the sensible route. The aim is a reliable next step your team understands, rather than the largest possible collection of workflows.