Keep the conversation inside your game.

Add text communication to your player experience. Use supported chat contexts to help players exchange messages while they connect and play.
Channel types
Message delivery
Permissions and controls
Contextual draft · Release status, supported versions, and limits await owner review.

Plan the integration

Channel types

Choose the game context for each channel and define eligible participants.

Message delivery

Plan message rendering, ordering expectations, retries, and the UI for an interrupted connection.

Permissions and controls

Define membership, reporting, and abuse handling responsibilities for your game and its operators.
ILLUSTRATIVE GAME WORKFLOW

provide text chat for an authorized group.

This example describes a game-team workflow. Service connections and game rules require explicit integration; it does not imply automatic bindings.

Scope and responsibilities

Text communication needs membership rules and abuse handling. Persistence, offline delivery, filtering, and retention are separate implementation decisions.

Related services

Explore complementary services for your game, with integration details for each building block.
SERVICE 1

Friends

Help players stay connected. Explore Friends
SERVICE 2

Parties

Keep the group together as they play. Explore Parties
SERVICE 3

Lobbies

Give players a shared place before the match. Explore Lobbies

Setup prerequisites

A test workspace with access to In-game Chat.
Step 1: pending
A confirmed API version and documented permissions for the workflow.
Step 2: pending
Client and backend tests for successful, invalid, repeated, and interrupted requests.
Step 3: pending
Review integration availability →
YOUR NEXT CHAPTER STARTS HERE

Build the backend for your next game.

Explore the services and plan your first player experience.