See the workflow
From an enquiry to a booked conversation
A useful first implementation connects one enquiry source to one CRM pipeline. This illustrative example shows the steps to agree before a build. It uses sample data and does not report a client result.
- Capture: receive the website or chatbot enquiry and its source.
- Qualify: collect the service required, location, budget band and preferred contact time. Offer a person when an answer is uncertain.
- Update the CRM: find an existing contact before creating a record; store the enquiry and communication preferences.
- Assign: route the opportunity to the agreed owner, with a task when a human decision is needed.
- Follow up: send the agreed acknowledgement and eligible follow-up messages; stop the sequence when the person replies or opts out.
- Book: offer an available appointment and record the confirmation. A failed booking becomes a task for the owner.
- Report: count enquiries, qualified opportunities, bookings and failed actions. Compare results over an agreed measurement period.
Inspect the sample CRM record
{
"enquiry_reference": "DEMO-001",
"source": "website_chat",
"service_required": "CRM follow-up automation",
"budget_band": "£8,000 - £20,000",
"location": "UK",
"pipeline_stage": "Needs scope call",
"owner": "Assigned sales contact",
"marketing_opt_in": false,
"next_action": "Arrange requested scope call"
}
Your field names, consent rules and pipeline stages are mapped during discovery. The budget band is sample enquiry data, not a package quote.
What happens when something fails?
A repeated enquiry updates the existing record. An unavailable CRM queues the action and alerts its owner after the agreed retry limit. An unanswered question goes to a person with the conversation attached. Acceptance testing should cover these paths as well as a successful booking.
Bring one current enquiry and a screenshot of your pipeline to the scope call. We can agree the starting workflow, systems, acceptance tests and a fixed build proposal.