Status match and challenge

How do we run a status match or challenge so the member's proof of status elsewhere is checked, eligibility decided under the program terms, and the tier updated?

Treat the match as an application with proof and a decision. Callvu takes the member's request (the competing program, the tier claimed, the proof they can supply), prefills the member's own account and history (the current tier, prior matches, the activity in the window), chases the proof through a link (a current statement or a profile screenshot showing the name, the tier and the validity date), reads and checks it against the program's match terms (the eligible programs and tiers, the mapping table, the one-match-per-period rule, the challenge's activity requirement and window), routes a proof the rules cannot read or a member outside the terms to the loyalty desk in the Decision Desk, grants the matched tier or the challenge with its target and end date, and writes it to the loyalty system, the system of record, with the member told the terms.

In scopeSimpleCallvu moves: chase and verify, decide, write back

Talk to an expert Try it in the sandbox

Last updated November 7, 2026.

The problem today

The screenshot showed a tier the competing program had not offered for two years, and the match was granted anyway.

Today, without Callvu

Status matches win high-value members from competitors, and they are abused: edited screenshots, expired tiers, members who match every year, programs the terms never included. An agent eyeballs the proof and grants the tier; the challenge's activity target is tracked in nobody's system; the member keeps the tier after failing it. The program's cost of acquisition rises with no record of what was granted and why.

The match terms are specific: which programs and tiers qualify, how they map, how often a member may match, what proof is required, and for a challenge what activity within what window keeps the tier. The proof is a document to read and check; the decision is a rule with exceptions; the grant has an end date and a target the loyalty system must track.

A match granted on checked proof with its end date on the record is an acquisition the program can measure.

How it runs

From the requestto the system of record.

A member (or a prospect who joins to apply) requests a status match or challenge on the website, in the app or by phone. Callvu opens the application.

Member: Supplies the proof of the competing status through a link and accepts the challenge terms.
Loyalty desk: Decides unreadable proof and members outside the terms in the Decision Desk.
Callvu: Prefills, chases, reads and checks, decides by rule, routes, grants and writes.

