The lead fee is treated as the complete follow-up cost
The budget uses one processing price and overlooks messaging, voice usage or agreed setup costs. The financial review begins with an incomplete total.
The situation
What this can look like
A team chooses a route using the engine fee alone. Different contact patterns create different usage costs, so the later comparison does not match the original assumption.
A practical example
An estate-agency owner budgets only the playbook purchase, then discovers that a voice-heavy route produces separate call usage and messaging charges. The selected sequence and actual conversations affect those components. Comparing the full cost with the existing process requires a realistic usage view, not a per-lead number treated as an all-inclusive monthly invoice.
The friction
Why the next step stalls
A processing charge and channel usage describe separate parts of the commercial model. Excluding either makes the cost of an appointment hard to interpret fairly.
A relevant next step
Put the next action around this request
Review expected volume, selected playbook, channel usage and applicable setup with Conversion24 before evaluating the route. Use the current published pricing or agreed proposal. Your finance owner can connect actual cost with confirmed booking outcomes without assuming every processed lead books.
What Conversion24 configures for this situation
Conversion24 reviews the chosen channel mix and commercial scope with you. The AI engine purchase, messaging, AI voice usage and applicable setup or custom work have separate terms on the pricing page. Your own WhatsApp Business Account is used where selected, with Meta billing those messages directly. We distinguish standard configuration from additional integration requirements before launch. The business then evaluates the complete commitment against its follow-up objective without assuming that a particular volume or channel pattern necessarily guarantees savings.
The missing link: usage measured.
Where the conversation can stall
- Engine fee budgeted
- Usage omitted
- Full cost misunderstood
A route to a relevant next step
- Cost components listed
- Usage measured
- Appointment cost assessed consistently
What to check in your own flow
List what is included and excluded beside each estimate. Keep projected usage separate from invoiced usage and compare the same cohort of appointments.
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 cost assumptions and channel-usage breakdown. We can map the opening, the appropriate next step and the outcome your team needs in the CRM.