Last Updated on November 18, 2026 by NowG Editorial Team
Start with a disputed £20 bonus
A retention manager sees two grants in the CRM, the cashier sees one in a player's balance, and support has two “campaign won” receipts. Which figure should finance book? Start with the system responsible for creating a grant and the corresponding ledger posting. Ask the CRM for the request and decision evidence. Check what the back office is actually querying. Three views can all tell the truth about different stages of one transaction.
This distinction matters during procurement. A vendor can put a PAM, CRM and wallet in one interface. You still need to know which service owns the decision, where it persists the result and which ID comes back when something goes wrong. Our casino CRM software comparison is a place to build the shortlist. Keep the responsibility matrix below attached to each demo. For definitions of the operator workflows, read the iGaming CRM primer.
PAM, CRM and back-office responsibility matrix
The entries describe a common separation. A sportsbook, dedicated wallet or safer-gambling system may own specific records depending on your architecture.
| Function | Typical authority | CRM or back-office role |
|---|---|---|
| Player account | PAM | CRM reads an appropriately scoped account key |
| Legal entity and brand | PAM plus operator configuration | CRM uses the signed-off scope |
| KYC status | PAM or KYC service | Back office shows the review decision |
| Login and account access | PAM or identity provider | CRM receives relevant state updates |
| Cash balance | Wallet ledger | Support sees available and held balances |
| Deposit status | Payments and wallet | CRM reacts to an approved state |
| Bet and settlement | Gaming or sportsbook service | Analytics maps settled rounds or bets |
| Bonus eligibility | CRM and engine policy | CRM proposes a grant within permitted bounds |
| Bonus award and expiry | Bonus engine | Support sees state and reason |
| Marketing preferences | Designated preference service | Channel and product gate applies at send |
| Self-exclusion | Operator's designated protection system | Marketing blocks and reports attempted dispatch |
| Risk case | Protection system | Back office exposes restricted workflows |
| Audience segment | CRM or CDP | CRM resolves the current membership |
| Journey decision | CRM | Records version and assigned treatment |
| Delivery outcome | Channel provider | CRM stores normalized receipt |
| Manual comp | Authorized operator and bonus engine | Role-limited back office submits the request |
| Accounting close | Finance | Data teams reconcile source identifiers |
| Access and audit | Each system plus central records | Support shows only permitted evidence |
Trace the path from deposit to welcome decision
Imagine a payment moves from pending to booked. The wallet records its posting and publishes a deposit event. The CRM resolves the player within the relevant scope, then checks eligibility and preferences. If the welcome offer qualifies, it sends a request to the bonus engine with a unique business reference. The engine returns a grant or denial. The journey can then check the relevant marketing controls before a channel send. Finance uses the authoritative posting and grant records, together with its accounting policy, for close.
| Object crossing the boundary | Minimum useful handoff |
|---|---|
| Player account | Account key, tenant, brand, status, source version |
| Payment | Transaction and posting keys, amount, currency, settlement state |
| Gaming activity | Bet or round key, product, occurrence and settlement timestamps |
| Bonus grant | Request key, grant key, rule version, lifecycle state |
| Protection and preference | Scope, decision or status, effective time, current version |
Pick one end-to-end trace and write down the actual ID at each stage. A label like “bonus reference” can mean the grant, campaign, rule or posting. Ask for the table or endpoint field name and what happens to it when something is reversed. This exercise exposes a deeper problem than missing fields. People in the same meeting can believe they are reconciling the same object while counting different ones.
A demo I would deliberately interrupt
Have the provider deliver a payment event twice, then demonstrate an account restriction between grant review and dispatch. The first step should preserve one eligible award. The second should demonstrate how the latest applicable protection decision reaches every relevant channel. Ask to see the evidence after each step. If the demo report simply removes the blocked contact from the recipient count, request the decision record that explains the removal.
A stale CRM snapshot should never override current account protection. An old status can still be valuable for investigating what the CRM knew at a specific time. Keep the evidence and define a separate rule for how the current authoritative status is read.
When would I use a PAM-embedded CRM?
For one business with a small retention team, bundled software can mean fewer integration boundaries, one support contract and fewer people to involve when something breaks. I’d look at standalone CRM when multiple PAMs must feed one brand portfolio, when experiments need richer controls, or when the bundled product lacks an approved operating model for another market. Require both options to show what can be exported at contract exit. Even one vendor may run its products on separate data models.
For a discovery workshop, request capabilities for account lookup, historical transactions, settlement and reversals, grant status, preference changes, protection changes, event replay, a current-status query and audit export. A product can provide some through events or files. The job is to prove each workflow has a reliable path and a responsible owner.
Can a CRM run without a PAM?
A CRM can technically run as a messaging database. A licensed operator still needs authoritative account, financial and protection services. CRM journeys that depend on those states need a reliable integration before a live send or award. NowG guide to PAM software
Is the back office a system of record?
Sometimes an action initiated in the back office writes to the authoritative system. The screen alone tells you little about record ownership. Ask which service committed the change, where the decision is logged and whether the same field can be changed elsewhere.
What happens when operators change platforms?
When the front end changes but the PAM stays, a stable account key can survive the release even if device and session tokens change. When the new platform owns the account, you may have two keys and a migration crosswalk. Keep original wallet and grant IDs available for historical explanation. Record the conversion status for each affected record. An optimistic plan often assumes the back office displays old and new data identically. Have a support agent open a case with a pre-migration bonus and confirm which view contains the original terms.
A second edge case is a brand-level restriction arriving on one interface while another interface applies a broad default. The back office should show the approved legal entity and brand scope, and the CRM should check the same current authority. Teams may need a separate administrative flow for correcting the status. Give that process an audit record distinct from a normal journey decision. A back-office user should be able to correct one thing without accidentally editing promotional permissions or cash balances.
A handoff sheet an engineer can fill in
For each function in the matrix, add the owning service, write API or actor, permitted readers, refresh policy and last observed revision. Sample the reward and account status paths first. Ask staff to retrieve the original event, the decision object and the outcome without asking another team for an ad hoc report. Then put one missing system in the test and verify that dependent actions wait or use the approved recovery path.