Repeated calls can belong to one booking journey. Attribute the business outcome once while preserving every interaction’s operational role, so answered-call growth does not become double-counted booking growth.
Attribution needs a unit of business intent
Repeat-call attribution links interactions to a distinct opportunity and authoritative booking. One customer may make several enquiries, and several callers may coordinate one appointment, so a telephone number alone is not a sufficient rule.
For a proposed model, keep separate interaction, customer, opportunity, and appointment references. Record the matching evidence and any uncertainty. Define the attribution window and whether the report describes first contact, last contact, assisted handling, or an explicitly estimated incremental effect.
These attribution views answer different questions. A receptionist can assist a booking without being the sole source of the customer or the reason the customer chose the business.
Follow a fictional three-call journey
A caller asks about pricing on Monday, calls again to provide an address on Tuesday, and confirms a time with staff on Wednesday. The business creates one appointment. The report should show three interactions and one booking, with the receptionist’s contribution labelled according to the chosen rule.
If the same caller later requests unrelated work at another property, that may be a new opportunity. Do not suppress legitimate business activity simply because the phone number already appeared within the reporting period.
| Journey pattern | Counting rule |
|---|---|
| Repeat clarification for same visit | One opportunity, multiple interactions |
| Booking rescheduled | Same appointment lineage where supported |
| Separate service request | New opportunity if the business definition fits |
| Different caller for same household visit | Reconcile through authorised evidence |
| Uncertain match | Keep unresolved attribution visible |
Test changed phone numbers and shared numbers. Automatic matching can merge unrelated people or split one journey into several apparent customers.
Report contributions without forcing exclusivity
First-touch and last-touch views can be useful, but neither establishes causation. Assisted-contact reporting can show the receptionist participated while keeping the final appointment count deduplicated. Revenue should attach to the underlying transaction once.
More detailed linkage increases data work and privacy exposure. Use only the identifiers needed for the approved purpose and restrict joins to authorised roles. Where evidence is weak, report a range or an unknown category rather than assigning every booking confidently.
This attribution design is proposed. The HVAC case study describes customer and request history without claiming booking attribution results. Pair it with qualified enquiry measurement.
Repeat-call attribution FAQ
Should each answered call count as a booking lead?
Count interactions separately from distinct opportunities and completed appointments.
Can a phone number uniquely identify the journey?
No. Shared and changed numbers require additional authorised context.
Which attribution model is correct?
Choose the model that answers the business question, state its limits, and keep the underlying booking and revenue deduplicated.