PLAYER SERVICE OPERATIONS

My Work

Good afternoon

Here is what needs attention across engaged player conversations.

Wednesday, July 29

Priority work queue

Players are ordered by what needs action first.

PlayerCasino / CertificateStageLast activityNext action

Follow-up schedule

An operational agenda of promised callbacks and check-ins—not an appointment-booking calendar.

0 today0 overdue

Today’s follow-ups

Open a service case or jump into the full Crisp conversation.

Service cases

Only players who engaged and entered Player Services appear here.

PlayerPlayer club #Casino / CertificateStageCrisp statusFollow-up ownerNext follow-up

Worklists

Saved operational views of players already engaged in a Crisp conversation. This is not Event Marketing.

ACTIVE INITIATIVE

July Certificate Extension

Players who replied to the expired-certificate SMS and now need guided follow-up through their existing Crisp conversations.

↔

The boundary is intentional

Bubble and Event Marketing initiate outbound campaigns and automatic drips. Player Service Center manages only players who replied or otherwise requested help, then continues their existing Crisp conversations.

Message templates

Shared by everyone on the platform. Anyone signed in can create or edit any template, and changes are live for the whole team straight away.

Templates

Loading…

Select a template

Pick one on the left, or start a new one.

Templates are shared. Anything saved here is what the whole team sends from, so a small wording fix helps everyone at once.

Proposed system architecture

Each system keeps one clear job.

B

Bubble

Players, certificates, bookings, initial SMS campaigns and drips.

Read-only lookup for service staff
→player replies
C

Crisp

SMS, chat, Hugo AI, conversation thread and message delivery.

Existing conversation remains intact
↔API + webhooks
H

Player Service Center

Queues, assignments, stages, follow-ups, audiences and reporting.

Operational system of record

Later integration work

For Tang after the workflow is approved.

1
Crisp webhook intake

Create or update a service case when a player replies.

Later
2
Player matching

Match Crisp phone/email/session ID to Bubble player and certificate.

Later
3
Read-only Bubble API

Display approved player, certificate and booking details.

Later
4
Send through Crisp

Continue one or many existing conversations from this app.

Later
5
Permissions and audit log

Control staff access and record every service action.

Later