Work reached through the number people already trust.
An operator-branded route to verified employers, where the subscriber decides whether to take part, what their profile says, and who may see it.
Demonstration availableLevel 2 of 5. Bought by Operator foundation, or Digital Services. 5 subscriber states render on sample data; 9 of the states this proposition needs do not exist yet. No employer, vacancy or placement here is real.
Open what exists todaySkilled work of the kind this service would help people reach. These technicians are not HeuriTel placements, no employer here is real, and nobody has been matched to anything.
Nine steps, and how few of them are built.
Three steps render. Six do not, and they include every step that protects the applicant — verification, the disclosure gate, and the confirmation that a placement actually happened.
- Opt inThe subscriber chooses to take part, in their own language.Demonstrated
- Build a profileBy voice, with the skills produced shown for correction.Demonstrated
- Set sharingThe subscriber decides whether verified employers may see it.Demonstrated
- Verify the employerBefore any opportunity from them is shown.Required for pilot
- Match explainablyWith the reason stated in terms the applicant can contest.Required for pilot
- Approve the disclosureThe applicant approves this employer seeing this profile.Required for pilot
- ApplyAnd see that the application was received.Required for pilot
- Confirm the placementConfirmed by both sides, or not counted.Required for pilot
- Withdraw or deleteAt any point, with confirmation of what was removed.Required for pilot
- Demonstrated
- A screen renders this today, on sample data.
- Intended
- The journey describes it, but no screen renders it yet.
- Required for pilot
- Neither shown nor described. It has to exist before a pilot.
Nothing here verifies an employer.
The demonstration shows an opportunity labelled as coming from a verified employer. That label is sample data. No verification source is contacted, no vacancy is real, and no posting is checked against anything.
- Employer verificationWho vouches for an employer, on what evidence, and who accepts that decision.Required for pilot
- Unsuitable or discriminatory postingsUnlawful terms, discriminatory criteria, or any fee demanded of an applicant. These have to be refused before display, not reported afterwards.Required for pilot
- Expired or filled vacanciesWithdrawn before somebody applies to something that no longer exists.Required for pilot
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.
10 steps: 4 public now, 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.
- 01 · What you can buyPublic nowAn operator-branded employment service connecting subscribers to verified employers, with consent the subscriber controls.All ten offers
- 02 · A working demonstrationPublic nowThe offer's journey on sample data.Open the demonstration
- 03 · The sample, as a workbookPublic now3 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
- 04 · Validation, on the samplePublic nowcandidates, opportunities and applications as three sheets: every candidate carries a consent state; every opportunity names a verified employer and its requirements; an application names a candidate and an opportunity and follows the lifecycle; no candidate fee anywhere. 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/jobs-matching-lifecycle/review - 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
- 06 · Decision and approvalEntitled workspaceA second person decides the recommendation; the maker cannot. Approval applies to a simulated recommendation.The approvals queue
- 07 · EvidenceEntitled workspaceexplainable match per application; consent and disclosure trace; placement and outcome statement; 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
- 08 · A controlled pilotPilot request availableThe request form is available here; the pilot is scoped in writing before anything runs on your systems: a consent and deletion policy accepted by the operator; an employer verification source; a documented bias-monitoring method. No pilot has been requested or agreed, and none is demonstrated.Request a controlled pilot
- 09 · Execution against your sandboxRequires an authorised sandboxThe dry-run plan names every connector call an approved decision would make across subscriber identity, consent store, SMS/USSD gateways, notification; nothing is called and no receipt exists, because no authorised sandbox is registered.
- 10 · Live operationNot implementedUnder a separate production authorisation, with outcomes reconciled against your own records: placements confirmed by the employer; consent states against the consent store. 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.
- Available after sign-in
- 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.
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
- HeuriTel Jobs
- Buyer
- Operator foundation, or Digital Services
- Problem
- Operators hold reach and trusted identity in markets with severe employment-matching failure; social-impact commitments are hard to evidence; job seekers face fee-charging intermediaries and opaque data sharing.
- Outcome a pilot would count
- Applications submitted, and placements confirmed.
- 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, 4 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 jobs-matching-lifecycle-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
- Candidates (candidate_ref, consented, consent_on, location, skills, availability); Opportunities (opportunity_id, employer, employer_verified, location, required_skills, start_within, places); Applications (application_id, candidate_ref, opportunity_id, state, disclosure_approved, updated_on). candidates, opportunities and applications as three sheets: every candidate carries a consent state; every opportunity names a verified employer and its requirements; an application names a candidate and an opportunity and follows the lifecycle; no candidate fee anywhere. 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 consent-and-matching v1, on the public sample: 6 measures with their basis, 3 sections and the exceptions it could not settle, each with an owner, and a decision against the explicit no-action alternative. The figures are the sample's and are on the workbench and in the workbook, not on this page. 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
- explainable match per application; consent and disclosure trace; placement and outcome statement; 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 consent and deletion policy accepted by the operator; an employer verification source; a documented bias-monitoring method. None is evidenced; no pilot is requested or agreed.
- Live requirements
- Connected under a separate authorisation: subscriber identity, consent store, SMS/USSD gateways, notification — none connected; reconciled before any outcome is claimed: placements confirmed by the employer; consent states against the consent store. Not built.
Beneath the offer: Journey Activation, Experimentation and Value, Partner and Delivery Operations, AI and Governance, Telecom AI Team-as-a-Service, Telecom AI Martech and Campaign Studio, Jobs & Social Impact.
The states, the products, the parties, the pilot and the detail beneath.
Every subscriber state — five render, nine do not exist
Five render. Nine do not exist.
5 render on a route you can open. 2 are shown as steps in the journey with nothing behind them. 9 appear in neither, and most of them are the protections rather than the features.
- EligibleDemonstratedThe subscriber sees that they qualify to take part, as a completed step.Open this screen
- Consent givenDemonstratedTaking part is shown as an explicit step the subscriber has completed, not an assumption.Open this screen
- Opportunity shownDemonstratedOne opportunity with its employer, pay range, distance and why it matches.Open this screen
- Profile created by voiceDemonstratedRecording in the subscriber's own language, with the skills it produced listed for correction.Open this screen
- Profile sharing controlDemonstratedA control the subscriber sets, with the two states named: shared with verified employers, or not shared.Open this screen
- Profile completedIntendedThe journey shows this as the next step. No screen completes it.
- Matches listedIntendedThe journey shows a fourth step for matches. One opportunity is displayed; a list of matches is not.
- Applicant approves disclosureRequired for pilotNo profile should reach an employer before the applicant approves that specific disclosure. The gate does not exist.
- Employer verifiedRequired for pilotAn opportunity is labelled as coming from a verified employer. Nothing verifies one; the label is sample data.
- Application submittedRequired for pilotApplying to an opportunity, and the applicant seeing that it was received.
- Placement confirmedRequired for pilotAn outcome confirmed by both sides, which is the only thing that makes an employment claim measurable.
- Consent withdrawn and profile deletedRequired for pilotWithdrawing and having the profile deleted, with confirmation of what was removed and from where.
- Unsuitable or discriminatory opportunity refusedRequired for pilotAn opportunity that should not be shown at all — unlawful terms, discriminatory criteria, a fee demanded of the applicant.
- Expired or stale opportunityRequired for pilotA vacancy that has been filled or has lapsed, withdrawn before someone applies to it.
- Bias monitoredRequired for pilotMeasuring who is matched and who is not, by the attributes that matter, on a stated method.
- Safeguarding escalationRequired for pilotA route for a report of exploitation or harm, reaching a person with authority to act.
The operator screens are not in this list. /operator/jobs, /employers, /matches and /placements are registered routes. Compared segment by segment, 146 of their 147 text segments are identical and only the title differs: one shell with four headings, not four working screens.
Applications and placements, not activity.
No figures are given because none exist. Profiles created and matches shown are activity; counting activity as impact is the failure this proposition most has to avoid.
- Applications submittedApplicants who applied, having approved the disclosure
- Placements confirmedConfirmed by employer and applicant, or not counted
- Time to placementFrom opt-in to a confirmed placement
- Opportunities refusedUnsuitable or unlawful postings stopped before display
- Consent withdrawnWithdrawals and completed deletions
- Match acceptanceMatches an applicant chose to act on
- Exclusion and bias signalsWho is matched and who is not, on a stated method
- Safeguarding reportsReports raised, and time to a human response
Six governed products, and what each one does here
Six governed products, and what each one does here.
HeuriTel Jobs is a proposition. It takes no product id, grants no entitlement, and adds nothing to the 16 governed products. Jobs and Social Impact remains a supporting catalogue stream; that classification is about entitlement, and it is not a reason for this proposition to be hard to find.
- Journey ActivationCarries opt-in, profile, consent and withdrawal as one governed journey.
- Experimentation and ValueMeasures employment outcomes against a stated method, rather than counting activity.
- Partner and Delivery OperationsOnboards and verifies employers, and holds what each is accountable for.
- AI and GovernanceApplies the matching and refusal policy, and records why a match was shown.
- Telecom AI Team-as-a-ServiceDelivers the capability with the operator and hands it over.
- Telecom AI Martech and Campaign StudioReaches subscribers in their own languages, including on SMS and USSD.
Four parties, and an employer is one of them
Twelve things that would have to be true before a pilot
Twelve things that would have to be true.
None of these is done. They are the gate between Concept defined and Controlled pilot ready, and most of them protect the applicant rather than deliver a feature.
- An operator-approved lawful basis and consent record
- An employer verification source, and who accepts its decisions
- The applicant-approves-disclosure gate, built and tested
- A documented matching method an applicant can contest
- A documented bias-monitoring method, with who reviews it
- Refusal rules for unlawful, discriminatory or fee-charging postings
- A safeguarding protocol with a named escalation route
- Deletion and withdrawal, exercised end to end
- Accessible delivery on the channels the audience actually has
- A defined operator liability boundary, agreed with Legal
- A bounded pilot cohort in one market
- Agreed success, stop and rollback criteria, including a harm trigger
Not started. A proposition that touches employment does not reach a pilot on engineering readiness alone: the lawful basis, the safeguarding route and the liability boundary are decisions an operator takes with its own Legal function.
The detail underneath
If you need the detail underneath.
The matching method — a ranked comparison, not a generative model
Matching a person to work is a classification and ranking problem with an explainability obligation: an applicant should be able to contest the reason they were or were not matched. A generative model makes that harder to satisfy, not easier.
No matching runs today. When it does, the method and the reason shown with a match are part of what an operator approves.
The record kept, and the subscriber’s right to remove it
Nothing is recorded today: the screens hold their state in the browser and no profile is stored. A pilot changes that, and the deletion path has to be built and exercised before it does.
The relationship to a similar employment model
HeuriTel Jobs is understood as an operator-labelled, internationally applicable telecom version of a similar employment model. That is recorded product intent, supplied by the product owner on 9 September 2026.
It describes where the design came from. The state of this proposition is the one given above: concept defined.
The catalogue definitions beneath this proposition
The detailed definitions sit under the governed products that compose it, in the streams for jobs and social impact, and for digital commerce and the partner ecosystem.
Jobs and social impactDigital commerce and partner ecosystem