The customer chooses messaging and still gets calls
A contact preference is captured, but it does not affect the sequence. The customer experiences a route they did not select.
The situation
What this can look like
Someone asks for a written reply because they cannot take calls at work. An adviser sees a new enquiry and rings anyway; the preference remains buried in the record.
A practical example
A solar prospect requests a written exchange while travelling abroad. The preference concerns how to begin, not necessarily a permanent refusal to speak. If they later request a call, that new answer should guide the next step. A default voice-heavy sequence that ignores both preferences creates contact effort without respecting the actual conversation.
The friction
Why the next step stalls
Preference, permission and availability need to inform the same routing decision. Collecting an option on a form creates an expectation that the follow-up will use it.
A relevant next step
Put the next action around this request
Map the selected preference to an approved messaging-only, voice-only or combined playbook. Conversion24 can return changed preferences to the CRM while keeping subsequent steps inside the agreed route. Define exceptions before offering choices you cannot honour.
What Conversion24 configures for this situation
Conversion24 reviews the selected message-first, voice-first or short-channel approach with you. Your supplied preferences and contact rules need to match what that configuration can honour. We agree the outcome mapping for a changed route or timing request, and scope bespoke logic when standard playbook behaviour is insufficient. The practical aim is continuity: the agent knows the enquiry purpose, and your CRM records the contact preference alongside the result instead of burying it in an unrelated note.
The missing link: suitable playbook selected.
Where the conversation can stall
- Preference selected
- Default route wins
- Contact feels mismatched
A route to a relevant next step
- Preference mapped
- Suitable playbook selected
- Changes returned to CRM
What to check in your own flow
Test each preference option with a sample enquiry. Check actual scheduled actions, not just whether the selected value exists in a field.
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 contact-choice fields and route definitions. We can map the opening, the appropriate next step and the outcome your team needs in the CRM.