Skip to content
HeuriTel
Sign in
Offer, Pack and Pricing Intelligence

Home Broadband, Fibre & FWA

Sell only the broadband that can be installed at the address, and say when it cannot.

When a household asks for broadband, compare fibre, fixed wireless, a mobile fallback and no offer against serviceability, installation capacity and what the household needs.

For Broadband, fibre and fixed-wireless teams.

Read the journey More in Offer, Pack and Pricing Intelligence
The decision, annotated from the record

A household asks for broadband, or a mobile customer's home usage says they need it.

The service this address can take, its installation date, and the offer that stands in when the answer is not yet.

  1. Fibre, where the address is serviceable and an installation can be bookedConsidered
  2. Fixed wireless, where fibre is not available and the signal supports itConsidered
  3. A mobile-data fallback until the address is serviceableConsidered
  4. No offer, with the serviceability position and a date to check againConsidered
The safeguards, the action and the channels

Before anything reaches the customer: Address serviceability, installation capacity, plan eligibility, price, consent and credit checks pass.

What would reach them: Offer the service the address can take, book the installation, and confirm the plan only when the appointment exists. On Web, App, Retail, Call.

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 service this address can take, its installation date, and the offer that stands in when the answer is not yet.

A household wants fibre. The map says the street is covered. The last three orders on that street were cancelled after the installer found no port.

  • Fibre, where the address is serviceable and an installation can be booked
  • Fixed wireless, where fibre is not available and the signal supports it
  • A mobile-data fallback until the address is serviceable
  • No offer, with the serviceability position and a date to check again
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 network's serviceability and the order system decide what can be installed and when; HeuriTel proposes within their answers.

What it does

Three things it helps you decide or do.

  • Read serviceability from the network, not the map

    Address serviceability, installation capacity, household usage and eligibility are what a broadband offer is judged on, before a plan is quoted.

    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

  • Offer fibre, wireless, a fallback or nothing yet

    Four answers to one address are ranked together, and the serviceability, capacity, eligibility, price, consent and credit checks can refuse any of them.

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

  • Distinguish the sale from the installation

    Quote, appointment, installation and activation are recorded separately, so a home counts as connected at activation.

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

Sell only the broadband that can be installed at the address

Read the journey; a working session shows it running.

Home Broadband, Fibre & FWA: the situation this product is about
Step by step, from both sides

Broadband, fibre and fixed-wireless teams

What the customer experiencesWhat the operator does
The momentThe moment that started it.A household asks for broadband, or a mobile customer's home usage says they need it.Reads address serviceability from the network's own records, installation capacity and appointment availability, household usage and plan eligibility, consent, credit and the services already held.
The decisionThe decision to be made.The customer's screen is unchanged.Ranks fibre, fixed wireless, a mobile-data fallback or no offer against serviceability at the address.
The safeguardsThe conditions that stop it.Still unchanged: the action waits until every check has passed.Address serviceability, installation capacity, plan eligibility, price, consent and credit checks pass.
The actionThe action that reaches the customer.Offer the service the address can take, book the installation, and confirm the plan only when the appointment exists. Reaches them on Web, App, Retail, Call.Recommends. The system that holds the right confirms, charges or provisions.
When it goes wrongThe failure, and the recovery.The sale is confirmed on the map's coverage, and the installer finds no port; the customer has already cancelled their previous provider.The plan is confirmed only when the appointment exists, a failed installation is recorded against the address rather than the customer, and the fallback is offered before the previous service is cancelled.
The resultThe change it made.What changed for them is what is counted; nothing else is claimed.Installed and active services, against sales that could not be installed.
The proofThe proof anyone can check.Can be answered for, later, from the record.Address, serviceability result, plan quote, appointment, installation record, activation and first month.
View requirements Read the journey in full

Hypothesis

An installed service is a household kept for years; a sale that cannot be installed is a cancellation and a complaint on the same day.

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
Installed and active services, against sales that could not be installed.
Running cost
Setup fee + annual product subscription; optional managed execution fee; optional verified-outcome fee with agreed baseline
What evidence supports it
Address, serviceability result, plan quote, appointment, installation record, activation and first month.
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 Home Broadband GrowthDecision definitionHT-0328

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

    /d/HT-0328
  2. HeuriTel Fibre GrowthDecision definitionHT-0329

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

    /d/HT-0329
  3. HeuriTel FWA GrowthDecision definitionHT-0330

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

    /d/HT-0330
  4. HeuriTel Broadband AcquisitionDecision definitionHT-0331

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

    /d/HT-0331
  5. HeuriTel Broadband Churn PreventionDecision definitionHT-0332

    Identify customers with a defined near-term churn risk, select only economically justified retention actions, and measure incremental saves against a holdout.

    /d/HT-0332
  6. HeuriTel Broadband UpsellDecision definitionHT-0333

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

    /d/HT-0333
  7. HeuriTel Speed Tier UpgradeDecision definitionHT-0334

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

    /d/HT-0334
  8. HeuriTel Broadband ExperienceDecision definitionHT-0335

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

    /d/HT-0335
  9. HeuriTel Broadband Proactive CareDecision definitionHT-0336

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

    /d/HT-0336
  10. HeuriTel Router UpgradeDecision definitionHT-0337

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

    /d/HT-0337
  11. HeuriTel Wi-Fi ExperienceDecision definitionHT-0338

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

    /d/HT-0338
  12. HeuriTel Fibre Rollout DemandDecision definitionHT-0339

    Use network, customer and economic data to support fibre rollout demand, with operator-approved actions, change controls and post-action verification.

    /d/HT-0339
  13. HeuriTel FWA Capacity-Aware SalesDecision definitionHT-0340

    Use network, customer and economic data to support fwa capacity-aware sales, with operator-approved actions, change controls and post-action verification.

    /d/HT-0340
  14. HeuriTel Broadband Installation AppointmentDecision definitionHT-0341

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

    /d/HT-0341

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.

Read the whole journey Read the scenario in full The rest of Offer, Pack and Pricing Intelligence Ask a question first
Related products, and why

In the same area: Customer retention and the next best pack

Which customer should hear from us, with what, and through where?