Source reporting loses the booking reference
The appointment count is visible, but it cannot be linked reliably to the original enquiry. Campaign attribution becomes a manual matching exercise.
The situation
What this can look like
Marketing sees a lead list while sales sees bookings. Without a shared reference, someone compares names and dates to decide which source deserves credit.
A practical example
A franchise recruitment prospect books an introductory call after coming through a specific regional campaign. The appointment record stores the contact name, while the original enquiry stores the campaign reference; neither contains a usable relationship to the other. Reporting cannot confidently identify which request produced the booking, even though both events are real.
The friction
Why the next step stalls
A name is not a stable connection between events. This missing identity can be an integration-design issue rather than a reporting-interface problem.
A relevant next step
Put the next action around this request
Agree enquiry and appointment identifiers that survive the journey. Conversion24 can return the booking outcome against the mapped source record. Keep any attribution model separate from the technical fact that a booking belongs to a specific request.
What Conversion24 configures for this situation
C24's implementation reviews the source identifier, calendar result and agreed CRM return together. Your system owner determines which reference links the configured outcome to the original enquiry. We test one complete request-to-booking path rather than rely on a matching display name. Bespoke attribution or reporting work is scoped separately. The agent uses the relevant franchise context in its opening, while your team analyses observed linked records without fabricating campaign credit for appointments whose source relationship cannot be established.
The missing link: events reconciled.
Where the conversation can stall
- Source record
- Unlinked appointment
- Attribution guessed
A route to a relevant next step
- Identifiers mapped
- Events reconciled
- Source relationship verifiable
What to check in your own flow
Trace several appointments back through the identifier chain. Mark unmatched outcomes explicitly rather than assigning them to the most plausible campaign.
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 enquiry identifiers and appointment references. We can map the opening, the appropriate next step and the outcome your team needs in the CRM.