Prefill and classify
The member's account (the current tier, the join date, prior matches and their dates, the activity in the recent window) is prefilled from the loyalty system; the request names the competing program and the tier, and the terms classify it: eligible program and tier under the mapping table, the member inside the one-match-per-period rule, a match or a challenge path, and the proof required.
Chase and verify the proof
The proof (a current account statement or a profile page showing the member's name, the tier, and the validity or expiry date, dated within the terms' recency) is requested through a link and read on arrival; it is checked for the name matching the member, the tier being one the competing program currently issues, the date within recency, and signs of alteration; what fails is requested again with the specifics.
Decide
A request inside the terms with proof that passes is granted by rule (the matched tier for the terms' period, or the challenge with its activity target and window); a proof the rules cannot read, a program or tier outside the table, a member outside the period rule, or a suspected alteration goes to the loyalty desk in the Decision Desk with the proof and only the allowed outcomes (grant, grant a lower tier with the reason, offer the challenge instead, or decline with the reason).
Grant and write back
The tier or the challenge with its target, its window and its end date is written to the loyalty system, the system of record, with the proof reference and the decision, the member is told the terms (what keeps the tier, when it ends), the challenge's progress is tracked against the activity feed, and the outcome at the end of the window is applied by rule.

Where it ends: The match was granted on proof read and checked against the terms, with the exceptions decided by a person, and the loyalty system holds the grant with its end date and the challenge's target. The Decision Trace shows the classification, the proof checks and any decision; the Audit Trace shows the request, the proof and the grant with time.

Runtime enforcement

What is enforcedwhile the work runs.

The regulations preloaded in Callvu Studio and the bank's own policies, applied as steps that run, not lines in a binder. A step that breaks a rule does not run, so a completed run was compliant.

Regulations

Program terms: The status match and challenge terms, published as part of the program's terms, set the eligible competing programs and tiers and their mapping, the proof required and its recency, the frequency limit (one match in a period, commonly a number of years), the matched tier's validity period, the challenge's activity requirement and window, and the program's discretion; the decision applies them as published and the record evidences it.
Consumer protection on promotions (the FTC Act Section 5 and the state unfair practices acts; the advertising substantiation rules): An advertised status match is an offer the program must honor on its stated terms, with the material conditions (the proof, the period, the challenge target) disclosed clearly; the terms shown at application and in the grant notice are the evidence.
Privacy and the competing program's data (the state privacy laws and GDPR where they apply): The proof contains the member's data from another company; it is collected from the member with the privacy notice, used only for the match decision, retained for the terms' period and the program's audit, and never shared back.

Company policies

The proof is read and checked against the mapping table, the recency and the alteration rules; nobody eyeballs a screenshot.
The frequency rule and the eligible programs are enforced by the classification.
A challenge's target and end date are on the record and tracked against the activity feed.
The loyalty system is the system of record for the grant and the challenge.

Controls

Account prefill with prior match history.
Term classification with the mapping table.
Proof chase with reading, recency and alteration checks.
Rule-based grant and Decision Desk for exceptions.
Loyalty system write with end date and target.
Challenge tracking and outcome by rule.

Clocks and deadlines

Proof recency: The terms' recency for the competing program's statement, checked on arrival.
Matched tier validity: The terms' period from the grant, on the record.
Challenge window: The terms' window from the grant, with the target tracked and the outcome applied at the end.

Documents and checks

The request and the classification
The proof as received and checked
The decision
The grant with its terms and the loyalty system record
The challenge's tracking and outcome

In the Decision Trace

The classification and the mapping.
The proof checks.
Any decision and the person.

In the Audit Trace

The request with time.
The proof with time.
The grant, the tracking and the outcome.

The handoff

Between the front doorand the back office.

The front door

The website, the app or a call; the member uploads proof through a link.

The back office

The loyalty desk decides only unreadable proof and members outside the terms; the grant and the tracking run from the record.

The Decision Desk

Unreadable proof, a program or tier outside the table, a member outside the frequency rule or a suspected alteration goes to the loyalty desk in the Decision Desk with the proof and only grant, grant a lower tier with reason, offer the challenge, or decline with reason.

Proof

In scope.Proof at scale, not one process at a time.

The kind of process Callvu runs in production for customers in this industry. Ask for a reference on this exact process. The results below are the industry's published proof; each claim code links to its record on agents.callvu.com.

More than 1,000 processes are live across Callvu customers.

Across Callvu customers

Callvu requests missing documents from the right party on a clock, reads them on arrival (OCR) and checks each against what the case needs.

HND-04 · Self-asserted · verified 2026-11-02

When a person must decide, the case goes to the right reviewer in the Decision Desk, with only the allowed choices, and the run waits for the decision.

CAP-07 · Self-asserted · verified 2026-11-02

A process can run a timer that tracks a regulatory clock, such as a response or disclosure deadline, and act when it runs out.

CAP-13 · Self-asserted · verified 2026-11-02

Questions

What buyers ask next,answered plainly.

What proof is accepted?

What the terms require: a current statement or profile page from the competing program showing the member's name, the tier and the validity date, within the terms' recency, read and checked for alteration.

How often can a member match?

As the terms allow, commonly once in a period of years; the classification checks the member's prior matches before the proof is requested.

What happens at the end of a challenge?

The activity is tracked against the target in the loyalty system, and the outcome (keep the tier or revert) is applied by rule at the end of the window, with the member told.

Related processes

Loyalty redemption Loyalty points adjustment Duplicate loyalty account merge Loyalty account takeover and fraud review Try it in the sandbox All travel and ecommerce processes

Bring this process, or the one that costs you most.

We build it against your policies and your systems, train your team and stay with you through launch. You are live in weeks.