AGO Chat - tenant 2

A second, independent shop on the same platform - its own site, its own operator login, nothing shared with the other demo tenant except the code.

Why this page looks different

demo-shop1.reserve-me.ru and this page are two separate sites in the same running deployment - the platform's actual multi-tenancy boundary, not a cosmetic one. Every row either tenant's visitors or operators can reach is scoped to its own site id; there is no shared conversation queue, no shared operator, no way for one tenant's login to see the other's data. The different color scheme here is deliberate, so that boundary is visible at a glance and not just true underneath.

Try it

  1. Open the chat bubble in the bottom-right corner of this page and send a message.
  2. Open the operator console in a new tab (or a private/incognito window - the console's own Keycloak session is a cookie, so a second identity needs a separate browser context): console.reserve-me.ru - log in with the credential below, not demo-shop1's.
  3. Find your message in the queue and reply. Then check demo-shop1's own operator login in your original tab or window - it will not see this conversation at all.

Operator login for this tenant (throwaway, safe to publish)

A real, working credential against the console above - deliberately public, not a leaked one. It only ever grants access to this tenant's own data, never demo-shop1's.

Username
demo-operator-2
Password
demo-operator-2-password
Open the operator console