Compliance per variant
Every claim checked against its market's claims rules; the manifest takes only what passed.
3 rows · Variant · Market · Language · Claims
Bought by Marketing and Brand director
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 available — A journey runs end to end on sample data, including its refusal and failure states. Runs today on a sample of your market; its workspace opens with Telecom AI Martech and Campaign Studio.
The result, on the sample
2 variants in the activation manifest across 2 markets; 1 required market-language pair(s) still uncovered; 2 compliance exception(s); 2836 responses worth 415200 units from 82000 sent.
Sample. Choose your market to see this page, the workbook and the review in your currency and language.
AI Campaign Creation and LocalisationYour market · units
2 variants in the activation manifest across 2 markets; 1 required market-language pair(s) still uncovered; 2 compliance exception(s); 2836 responses worth 415200 units from 82000 sent.
In the activation manifest2variants
Compliance exceptions2variants
Sent82,000recipients
Response rate3.5%
Decision Activate the 2 manifest variants; hold 1 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.
The other 2 measures the run holds
- 3.5 % — Response rateresponses over sent
- 415,200 units — Valueresponses × the brief's value per response
See the product
The workspace, screen by screen.
The 7 screens a demo walks through, captured from the built product on sample rows. Sign in to run it on your own market and your own numbers.
1 of 7 · Overview The workbench: the tiles, the run, the ladder, the last run and the next step. Captured on the built product, signed in as an analyst, on 2026-09-30. Sample rows. 
2 of 7 · Sample The result on the sample: the headline and the tiles, each with its basis. Captured on the built product, signed in as an analyst, on 2026-09-30. Sample rows. 
3 of 7 · Sample The decision the engine proposes, and what happens if nobody acts. Captured on the built product, signed in as an analyst, on 2026-09-30. Sample rows. 
4 of 7 · Sample The checks the engine refused, each with its reason and its owner. Captured on the built product, signed in as an analyst, on 2026-09-30. Sample rows. 
5 of 7 · Your data Your data: the sheets, the template to download, and the review of what comes back. Captured on the built product, signed in as an analyst, on 2026-09-30. Sample rows. 
6 of 7 · Runs Every run, as it was computed, with the version it ran on. Captured on the built product, signed in as an analyst, on 2026-09-30. Sample rows. 
7 of 7 · Decide The proposal to an approver, and what the approver sees. Captured on the built product, signed in as an analyst, on 2026-09-30. Sample rows.
Three things it decides
Each on your rows, each with its reason written.
Coverage per brief
Market-language pairs required, approved, missing.
2 rows · Brief · Required · Approved · Missing
Activation manifest
What may be activated, on the sample.
2 rows · Variant · Brief · Market · Language
What it needs from you, and how a pilot proves it
Time to campaign, and languages covered.
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 the refusal names the column.
- The data you supply
- Briefs, Claims, Variants, Reviews — your own rows, on your own subject keys, through the same review the sample passes. Bring your data — the workbook out and back, after sign-in. Download the sample workbook
The 4 sheets, column by column
- 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.
- The measure
- Counted once reconciled against your own records: responses against the campaign system; activations against the send log.
- The approval
- A second person approves; the person who loaded the data cannot. The decision is audited with its reason.
The products and the streams it draws on
Runs on Telecom AI Martech and Campaign Studio; draws on Journey Activation, AI and Governance, AI Assurance, Governance and Handover and the Campaigns & Personalisation, AI Operations & Governance streams of the catalogue. The lifecycle to live operation and the twelve-line contract are in the workbench, after sign-in.
See it on your own numbers.
Sign in with your work email; the sample is generated for your market and currency; change the values and run again. Or book a demo and we walk it with you.