Paying once for each customer
Define how repeated enquiries and orders should count across your acquisition sources. LeadScale brings agreed duplicate and frequency rules into the processing flow, with delivery evidence to support the supplier acceptance decision.
The LeadScale Engine™ supports deduplication and frequency controls across records in a configured processing flow. For telecoms acquisition, agree which repeats matter and how to handle them, then define any downstream outcome the programme needs. Record checks inform acceptance decisions; supplier terms determine what is payable, and activation is a separate event.
Put the repeat rule where the records meet
The same person may appear through more than one acquisition journey. Comparing only within each source leaves the programme's view fragmented. Agree which routes enter the flow, what makes a repeat relevant and what action the programme should take.
- Identify the inputs. Establish the sources, fields and routes supplying acquisition records.
- Define the repeat. Agree deduplication and frequency requirements, including legitimate further requests.
- Apply the handling. The Engine runs the agreed contact and repeat checks before onward delivery, with failed-result handling set for the programme.
- Use the delivery evidence. Where supply is against an order, reconciliation relates delivery to it. Review that evidence alongside the supplier's acceptance terms.
Connect acceptance criteria with supplier terms
Consider a person submitting the same request through two sources while the first order is still being followed up. The programme needs a rule for the second submission. The supplier agreement needs to say how that situation affects acceptance and payment.
Now consider the same person returning for another service. That may be a legitimate new request. Set out how the available record information and frequency rules should handle it.
Separately, decide which later event measures acquisition success. The client and LeadScale agree what the programme is trying to optimise for. Where you share outcome data, the Engine and connected systems can be configured around those outcomes.
Repeat-order processing at Vodafone
Needs approval
Vodafone's consumer acquisition programme brought several journeys into a shared processing flow. Programme rules addressed repeat-order behaviour and onward routing, while downstream outcomes returned to the Engine.
End
Include the later event if activation matters
If the programme is judged on activation, identify the system that records it and the information it can return. Scope that connection alongside the record processing. The supplier agreement determines the payable event.
Questions from telecoms acquisition teams
Can repeat controls work across several sources?
Yes, where their records enter the configured flow. Agree the routes and available data together, so the comparison covers the inputs your programme needs.
How should we define a duplicate?
Specify the repeated request you want to control, the available comparison information and any frequency requirement. Include how legitimate further requests should be handled.
Can activation outcomes feed advertising platforms?
Assess the event recorded by your systems and the signal accepted by the advertising destination. Agreed outcomes can feed back where the programme and connections support the return.
Where are repeat records creating a dispute?
Bring the acquisition routes, repeat rules and supplier acceptance terms. We'll discuss the processing and outcome information needed to make the decisions clearer.