Skip to content
HeuriTel
Sign in
Customer Intelligence

Customer Acquisition & Market Share

Acquire the customer who is still there in ninety days, not the sale that leaves with the incentive.

When a prospect is qualified, compare the standard offer, a smaller incentive, a cheaper channel and no incentive, against likely value and the cost of the acquisition.

For Acquisition, dealer and digital-channel teams.

The decision, annotated from the record

A prospect is qualified through a dealer, a port-in request or a digital lead.

The first offer and incentive this prospect gets, its channel, and the point at which the acquisition is not worth its cost.

  1. The standard first offer through the channel that qualified the prospectConsidered
  2. A smaller incentive where the prospect's likely value does not justify the full oneConsidered
  3. The same offer through a cheaper channelConsidered
  4. No incentive, recorded, where the connection is likely to leave within a quarterConsidered
The safeguards, the action and the channels

Before anything reaches the customer: Consent to contact, duplicate identity, eligibility, incentive budget and dealer terms pass.

What would reach them: Present one first offer through the permitted channel and activate the connection on acceptance. On Retail, Dealer, Web, USSD.

A pilot's requirements are specified: the data, the authority and the consent design.

The journey, step by step. Read the journey in full

The journey below is written for a generic operator. Tell us your market and it will be presented in it.

Configure a demonstration
The decision

The first offer and incentive this prospect gets, its channel, and the point at which the acquisition is not worth its cost.

A prospect has been qualified through a dealer. The incentive would win the sale. Half the connections won that way last quarter were inactive within ninety days.

  • The standard first offer through the channel that qualified the prospect
  • A smaller incentive where the prospect's likely value does not justify the full one
  • The same offer through a cheaper channel
  • No incentive, recorded, where the connection is likely to leave within a quarter
The decision, step by step
  1. 01Eligibility rules
  2. 02propensity/uplift or value score
  3. 03treatment constraints
  4. 04ranked action including no-action
  5. 05decision log

The order, dealer and identity systems remain authoritative; HeuriTel proposes within the incentive budget and dealer terms.

What it does

Three things it helps you decide or do.

  • Qualify the prospect before the incentive is spent

    Source, consent, duplicate identity and comparable-customer value are read before an offer is made, so an incentive comes after the checks.

    In the record’s words
    • customer_id
    • account_type
    • tenure_days
    • active_products
    • recharge_30d
    • usage_30d
    • revenue_30d
    • last_contact
    • consent_status
    • outcome_label
  • Compare offers, incentives and channels, including none

    The standard offer, a smaller incentive, a cheaper channel and no incentive are ranked, and the consent, duplicate, eligibility and budget checks can refuse.

    In the record’s words
    • No consent
    • ineligible product
    • price/catalogue mismatch
    • contact cap
    • credit/fraud block
    • channel unavailable
    • control assignment
  • Measure acquisition on who stays

    Activation, ninety-day status and acquisition cost are recorded separately, so a signed connection counts as an acquired customer only once active at ninety days.

    In the record’s words
    • Decision log
    • eligibility snapshot
    • price/order response
    • delivery receipt
    • control assignment
    • revenue/outcome ledger
The journey

Acquire a customer who is still there after ninety days

Read the journey; a working session shows it running.

Customer Acquisition & Market Share: the situation this product is about
Step by step, from both sides

Acquisition, dealer and digital-channel teams

StepWhat the customer experiencesWhat the operator does
The momentThe moment that started it.A prospect is qualified through a dealer, a port-in request or a digital lead.Reads prospect source and how it was qualified, consent to contact and duplicate identity checks, likely value from comparable customers, incentive budget and dealer terms.
The decisionThe decision to be made.The customer's screen is unchanged.Ranks a first offer, a channel and an incentive against the prospect's likely value and the cost of acquiring them.
The safeguardsThe conditions that stop it.Still unchanged: the action waits until every check has passed.Consent to contact, duplicate identity, eligibility, incentive budget and dealer terms pass.
The actionThe action that reaches the customer.Present one first offer through the permitted channel and activate the connection on acceptance. Reaches them on Retail, Dealer, Web, USSD.Recommends. The system that holds the right confirms, charges or provisions.
When it goes wrongThe failure, and the recovery.The prospect is an existing customer under a second identity, and the incentive would pay for a connection the operator already has.The duplicate check stops the incentive, the dealer sees the reason, and the prospect is offered a legitimate second-line product instead.
The resultThe change it made.What changed for them is what is counted; nothing else is claimed.Activated connection still active and spending after ninety days, against acquisition cost.
The proofThe proof anyone can check.Can be answered for, later, from the record.Prospect source, consent, duplicate check, offer rationale, incentive, activation and ninety-day status.

