From an enquiry to a clear next step.

Use this as a starting map, then adapt it to the people, tools, and permissions involved. This site does not connect to a customer system or execute an automation.

The process

1. A relevant enquiry arrives

Identify the approved source, the fields you actually need, and the purpose for using them. Do not automatically add every enquiry to a marketing list.

2. Create or update the right record

Use a duplicate check and keep only necessary information. A repeated submission should not trigger conflicting actions.

3. Assign a real person

Someone owns the next step and any exceptions. Make it visible when the record lacks information or the integration fails.

4. Draft, then review

Use an approved response template if appropriate. A human checks context, promises, contact details, and whether the message should be sent.

5. Offer the right next step

Invite a booking or ask a clarifying question only when it fits the enquiry. Record what was offered; do not count an invitation as a booking.

Before this goes live

Use this local checklist to prepare the workflow. These checks are a starting point, not a full security or compliance assessment.

• The source and purpose of the enquiry are understood.
• Required fields and duplicate behavior are tested.
• An owner is assigned and can see exceptions.
• A human approves customer-facing messages.
• A failed integration has an alert and a manual fallback.
• Bookings, enquiries, and sales are recorded as different events.

Checklist saved in this browser only. Clear these checks

Choose tools last

Start with the systems already in use. A new tool needs a specific job and a responsible owner. Confirm supported actions, plan requirements, data handling, and failure behavior before enabling an integration.

Explore tools by the work they support →