How a bot hands an enquiry to a person

A sample workflow

Imagine an enquiry for a consultation. This is an educational scenario, not a client project. The user chooses a service, describes the task and confirms a contact. The bot shows a summary and allows corrections before submission.

States beyond the happy path

Before confirmation the enquiry is a draft. After confirmation the system assigns a reference and attempts CRM delivery. Repeated clicks should return the same enquiry state instead of creating another record.

If the CRM is unavailable, do not claim a manager received the enquiry. Depending on the implementation, save it in a reliable queue and explain the delay, or show an honest error with an alternative contact.

What the operator receives

An enquiry reference, service, task summary and permitted contact details. Pass only the context needed to help. Tell the user where the conversation continues; response hours and promises must match the team’s capacity.

Pre-launch checks

Test empty and invalid contacts, cancellation, repeated clicks and an unavailable CRM. Confirm that data is not lost or duplicated and a technical error is not displayed as success.

For WhatsApp, also check the business account, messaging permission, required templates and platform costs. A Telegram interface demonstration does not prove a working WhatsApp integration.

Measure different outcomes separately

A messenger click, delivered enquiry and qualified lead are different events. A manager records whether the enquiry fits the service, receives an estimate and becomes a paid project. Click counts alone cannot establish effectiveness.