Campaign attempts and unique contacts answer different questions. This guide helps analysts reconcile the rows before reporting reach or qualification. Use a stable, authorised contact reference and keep the phone event identifiers in a separate attempt ledger.
The steps below are a proposed operating method. Confirm supported actions in your configured HeyRik account before using them in a client commitment.
Define the grain of each record
An attempt row represents one initiated attempt under the chosen reporting definition. A contact row represents one business contact under the owner’s matching rules. A transferred phone interaction may also produce linked segments. Do not assume every provider identifier represents a new person.
Amazon Connect’s describe-contact documentation includes relationships such as the initial contact identifier. That illustrates why a segment count needs careful interpretation. Use the applicable relationships in your actual system rather than copying another provider’s schema.
Use two linked ledgers
- Attempt ledger: attempt ID, contact reference, campaign, initiated time and raw provider result.
- Contact ledger: stable business reference, matching-rule version and latest reviewed business state.
- Relationship field: links related segments or retries where the provider supplies that evidence.
- Exception list: missing reference, duplicate import, unresolved match or late event.
- Reconciliation date: completed period, time zone and extraction time.
Worked reconciliation: six attempts, three contacts
Illustrative rows: C1 has three attempts, C2 has two and C3 has one. The attempt count is six and the distinct referenced-contact count is three. If one attempt has no trusted contact reference, keep it in the attempt total and report the unique-contact count for the mapped subset with an unresolved row.
A shared family or business phone number does not establish that two contact records represent one person. Apply the approved matching rule and inspect uncertain matches before claiming unique people reached.
Close the period reproducibly
- 1Freeze the completed period and time zone.
- 2Identify late events and the rule for including them.
- 3Group attempts by trusted contact reference.
- 4Separate linked phone segments from genuinely new attempts.
- 5Review unmatched records and preserve corrections with a reason.
Connect the reconciliation to qualified outcomes
Report qualification using the correct unit: qualifying attempts, distinct qualified contacts or qualified accounts. State the denominator and evidence definition. Reconciliation improves interpretability; it does not demonstrate an increase in leads or revenue. Those outcomes need downstream records.
A little more before you begin.
Can we deduplicate everyone by phone number?
A number may be shared or changed. Use the business’s approved matching rules and retain uncertain matches for review.
Start here
Discuss the supported workflow for your BPO
Build a voice agent, upload your list or connect your leads, and run your first campaign on HeyRik — free to start, no credit card required.