Hypothesis

A connection that leaves within a quarter cost the incentive and the dealer commission and earned nothing; acquisition is measured on who stays, not on who signed.

Modelled

The mechanism that could produce the result, stated; the figure is measured in the pilot.

Observed

Measured in a pilot’s validate stage, on your systems, against a comparison agreed first.

The result, the mechanism, the measurement, and the record’s five answers
Desired result
Incremental revenue or retention; lower contact waste; improved conversion with margin guardrails
Mechanism
Ingest → qualify → score → apply limits/consent → assign control → execute approved action → capture delivery and business outcome → monitor/retrain
Measurement

Randomised holdout where feasible; intent-to-treat primary view; pre-declared denominator; guardrails for complaints, margin and opt-out

Measured on: Eligible population; treatment rate; conversion; incremental revenue; ARPU; churn; contact rate; margin; opt-out; decision latency

  1. 01
    Desired result

    The result wanted.

    Incremental revenue or retention; lower contact waste; improved conversion with margin guardrails

  2. 02
    Mechanism

    The mechanism that could produce it.

    Ingest → qualify → score → apply limits/consent → assign control → execute approved action → capture delivery and business outcome → monitor/retrain

  3. 03
    Evidence required

    The records kept to show it.

    Decision log; eligibility snapshot; price/order response; delivery receipt; control assignment; revenue/outcome ledger

  4. 04
    Costs and risks

    The cost, and the ways it can go wrong.

    Costs: Setup fee + annual product subscription; optional managed execution fee; optional verified-outcome fee with agreed baseline

    If it fails: Fail closed on eligibility/consent/price; queue retryable events; do not duplicate orders; route exception to campaign operations

  5. 05
    Measurement approach

    The measure that shows it helped.

    Randomised holdout where feasible; intent-to-treat primary view; pre-declared denominator; guardrails for complaints, margin and opt-out

    Measured on: Eligible population; treatment rate; conversion; incremental revenue; ARPU; churn; contact rate; margin; opt-out; decision latency

Measured in the pilot's validate stage, on your systems, with the comparison agreed first. Every line above is the record's own design intent.

The business side

The change
Activated connection still active and spending after ninety days, against acquisition cost.
Running cost
Setup fee + annual product subscription; optional managed execution fee; optional verified-outcome fee with agreed baseline
What evidence supports it
Prospect source, consent, duplicate check, offer rationale, incentive, activation and ninety-day status.
Technical detail

Inputs, decision logic, systems touched, records kept.

The four questions, field by field

What would we need from your systems, and how much history?

Attributes required

  • customer_id
  • account_type
  • tenure_days
  • active_products
  • recharge_30d
  • usage_30d
  • revenue_30d
  • last_contact
  • consent_status
  • outcome_label

Also useful, not required

  • Network experience
  • digital clickstream
  • complaints
  • location cohort
  • household/account links
  • partner purchases

8-12 weeks of customer, usage, revenue, product, contact and outcome history; stable customer key; one executable channel

The 14 definitions underneath

