Appearance
Availability and current limits
Reviewed 12 October 2026. This handbook covers the core pilot: Inbox, Operator, CRM and Marketing. Your workspace permissions and configured connections determine what you can use within that scope.
| Area | What is included | What to check |
|---|---|---|
| Inbox | Connected conversations, drafts, assignment, follow-up and reviewed replies | Each channel must be connected and verified; sending needs separate permission |
| Operator | Questions, approved source reads, reply preparation and reviewed channel tools | Current access, enabled tools and available AI budget |
| People (CRM) | People, companies, players, memberships, consent and audiences | Identity links, source dates and your record permissions |
| Marketing | Campaign records, content, events, audiences and campaign-linked workflow design | Player campaign sending is not yet enabled; a workflow draft does not execute messages |
| Supporting areas | Home, Agents, Knowledge, Connections and Settings | Workspace configuration and administration rights |
Outside the initial release
Finance and the Academy ledger, Work tasks and projects, Operations and stock, procurement, and the booking calendar are deferred. Their presence in earlier materials or a development workspace does not make them available in the core release. An administrator cannot enable these areas by granting more permissions.
Connection and source limits
Player records can include retained history. Check the source date: cached information is not a fresh sync. Broad provider synchronization is outside this release; supported player-only reads depend on the configured capability.
Campaign email preparation is separate from Inbox email. Dedicated sender verification and explicitly activated staff tests do not enable player campaign dispatch. See Marketing.
Joining the pilot
A waitlist request records interest. It does not create a workspace or grant admission. A new club needs a platform-issued invitation and must be within the authorised pilot scope. Staff invitations happen separately once the workspace exists.
If your workspace looks different
Check the workspace name, team access and connection state. A feature described here may still require a configured channel or an enabled runtime. Ask your administrator about the visible unavailable state before assuming that more permissions or a retry will fix it.