The answers you need to know.

What data do you need to start?

A feed from the systems you already run — player records, ratings and activity — through an adapter, in near-real-time. Seven reads it; it does not write back into it. Your data stays isolated to your deployment.

Who owns the player relationship?

You do. Every interaction compounds into a profile that belongs to the operator — tastes, triggers, history, sentiment. When a host leaves, the relationship stays on your side.

What happens when Seven gets it wrong?

It stops. Anything outside the guardrails — a request Seven has no rule for, a threshold crossed, a conversation turning — escalates to the person you named, with the full thread.

How do you prove it worked?

A matched control group, carved at enrollment, that Seven never touches. Incremental trips, play time, actual win, dining and hotel uplift, all measured against that holdout. If the holdout does not show the gap, we do not claim the credit.

Which channels does Seven use?

SMS and in-app chat today. Where both channels are in play, Seven carries the context across them, so the conversation continues where it left off rather than starting over. In any language the player writes in.