Skip to content
HeuriTel
Sign in
A woman checking her phone at a market stall in bright daylight.

Produce compliant campaign content in your markets' languages, at campaign speed, with approval retained.

Multi-market, multi-language campaign production is slow and expensive, and brand and regulatory compliance is checked late.

Demonstration availableLevel 2 of 5 — A journey runs end to end on sample data, including its refusal and failure states. Bought by Marketing and Brand director. Nothing here has run against an operator system.

Open the demonstration

A woman checking her phone — where a campaign lands. The briefs, claims and variants here are the sample's; nothing was activated.

Public nowAnyone can do this from this page, without signing in, and the page keeps no record of it. This page, its sample workbook and the sample's review need no sign-in; the steps below say which need more.

The sample, computed

3 variants in the activation manifest across 2 markets; 5 required market-language pair(s) still uncovered; 2 compliance exception(s); 6026 responses worth 798000 KES from 137000 sent.

HeuriTel default synthetic sample — Kenya, in KES, Kiswahili; sample campaign-localisation-review-sample v1. Synthetic rows invented by HeuriTel, sized for Kenya in KES. Not an operator's figures; nobody here is real. Configure a market to see the same sample recomputed for it. Configure a market and this page, the workbook and the review recompute for it.

  • 3 variants — In the activation manifestapproved on the sheet, reviewed as approved, every claim permitted in the market
  • 5 pairs — Coverage gapsmarket-language pairs a brief requires with no activatable variant
  • 3 variants — Compliance exceptionswithdrawn or foreign-market claims, approvals without a review, sends without approval
  • 137,000 recipients — Sentsum over variants
  • 4.4 % — Response rateresponses over sent
  • 798,000 KES — Valueresponses × the brief's value per response

Activate the 3 manifest variants; hold 5 uncovered pair(s) until reviewed; withdraw 1 variant(s) sent without approval. If nobody acts: Variants go out as each market team sees fit, including one built on a withdrawn claim. No copy was generated. No message was sent. No campaign was activated.

From this page to live operation

10 steps: 3 public now, 1 after sign-in, 3 in an entitled workspace, 1 a request form, 1 needing an authorised sandbox, 1 not implemented.

Each step says who can take it today. A route existing is not the same as an action being available: the state beside each step is decided by the same rules that refuse a request.

  1. 01 · What you can buyPublic nowProduce compliant campaign content in your markets' languages, at campaign speed, with approval retained.All ten offers
  2. 03 · The sample, as a workbookPublic now4 data sheets, a manifest and the generated guide, dictionary, validation lists and expected outputs — downloadable without signing in, in the sample's market and currency.Download the sample workbook
  3. 04 · Validation, on the samplePublic nowbriefs, claims, variants and reviews as four sheets: every variant names a brief and a market-language pair; every claim a variant uses is a permitted source claim; a review names a variant and a decision. The public review checks a returned workbook against the sample it was issued from, answers with the result before and after, and stores nothing.POST /api/sample/campaign-localisation-review/review
  4. 05 · Acceptance and the stored simulationEntitled workspaceYour organisation's own workbook, reviewed, accepted as an immutable version with its original retained, and the engine's result stored whole — never recomputed on reopening.Open the workbench
  5. 06 · Decision and approvalEntitled workspaceA second person decides the recommendation; the maker cannot. Approval applies to a simulated recommendation.The approvals queue
  6. 07 · EvidenceEntitled workspacereview decision per variant with the claims checked; activation manifest of approved variants; response and value measurement per market; run register export. The register export, the retained original, the run history, the dry-run plan and the pilot package are downloadable from the workbench.Evidence on the workbench
  7. 08 · A controlled pilotPilot request availableThe request form is available here; the pilot is scoped in writing before anything runs on your systems: a claims register approved by Legal; brand rules for each market. No pilot has been requested or agreed, and none is demonstrated.Request a controlled pilot
  8. 09 · Execution against your sandboxRequires an authorised sandboxThe dry-run plan names every connector call an approved decision would make across campaign management, notification channels, brand asset store; nothing is called and no receipt exists, because no authorised sandbox is registered.
  9. 10 · Live operationNot implementedUnder a separate production authorisation, with outcomes reconciled against your own records: responses against the campaign system; activations against the send log. Not built; no connector exists.
Public now
Anyone can do this from this page, without signing in, and the page keeps no record of it.
A verified sign-in sees it on sample data; it reads nothing private and stores nothing.
Entitled workspace
A member of an organisation that holds the owning product and has the journey configured; the role decides which actions.
Pilot request available
The request form is available. A pilot is scoped in writing afterwards; the pilot itself is not demonstrated.
Requires an authorised sandbox
Needs an authorised operator sandbox, which no organisation has registered. The permission that would reach one is refused to everyone.
Requires production authorisation
Needs a production authorisation from the operator and a connected operator system. No such authorisation exists.
Not implemented
No code performs this.
On demand

