Capture the enquiry once, assign an owner, set the next action, and show when it needs attention. Automate those repeatable steps before trying to automate the whole conversation.
- New enquiry
- Check for a match
- Assign an owner
- Prepare the next step
- Person reviews
1. Decide what a good handoff includes
Start with a recent enquiry and ask a colleague to continue the conversation using only the record you give them. If they need to search several chats to understand the request, the record is incomplete. A useful handoff explains who contacted you, what they need, what has already happened, and what someone should do next.
Choose a small set of statuses with meanings the whole team understands. For example, New means nobody has assessed it; Assigned means a named person owns it; Waiting means you need something from the prospect; Closed means no further action is planned. Do not use a status such as In progress without also recording the next action.
| Field | What to record |
|---|---|
| Enquiry ID | A stable reference for this request |
| Source | Form, email or permitted message channel |
| Request | The customer's question in a short summary |
| Owner | One named person responsible |
| Next action | A concrete step, such as checking requirements |
| Due time | A time the team has agreed it can meet |
| Last contact | What was sent, when, and by whom |
2. Keep one record for the same enquiry
A prospect may complete a form and then email the same question. Creating a fresh sales task for every message can make one opportunity look like two. Keep the original channel record or submission ID and use it when checking whether the event has already been handled.
Do not merge records only because two people have the same name. A shared company inbox can also represent different requests. When the match is uncertain, put it in a review list. Save enough context for a person to decide whether to combine it with an existing enquiry or open a separate one.
3. Set an owner and a backup
Decide how work is assigned before connecting the tools. A small business might send all new enquiries to one coordinator. A larger team might route them by service, region, or availability. Keep the rule easy to explain and provide a fallback when no rule matches.
An alert saying New lead is easy to dismiss. An assigned task saying Review the document request by tomorrow morning is easier to act on. Agree what happens when the owner is away or the task becomes overdue. Escalation should bring the record to the backup person, not send the same customer several competing replies.
- Assign by a written rule the team can understand.
- Use a shared queue when the correct owner is unknown.
- Notify the backup only when the agreed condition is met.
- Pause reminders when the enquiry is closed.
4. Prepare helpful replies without making promises
Automation can gather the request details, suggest missing questions, and prepare a draft reply. Keep firm prices, delivery dates, unusual requests, and sensitive conversations with a person who can make those decisions. A fast draft is useful only if it is accurate and appropriate.
For example, a design studio receives a request for 200 product images. The workflow records the enquiry, attaches the supplied brief, assigns a coordinator, and prepares questions about the required formats and deadline. The coordinator checks those questions before sending them. This is an illustrative workflow, not a report of a customer result.
5. Test the awkward cases before launch
A tidy sample enquiry is only one part of a test. Try a missing email address, a duplicate submission, a request outside your services, and an owner who is unavailable. Confirm that a failed connection becomes visible and the original request stays recoverable.
Test messages in a safe workspace or with your own agreed test recipients. Do not contact a real prospect repeatedly to check whether the automation works. If a retry is needed, verify whether the destination already received the first action. Zapier's documentation specifically notes that replaying a timed-out action may create duplicate data.
- The same event arrives twice: one task remains.
- Required details are missing: the record waits for review.
- The owner is absent: the backup gets a clear task.
- The destination is unavailable: the failure is visible.
- The customer declines: follow-up stops.
6. Measure the handoff, not just the alerts
For a short pilot, track how many enquiries have no owner, how many have an overdue next step, and how often the team has to correct a record. Compare the time needed to prepare the same kind of handoff before and after the change. Include the time spent reviewing and fixing it.
Separate enquiry handling from sales results. Faster assignment does not prove more revenue, and a clicked contact link is not automatically a qualified lead. Keep the first version small enough that your team can explain every step and take over manually if needed.
Your ready-to-use checklist
0 of 6 checked For your own planning
Your ticks stay in this open page only. No answers are sent to us.
Make the next step clear.
Use this brief with your team or an automation partner. Leave out passwords and confidential customer information.
Copy this handoff brief
Free templateSources and notes
Technical references checked on September 19, 2026. Product features and plans can change.
- Zapier: duplicate data and timeout replays
Supports the caution about duplicates when replaying a timed-out action. The checklist and studio scenario are AFB planning examples.