DeterministicDay oneModerate complexityLevel 2 Refined bespoke
Reachability & Consent
Measures how much of your base is contactable per channel given consent and contact tokens, and sizes the value locked behind missing consent.
The addressable base per channel, the value you can actually touch, and what growing consent is worth.
Who it's for
Any brand that suspects it cannot actually reach much of its base, or wants to quantify the return on a consent-growth push before funding it. Runs day one.
The engagement
What you get
- Reachability and consent model per channel
- Addressable-value view and consent-growth opportunity sizing
- Reachability attributes written to Braze
What Fuse does
- Map the consent flags and contact tokens available per channel
- Build the reachability model and the addressable-value view per channel
- Size the value locked behind missing or withdrawn consent
- Write reachability attributes into Braze and document the definitions
What we need from you
Data & access
- Consent flags per channel
- Contact tokens (email, MSISDN, push) per customer
Your responsibilities
- Provide consent flags and contact tokens (email, MSISDN, push) per customer
- Confirm the consent model and channel definitions with compliance
- Provide Braze workspace access and an agreed attribute namespace
Outcomes and proof
- A clear view of the addressable base and touchable value per channel
- A sized business case for a consent-growth programme
- Every downstream model scoped to the base it can actually act on
Assumptions
- Consent state is recorded and can be tied to the customer record
- Channel identifiers are stored and reasonably clean
- Consent capture and compliance policy are owned by the client
Out of scope
- Building consent-capture forms or preference centres
- Legal or compliance sign-off on the consent model
- Deliverability remediation such as sender reputation or domain setup