The contract, the data, the pilot and the products beneath.

Four things a technical or commercial evaluation asks for, each in the same terms as the other nine offers.

The offer in twelve lines
The offer, in twelve lines

The offer in the same terms as the other nine.

Read from the offer contract and the engine's own run; the same twelve fields on every offer page.

Commercial offer
AI Campaign Creation and Localisation
Buyer
Marketing and Brand director
Problem
Multi-market, multi-language campaign production is slow and expensive, and brand and regulatory compliance is checked late.
Outcome a pilot would count
Time to campaign, and languages covered.
Current availability
Demonstration available — level 2 of 5: A journey runs end to end on sample data, including its refusal and failure states. Of 10 steps, 3 are public now, 3 need an entitled workspace, 2 need what does not exist yet. Public now Entitled workspace Not implemented
Public sample
HeuriTel default synthetic sample: Kenya, in KES and Kiswahili (sample campaign-localisation-review-sample v1). Download the workbook. Synthetic rows invented by HeuriTel, sized for Kenya in KES. Not an operator's figures; nobody here is real. Configure a market to see the same sample recomputed for it.
Data requirements
Briefs (brief_id, name, markets, languages, value_per_response); Claims (claim_id, text, markets, permitted); Variants (variant_id, brief_id, market, language, claims_used, review, sent, responses); Reviews (variant_id, reviewer_role, decision, reason, reviewed_on). briefs, claims, variants and reviews as four sheets: every variant names a brief and a market-language pair; every claim a variant uses is a permitted source claim; a review names a variant and a decision. A subject column holds your own pseudonymous reference; a phone number, IMSI, IMEI or account number in it is refused and never echoed back.
Executable result
Engine review-and-activation v1, on the public sample: 3 variants in the activation manifest across 2 markets; 5 required market-language pair(s) still uncovered; 2 compliance exception(s); 6026 responses worth 798000 KES from 137000 sent. 6 measures with their basis, 4 sections, 5 exceptions with owners. Recommendation: Activate the 3 manifest variants; hold 5 uncovered pair(s) until reviewed; withdraw 1 variant(s) sent without approval. If nobody acts: Variants go out as each market team sees fit, including one built on a withdrawn claim. Simulated; nothing ran against an operator system.
Approval model
Maker-checker: the person who accepted the data or requested the run cannot decide its recommendation; a client administrator does. Approval applies to a simulated recommendation.
Evidence
review decision per variant with the claims checked; activation manifest of approved variants; response and value measurement per market; run register export; the retained original with its inspection verdict; the run history; the per-record dry-run plan; the pilot package.
Pilot requirements
a claims register approved by Legal; brand rules for each market. None is evidenced; no pilot is requested or agreed.
Live requirements
Connected under a separate authorisation: campaign management, notification channels, brand asset store — none connected; reconciled before any outcome is claimed: responses against the campaign system; activations against the send log. Not built.

Beneath the offer: Telecom AI Martech and Campaign Studio, Journey Activation, AI and Governance, AI Assurance, Governance and Handover, Campaigns & Personalisation.

Your data — 4 sheets, checked before anything is read
Your data

4 sheets, checked before anything is read from them.

briefs, claims, variants and reviews as four sheets: every variant names a brief and a market-language pair; every claim a variant uses is a permitted source claim; a review names a variant and a decision. A subject column holds your own pseudonymous reference; a phone number, IMSI, IMEI or account number in it is refused and never echoed back.

  • Briefseach campaign brief: the markets and languages it must cover and the value of one response. Columns: brief_id, name, markets, languages, value_per_response.
  • Claimsthe sentences Legal permitted, and where. Columns: claim_id, text, markets, permitted.
  • Variantsone rendering per market and language: the claims it uses, the review, and what it measured once sent. Columns: variant_id, brief_id, market, language, claims_used, review, sent, responses.
  • Reviewswho reviewed each variant and why it was decided. Columns: variant_id, reviewer_role, decision, reason, reviewed_on.
A pilot’s measure and prerequisites — 5 things that would have to be true
What a pilot would count, and needs

Time to campaign, and languages covered.

Nothing is counted until it is reconciled against your own records: responses against the campaign system; activations against the send log.

  • a claims register approved by Legal
  • brand rules for each market
  • Connected under authorisation: campaign management. Not connected today.
  • Connected under authorisation: notification channels. Not connected today.
  • Connected under authorisation: brand asset store. Not connected today.
Built on 4 governed products and 2 catalogue streams
What it draws on

4 governed products and 2 catalogue streams.

The offer is a commercial view onto the same platform every other offer runs on. Its workbench opens with Telecom AI Martech and Campaign Studio.