Skip to content
Garuda
Operating

Reading conversations and leads

Conversations shows every stored transcript with the page it happened on; Leads shows the contacts captured with consent. Both are read-only, so you read them here and reach people elsewhere.

Last checked against the running product on 30 August 2026.

These two screens are where the work of the widget shows up. Nothing in either of them estimates, scores or predicts anything: they show what was actually stored.

  1. Start at Overview for the totals

    The first screen in the sidebar has four counters — Agents (with how many are published), Conversations, Messages, and Leads (with the conversion rate) — plus a daily conversation chart, the five most recent conversations and your agents. Every number comes from the server; none is an estimate.

    Workspace insights are not built

    The dark panel on Overview says so. There are no trend recommendations, no intent analysis and no per-agent performance scores in this release. Agent pages say the same thing.

  2. Open Conversations

    The list on the left is every stored conversation, newest first. The search box above it filters the list you already have by visitor name and message text. Selecting a row loads the transcript in the middle.

    A conversation is labelled Lead captured when it produced a lead, and AI active otherwise. Where no lead was captured there is no name to show, so the row reads Anonymous visitor.

  3. Read the transcript and its context

    The middle column shows the messages in order, with the visitor on the right and the agent on the left, and the conversation start time at the top. The right-hand column carries the rest:

    • Captured lead — the email, phone and company on the lead, if one was captured, or a line saying none was.
    • Page metadata — the origin the widget ran on, the page title, and the visitor's locale.

    A message badged Team is one Garuda recorded rather than one either side typed. The one you will actually see is The visitor asked to continue with a person on WhatsApp, written once when somebody used the handoff button, so a thread that moved to WhatsApp does not look like a visitor who simply stopped replying.

    Conversations can be linked to directly

    Adding ?id= and a conversation id to the Conversations URL opens that thread. The links from Overview use exactly that.

  4. Open Leads

    Three tiles at the top — captured leads, lead conversion and conversations — then a table of every lead, newest first. The search box matches name, email and company; the pills beside it filter by status: All, New, Qualified, Contacted and Customer.

  5. Open a lead

    Selecting a row opens a panel with the email, phone, company and source. widget means the visitor consented in a conversation; manual means somebody on your team typed the row in, and that no consent evidence was collected in Garuda.

  6. Act on it outside Garuda

    Reply by email or phone yourself, export the table for your CRM, or wire up a webhook so new leads arrive in your tools automatically. See Exporting your leads and Sending leads to your CRM with a webhook.

    To reach somebody while they are still on the site, the route is the WhatsApp handoff rather than this screen. Switch it on in the agent's Handoff rules and visitors get a button that opens a WhatsApp chat with you: see Handing a conversation to a person on WhatsApp.

You can answer a visitor yourself

Type into the reply box under the transcript and press Enter, or Shift and Enter for a new line. Your answer appears in the visitor’s widget within about twelve seconds, in the same conversation, provided their chat panel is still open — the widget checks for new messages while it is open and stops while the tab is hidden. If they have closed the panel, they will see your reply the next time they open it.Your replies are marked Team in the transcript so you can tell them apart from the agent’s own answers. The agent reads them as part of the conversation, so it will not contradict what you just said. A reply is capped at 4,000 characters.If the visitor has already left the page, the WhatsApp handoff is the way to reach them instead.

Leads is read-only too

The Leads table carries the same badge. You can add a lead by hand and export the table, but you cannot edit or re-status an existing lead from the portal.

Private previews — the Test button and the Conversation playground — never appear in Conversations. Only real widget traffic is stored there.

Both screens request up to 100 records at a time and show that first page, so a busy workspace sees its 100 most recent rows here. The CSV export covers the whole table.

If it still does not work

Conversations is empty after you installed the widget

A conversation is stored when a visitor actually opens the widget and sends something. If nobody has, there is nothing to show — and if the widget is not appearing at all, work through My widget is not showing up.

The transcript will not load

A red box appears with the reason. Reselect the conversation to try again; if it persists, sign out and back in, because an expired session produces the same message.

A conversation has a lead but the list still says Anonymous visitor

The name shown is the name on the captured lead. A visitor who gave only an email address has no name to display, and the lead panel on the right will still show the address.

New conversations have stopped appearing

The plan allows 100 conversations in any rolling 30-day window. Past that, the widget tells visitors it is unavailable and no new conversation is opened. Check Billing, and check the agent has not been paused.

Back to all help articles

Still stuck?

Every article here is written from the product as it works today. If something on this page does not match what you see in your workspace, trust the product and tell us — include the page you were on and what you expected.