An appointment request is reported as confirmed
The person submits a preferred time. The business has not accepted it, but the journey labels the request as a booked appointment.
The situation
What this can look like
The customer expects a visit while the branch treats the entry as a request to review. Sales reporting counts it as complete before the final time is agreed.
A practical example
A vehicle buyer replies that they would like a test drive on Friday afternoon. The dealer still needs to confirm the demonstrator and appointment. Reporting that reply as booked overstates progress and can leave the customer expecting a visit nobody has arranged. A requested time and a confirmed calendar event are different states.
The friction
Why the next step stalls
Request and confirmation are separate states unless the booking integration truly confirms availability. Confusing them creates customer expectations that operations may not be able to fulfil.
A relevant next step
Put the next action around this request
Agree when a requested appointment becomes confirmed and which system supplies that event. Conversion24 can return both stages separately through the mapping. Use wording that describes the actual state while your team resolves any pending request.
What Conversion24 configures for this situation
C24's configuration defines the intended appointment outcome with your dealer and calendar owner. We check whether the selected route books directly or hands a request to the dealership for confirmation. The agent's wording must reflect that distinction, and the CRM result should retain the relevant vehicle and requested timing. Your dealer confirms vehicle availability and any specialist conditions. Testing the two states before launch keeps the commercial report aligned with what the customer was actually told.
The missing link: availability accepted.
Where the conversation can stall
- Time requested
- Confirmation implied
- Branch still reviewing
A route to a relevant next step
- Request labelled honestly
- Availability accepted
- Confirmed outcome recorded
What to check in your own flow
Trace a preferred-time submission through acceptance. Verify the final confirmation message and reporting status against the branch's appointment record.
Playbook scope and purchase terms
- Contact route
- WhatsApp and AI voice can work together where approved for the enquiry. A full playbook supports up to ten attempts in five days; short single-channel playbooks have a different scope.
- Ownership
- Conversion24 supplements your CRM. Agreed outcomes return through the mapped handoff. Your team owns specialist advice, proposals and delivery.
- Purchase
- Businesses with fewer than 100 monthly leads can use the service. Minimum purchase: 100 playbooks per month. Messaging, voice usage and applicable setup costs are separate. Review current pricing.
- Configuration
- Your team supplies business information and reviews the agent's identity, terminology, FAQs, appointment rules and handover. Standard playbook logic is fixed. Bespoke flows, additional integrations, A/B tests and specialist analysis are scoped separately. Explore implementation.
See the follow-up route in a demo.
Bring your requested-versus-confirmed booking events. We can map the opening, the appropriate next step and the outcome your team needs in the CRM.