Competition CRM
A CRM that knows who should not be contacted.
A general purpose CRM knows who bought. A competition CRM also needs to know what they entered, whether they hit a limit, whether they excluded themselves and what they agreed to hear about.
Beaver keeps all of that on one customer record, inside the platform that enforces it.
One record
Everything about the customer, in one place.
- Account information and account status
- Entries, with competition and ticket number
- Spending history and wallet movements
- Protection state: limits, breaks, exclusion, care flags
- Marketing consent and channel preferences
Player profile work runs hourly, so the record the campaign engine reads is current.
One player. One record.
- Entry eligibility
- Spending
- Marketing eligibility
- Operator review
Status
Built, with live components.
| Capability | Status | What that means |
|---|---|---|
| Player record, entries and spend history | Live | The account and console views. |
| Campaign sending to real audiences | Live | With care flag suppression applied. |
| Care flag and closed account suppression | Live | Protection outranks promotion. |
| Customer segmentation | Built | Audiences defined from the customer record. |
| Customer journeys | Built | Welcome, draw reminders, winners, win back. |
| Channel preferences | Built | Email, SMS, push and on site. |
| Predictive scoring, LTV or churn targeting | Not available | Research only. Not for sale. |
Live proven on the deployed platform. Built in the product with passing tests, not yet proven with live customers. Roadmap planned, not a working feature.
Why it lives in the platform
Export your list to a separate CRM and it forgets the rules.
The moment customer data leaves the platform that enforces protection, the protection state starts going stale. An exclusion recorded at 10am is not much use to a list exported at 9am.
Keeping the CRM inside Beaver means segmentation and sending read the same state checkout does.
The campaign does not outrank the account state.
