Giselle Cloud
The engagement tool you are shopping around for, already built: CLOE journeys, IN-GRID Loyalty, the Jackpot Server, tournaments, wheels, bonusing, messaging and an AI analyst, on the platform you run today. One stream of events in, rewards out as your own bonuses, and no replatform.
Launching a brand? Dench Core runs the platform and the suite as one →
01 · The back office
Five screens from the product, with demo data, and the controls work. Open a segment, adjust a player's loyalty, map your IDs, start a journey from a recipe, ask the analyst. On a call we open the real one, on your brand.
Every segment on the brand, how often it recalculates, and where it is used.
| ID | Name | Last Update Date | Update Type | Use In Campaigns | Participants | Status | |
|---|---|---|---|---|---|---|---|
| 5121 | Reactivated depositors | 31/10/2026 09:41 | Real Time | iWin-back reload, Weekend wheel invite | 1,842 | ACTIVE | |
| 5118 | High value, casino | 31/10/2026 09:00 | Hourly | iVIP tournament series | 612 | ACTIVE | |
| 5114 | Registered, no deposit | 31/10/2026 09:41 | Real Time | iWelcome journey | 3,407 | ACTIVE | |
| 5109 | Sport first bet, 7 days | 31/10/2026 03:00 | Daily | iNot used yet | 958 | ACTIVE | |
| 5102 | Dormant, 30 to 60 days | 31/10/2026 03:00 | Daily | iWin-back reload | 2,264 | ACTIVE | |
| 5097 | Bonus-only players, watchlist | 29/10/2026 12:00 | Hourly | iNot used yet | 141 | INACTIVE | |
| No segments match your search | |||||||
Every programme running on the brand, and who is in it.
| ID | Name | Type | Start Date | End Date | Last Reset Date | Reset Period | Level Count | Status |
|---|---|---|---|---|---|---|---|---|
| 14 | Demo Casino Club | Tier | 01/01/2026 | – | 01/10/2026 | Quarterly | 7 | ACTIVE |
| 17 | Sportsbook Ladder | Tier | 01/03/2026 | – | 01/10/2026 | Monthly | 5 | ACTIVE |
| 21 | Autumn Map | Map | 01/10/2026 | 30/11/2026 | – | Lifetime | 12 | ACTIVE |
| Customer ID | Username | Level | Level Reach Date | Total Points | Available | |
|---|---|---|---|---|---|---|
| 100207 | demo.player.207 | Gold | 12/10/2026 | 18,420 | 2,150 | |
| 100233 | demo.player.233 | Platinum | 02/09/2026 | 41,300 | 6,800 | |
| 100118 | demo.player.118 | Silver | 27/10/2026 | 9,640 | 1,210 | |
| 100052 | demo.player.052 | Bronze | 19/10/2026 | 3,880 | 640 | |
| 100150 | demo.player.150 | Iron | 30/10/2026 | 1,120 | 300 |
Every manual change lands on Loyalty Change History, with the back-office user who made it.
Manage external data mappings and integrations
| Id | Name | External Id | |
|---|---|---|---|
| 41 | Demo Fortune Ways | g-104221 | |
| 42 | Demo Gold Mine | g-104230 | |
| 43 | Demo Book of Ages | g-104318 | |
| 44 | Demo Sugar Stack | g-104402 | |
| 45 | Demo Roulette Live | g-200017 | |
| 46 | Demo Crash X | g-310006 | |
| 47 | Slots | cat_slots | |
| 48 | Live Casino | cat_live | |
| 49 | Table Games | cat_table | |
| 50 | Crash Games | cat_crash | |
| 51 | Jackpot Games | cat_jackpot | |
| 52 | Pragmatic Play | pragmatic | |
| 53 | Play’n GO | playngo | |
| 54 | Evolution | evolution | |
| 55 | Hacksaw Gaming | hacksaw | |
| 56 | NetEnt | netent | |
| 57 | Active | ACTIVE | |
| 58 | Suspended | SUSPENDED | |
| 59 | Self-excluded | SELF_EXCLUDED | |
| 60 | Closed | CLOSED | |
| 61 | Not verified | KYC_NONE | |
| 62 | Pending | KYC_PENDING | |
| 63 | Verified | KYC_OK | |
| 64 | Rejected | KYC_REJECTED | |
| 65 | Match result | mkt_1x2 | |
| 66 | Over/Under | mkt_ou | |
| 67 | Both teams to score | mkt_btts | |
| 68 | Handicap | mkt_ah | |
| 69 | Single | SINGLE | |
| 70 | Multiple | MULTI | |
| 71 | System | SYSTEM | |
| 72 | Demo Sportsbook | sb_demo | |
| 73 | Nuvei | nuvei | |
| 74 | Skrill | skrill | |
| 75 | Trust Payments | trustpayments | |
| 76 | Interac | interac | |
| 77 | Visa | card_visa | |
| 78 | Mastercard | card_mc | |
| 79 | Skrill Wallet | ewallet_skrill | |
| 80 | Apple Pay | applepay | |
| 81 | Bank Transfer | bank_sepa | |
| 82 | Interac e-Transfer | interac_etransfer | |
| 83 | Football | sport_1 | |
| 84 | Tennis | sport_5 | |
| 85 | Basketball | sport_2 | |
| 86 | Ice Hockey | sport_4 | |
| 87 | Demo Premier Division | lg_9001 | |
| 88 | Demo Cup | lg_9002 | |
| 89 | Demo Basketball League | lg_9100 | |
| 90 | VIP | FLAG_VIP | |
| 91 | Manual withdrawal review | FLAG_MANUAL_WD | |
| 92 | Bonus excluded | FLAG_NO_BONUS | |
| 93 | Test account | FLAG_TEST |
Ready-made flows for the problems you actually have.
A week of nudges for players who signed up and never deposited. It ends the moment they do.
A reward for each verification step, then an invitation to refer a friend once the account is verified.
A welcome, a tour of the site, one feature worth knowing, then cashback at the end of the week.
Three escalating nudges toward a second deposit, each one checking first whether it already happened.
Active in casino, absent from the sportsbook: a free bet to try it. The same flow runs the other way.
Regular depositors who have gone quiet for a fortnight get a reason to come back before they lapse.
Five deposits over thirty days, a smaller match each time and a wider window to claim it.
Bonus money on the day, an email that names it, and an SMS reminder the day after.
A thank-you after a big win, then seven days to see whether the player keeps playing.
One week without a login: a message, spins if they are still away, and an exit the moment they return.
A month of silence: a reload offer by email, three days to deposit, an SMS if they do not.
Every recipe here is a preset. Turn off Hide presets to see them.
What CRM contributed, who it reached, and how fresh the data behind it is.
| Journey | Active | Completed | Failed | Paused | Completion |
|---|---|---|---|---|---|
| Welcome journey | 2,914 | 1,206 | 12 | 0 | 29% |
| Win-back reload | 1,206 | 388 | 4 | 0 | 24% |
| Big-win follow-up | 388 | 96 | 0 | 388 | 20% |
Newly registered cohort: negative margin for 26 consecutive days
Win-back reload: 41% of entrants stall at the deposit wait
Push consent missing for 1,120 active players
Gold tier players who joined a tournament deposit twice as often
Ask about segments, CLOE flows, indicators or trends, or start from one of these.
| Registration Month | Players | 1 day Retention | 7 days Retention | 28 days Retention | 90 days Retention |
|---|
Segments on how your players actually play. A segment is a rule over the behavioural indicators Giselle computes from your platform’s events, recalculated in real time, hourly or daily. The list shows which journeys and campaigns use it.
Loyalty on your platform, more than one programme at a time. Tiers or a free-form map, points that reset when you choose, and every reward paid as your own bonus. Adjust a player by hand and it is on the history with your name.
Your IDs, mapped once. Games, studios, account and KYC statuses, payment methods, sports and customer flags, each paired with the ID your platform sends. Eligibility filters, tournaments, loyalty missions and bonus rules pick from these lists, in your terms.
The first journey starts from a recipe, not a blank canvas. Ready flows by lifecycle stage, from registered-no-deposit to the big-win check-in and the 30-day win-back. Use one and it becomes a draft, ready to go live on a held-back cohort.
The first screen your CRM lead opens. Incremental deposits against a holdout, players reached, the journeys in flight and what the analyst found overnight. Open the Assistant and ask it in plain words.
02 · What is in it
The AI analyst reads all nine. IN-GRID Loyalty and the Jackpot Server are also licensed on their own.
03 · Your first ninety days
Your side is one thing: a stream of events posted to one endpoint. If your platform already emits a transaction feed or a webhook, that is typically a few engineer-days, and our engineers write the mapping, not yours.
Read the docs for your platform’s API or event feed, and tell you in writing what the integration takes on your side.
Send the docs, the brands you want on it, and the bonuses you already run.
The number in writing, before you commit.
Write the mapping from your platform to ours: games, studios, statuses, payment methods, flags.
Events flowing in a sandbox, against your real schema.
Point one stream of events at one endpoint: bets, deposits, logins, registrations, consent changes.
A mapping document naming which indicators your feed can and cannot populate.
Register your bonus IDs, so a reward is your own bonus, fired by its ID: signed, idempotent, retried.
One journey live on a held-back cohort.
Pick the journey. Most pick registered-no-deposit or the big-win reload, because both fail loudly if the plumbing is wrong.
The journey in Flows, node by node, with the control group beside it.
The first treatment-against-control readout, in contribution margin.
Then the rest, switched on as you want it: loyalty, tournaments, wheels, jackpots, and widgets themed to your front end. We run the technology: hosting, releases, monitoring.
Give us your cost inputs: gaming tax, payment fees, jackpot contribution, licence cost. Your CRM team runs the journeys, segments and programmes from the back office.
What a journey earned on your costs, not what it sent.
No replatform, no migration. Your players and your wallet stay where they are, and your wallet enforces every reward the suite triggers.
04 · Standard, and ours
The CRM and gamification suite you would otherwise buy on top, as one product: journeys, loyalty, jackpots, tournaments, wheels, bonusing, messaging, segmentation and the analyst. A loyalty tier, a bonus, a jackpot contribution and a journey decision read the same player, with no nightly export in between.
Give it your gaming tax, payment fees, jackpot contribution and licence cost, and treatment and control carry their own margin, rolled up daily. A segment with positive GGR and positive NGR can still be losing money. This is the number that shows it.
Register a bonus ID and the journey fires it when the moment comes: signed, idempotent, retried. A failed reward is a state you can query, not a silence you discover. Your wallet enforces every rule, because it is your wallet.
Giselle has run since 2017 where a bonus is a wallet operation and gaming tax and payment fees sit on the same ledger. Giselle Cloud is the same suite, packaged for the platform you run.
05 · The record
06 · How it is bought
You hold the licence and run the operation: marketing, support, payments relationships, compliance. We deliver and run the technology: the platform with its CRM and gamification suite, integrations, front end, hosting, releases, support. Your provider contracts or ours.
The platform built out to your market and your specification: dedicated environment, custom front end, features against your requirements. The way the largest accounts have been delivered for ten years.
Our infrastructure end to end, run under the group’s Curaçao setup: licensing, provider contracts, payments. You bring the brand and the marketing.
The engagement suite, journeys, loyalty, jackpots, tournaments, bonusing and the analyst, on the platform you already run.
You pay for the modules you take, on the platform you already run.
Take the whole suite or the part you are missing. IN-GRID Loyalty and the Jackpot Server are licensed on their own as well. Connecting your platform is typically a few engineer-days on your side, and the mapping is ours.
07 · Asked first
Post a stream of events to one endpoint: bets, deposits, logins, registrations, consent changes. If it already emits a transaction feed or a webhook, that is typically a few engineer-days on your side, and our engineers write the mapping.
The rest is ours to carry: one API your site reads tournament, loyalty and wheel state from, rewards fired as your own bonuses by their ID, and widgets themed to your front end.
Yes. IN-GRID Loyalty and the Jackpot Server are their own modules with their own licences: take the loyalty module without the jackpot server, or the jackpot server on its own.
You buy the modules you want and keep the platform you are on.
Giselle has run inside our own licensed platform since 2017, across thirty-plus brands. Giselle Cloud is the same suite: the segments, the journeys, the bonuses, the tournaments and the loyalty are the ones those brands ran on. What is new is the connection to your platform.
The platform you run, the docs for its API or event feed, and the bonuses you run today. It comes back in writing: what your side takes, which indicators your feed populates, and the first journey we would put live.