+22%
Long-tail VIP retention
vs. cohort treatment
Solutions · VIP management
Your VIP team handles 30 players. Canon handles the next 3,000.
Most operators have a long tail of high-value players that don't quite qualify for personal management — and get cohort treatment instead. Canon gives them per-player decisions without per-player headcount.
VIP coverage · live
Where the long-tail VIP gap closes.
Tier 1 · Human-managed30 named VIPs
A
M
T
S
K
+25
Long tail · Canon-managed2,987+ players
Avg lifetime
£412
Decisions / week
21K
RG escalations
−18%
Per-player decisions, no extra headcount
Today
The VIP gap is structural.
Manageable VIPs only
Your team can manage 30–50 named VIPs. Players ranked 50–3000 are 'segment 2' — they get the cohort treatment.
Same offers, different inboxes
Sub-VIPs get the same 'high-value player' bonus the actual VIPs decline. The bonus isn't sized to them.
Risk concentrated in long-tail
Long-tail VIPs are where bonus abuse, RG escalations, and churn cluster — exactly the players cohort treatment misses.
With Canon
Per-player VIP treatment, applied to your long tail.
Per-player offers
Each long-tail VIP gets a decision shaped by their elasticity, lifecycle, and risk — not the cohort average.
VIP-aware policies
Pin policies for specific players, exclude others, set spend caps and frequency by VIP tier.
RG-aware
Long-tail VIPs are where RG risk concentrates. Canon flags loss-chasing, escalation, and session-length issues to your team.
Hand-off to humans
When a player crosses a threshold (revenue, risk, intent signal), Canon escalates to a named VIP manager rather than handling autonomously.
Outcomes
What the long tail looks like with Canon.
3,000+
Players given per-player treatment
without adding VIP headcount
−18%
RG escalations missed
vs. cohort baseline
“We always knew the long-tail VIPs were our biggest leak. Canon was the first thing that gave us per-player treatment without hiring a second VIP team.”
See per-player VIP on a slice of your tail.
A 60-day pilot on the 1,000 players your VIP team can't reach. Holdout-measured.