Get started

2people.chat documentation

Add the chat widget to your site, recognise your players securely, connect your operator API, and let the AI assistant and your agents work the same conversation together.

#What is the platform?

2people.chat brings player support requests into a single inbox. Every conversation that starts in the widget on your site is first handled by the AI assistant, which answers from your knowledge base and, if connected, with verified data from your operator API. Conversations the assistant cannot resolve, or that meet the hand-off rules you set, are handed over to the agent console or to Telegram.

There are two web applications:

  • Admin console: websites and widget, AI agents, integrations, team and roles, analytics, webhooks, privacy and usage.
  • Agent console: inbox, conversations, saved replies, visitors and a personal profile (availability, working hours, Telegram link).

#Key concepts

Tenant
Your organisation’s isolated workspace. Conversations, team, settings and data belong to the tenant and no other tenant can reach them. API calls name the tenant in the X-Tenant-Id header.
Brand and website
A tenant can hold several brands; every website belongs to one brand. A website has a domain (plus optional extra origins), a widget key (starting with wk_) and a signing secret for player identity.
Visitor and player
Anyone who opens the widget is a visitor. A visitor verified with an identity token signed on your server is linked to the player in your operator system; a player id is never accepted directly from the browser.
Conversation
A chat with one visitor. It can be with the AI, waiting for an agent, with an agent, or closed; messages, internal notes, tags and the satisfaction rating belong to it.
AI agent
An assistant defined, versioned and published to websites in AI Studio. It uses knowledge bases and the tools you allow, and hands over to a person under the conditions you set.
Agents
Team members who take over conversations. What they can do depends on their role (e.g. Agent, Supervisor); conversations are offered to available agents.
Integrations
The operator API connection (player, wallet, deposit and bonus data, plus bonus grants), the Telegram bridge, webhooks and API keys for server-to-server use.

#How the pieces fit

  1. The widget opens on your site and starts a session for the visitor.
  2. If the player is logged in, your page passes an identity token signed by your server to the widget, and the visitor is linked to the verified player.
  3. The AI agent answers. Account-specific data (balance, deposits, bonus history) is read from your operator API, and only for verified players.
  4. When needed, the conversation is handed to an agent, who replies from the console or from Telegram.
  5. Events reach your systems through webhooks; reports are in the analytics screens and the REST API.
Getting startedFrom the invite link to your first test chat, step by step.Chat widgetThe one-line script, data-* attributes, appearance and consent.Player identityVerify logged-in players with a token signed on your server.Operator APIUpload your API document, map it, test it and publish it.WebhooksReceive events in your own systems as signed HTTP requests.API referenceEvery endpoint an API key can call, with its schemas.