Zora Support

Zora Support/Docs

Users & agents

Manage visitors, leads, agents, and admins—and collect the details you need before chat starts.

Zora Support tracks people who chat with you (visitors, leads, and registered users) separately from your internal team (agents and admins).

User types

  • Visitors — anonymous people browsing with the widget loaded
  • Leads — contacts with partial details (for example an email from a follow-up form)
  • Users — contacts with a fuller profile in your workspace
  • Agents / admins — team members who sign in to the admin console

New contacts appear in the users table in real time. Enable visitor registration in settings if you want to see online visitors who have not yet started a chat.

Manage agents and admins

Create and edit agents from the Users area with Add user. Only agents and admins can sign in to the admin console.

Configure:

  • Agent privileges — what each role can see and change
  • Supervisor — an admin (or comma-separated admin IDs) with elevated oversight

Agents can set themselves online or offline from the profile panel. With away mode enabled, inactivity in the admin can automatically mark an agent offline (desktop sessions).

Collect user details

Gather name, email, and other fields with:

  • A registration / pre-chat form before the first message
  • Built-in follow-up messages
  • Chatbot flows that ask for information mid-conversation

Keep forms short—ask only for what routing or follow-up requires.

Registration (pre-chat)

The registration form can act as a lightweight gate: email only, name only, or a fuller profile. A login form appears when the email field is enabled. You can also pass identity via URL parameters when you already know who the visitor is from your own app.

Login verification URL

Under user settings you can point Zora at an external verification endpoint. When someone signs in through chat, Zora requests that URL with email and password query parameters. Your endpoint should return JSON describing the user (name, email, optional avatar, department, and related fields) so Zora can register and log them in automatically.

Online presence

  • Online/offline status for agents is visible to routing and availability logic.
  • Online-user notifications (when enabled) cover visitors and leads and typically fire once per user in a 24-hour window.
  • The users table paginates similarly to conversations (about 100 rows per scroll).

Next steps

Set office hours and departments, enable chatbot & AI, or automate identity with the JavaScript API.