14 in this product

  1. HeuriTel Customer AcquisitionDecision definitionHT-0023

    Identify eligible records for customer acquisition, choose from approved actions including no action, execute through the system of record, and measure the agreed business outcome.

    /d/HT-0023
  2. HeuriTel Port-In AcquisitionDecision definitionHT-0024

    Identify eligible records for port-in acquisition, choose from approved actions including no action, execute through the system of record, and measure the agreed business outcome.

    /d/HT-0024
  3. HeuriTel Competitor Win-OverDecision definitionHT-0025

    Identify eligible records for competitor win-over, choose from approved actions including no action, execute through the system of record, and measure the agreed business outcome.

    /d/HT-0025
  4. HeuriTel Acquisition OffersDecision definitionHT-0026

    Identify eligible records for acquisition offers, choose from approved actions including no action, execute through the system of record, and measure the agreed business outcome.

    /d/HT-0026
  5. HeuriTel Acquisition Channel OptimisationDecision definitionHT-0027

    Identify eligible records for acquisition channel optimisation, choose from approved actions including no action, execute through the system of record, and measure the agreed business outcome.

    /d/HT-0027
  6. HeuriTel Referral AcquisitionDecision definitionHT-0028

    Identify eligible records for referral acquisition, choose from approved actions including no action, execute through the system of record, and measure the agreed business outcome.

    /d/HT-0028
  7. HeuriTel Lead ConversionDecision definitionHT-0029

    Identify eligible records for lead conversion, choose from approved actions including no action, execute through the system of record, and measure the agreed business outcome.

    /d/HT-0029
  8. HeuriTel Digital AcquisitionDecision definitionHT-0030

    Identify eligible records for digital acquisition, choose from approved actions including no action, execute through the system of record, and measure the agreed business outcome.

    /d/HT-0030
  9. HeuriTel Retail AcquisitionDecision definitionHT-0031

    Identify eligible records for retail acquisition, choose from approved actions including no action, execute through the system of record, and measure the agreed business outcome.

    /d/HT-0031
  10. HeuriTel Location-Based AcquisitionDecision definitionHT-0032

    Identify eligible records for location-based acquisition, choose from approved actions including no action, execute through the system of record, and measure the agreed business outcome.

    /d/HT-0032
  11. HeuriTel Market Share GrowthDecision definitionHT-0033

    Identify eligible records for market share growth, choose from approved actions including no action, execute through the system of record, and measure the agreed business outcome.

    /d/HT-0033
  12. HeuriTel Acquisition Cost OptimisationDecision definitionHT-0034

    Identify eligible records for acquisition cost optimisation, choose from approved actions including no action, execute through the system of record, and measure the agreed business outcome.

    /d/HT-0034
  13. HeuriTel Dealer Lead PrioritisationDecision definitionHT-0035

    Identify eligible records for dealer lead prioritisation, choose from approved actions including no action, execute through the system of record, and measure the agreed business outcome.

    /d/HT-0035
  14. HeuriTel Coverage-Led AcquisitionDecision definitionHT-0036

    Use network, customer and economic data to support coverage-led acquisition, with operator-approved actions, change controls and post-action verification.

    /d/HT-0036

Search definitions across every product

Implementing it

Four stages, and what has to be true before the next one starts.

12-16 weeks to pilot; 2-4 additional weeks per market after reusable interfaces exist.

  1. 01

    Scope

    One use case, one value unit and a denominator finance has agreed to. Without these there is nothing a later result can be compared against.

    • Confirm value unit
    • select use case
    • baseline denominator
  2. 02

    Connect

    The attributes mapped from your systems, and the decision and outcome interfaces working in both directions.

    • map attributes
    • integrate decision and outcome APIs
  3. 03

    Validate

    Eligibility agreed, a dry run with nothing sent, then a controlled pilot with a holdout that is actually respected.

    • build eligibility
    • dry run
    • controlled pilot
  4. 04

    Operate

    The live loop: decide, check, execute through your systems, capture what came back, and measure against the control.

    • Ingest
    • qualify
    • score
    • apply limits/consent
    • assign control
    • execute approved action
    • capture delivery and business outcome
    • monitor/retrain
The team, and the four states each assessed against your systems

Who does it. 1 telecom product lead · 1 CVM specialist · 1 data engineer · 1 ML engineer · 1 integration developer · 0.5 QA · 0.5 DevSecOps · 1 deployment coordinator

Readiness is assessed on your data, your integration and your authority.

Readiness

Needs client data and integration review

The client’s data and integration position.
Runtime / build state

Target product definition

What exists as running software.
Surface state

Not audited

Whether this product shows the entry anywhere.
Client status

Not assessed

Where a named client has reached.

Next steps from here.

See HeuriTel on the sample of your market

Verify your email to open a demonstration on the sample of your market.