Identity in the live chat widget

    How Gruvi handles the email address a visitor types, and the three options for confirming who they are.

    5 min read · Updated 27 October 2026

    The live chat widget can collect a visitor's email address. These settings control what Gruvi does with it.

    What these settings do

    The pre-chat form asks for a name and an email address so you can follow up after the chat.

    A typed address does not by itself tell Gruvi who the visitor is. You choose whether Gruvi treats it as confirmed, and how it is confirmed.

    This matters when a visitor asks about something they did before, such as a previous request. Showing that history means linking the conversation to a customer record.

    Verified and unverified

    An email address on a conversation is either verified or unverified.

    Verified
    The chat joins the customer with that address. The visitor can see their previous requests, and Chloe and your connected apps treat them as that customer.
    Unverified
    The address is collected so you can follow up. The conversation is not joined to the customer record, and previous requests are not shown.

    An unverified conversation works normally. You can answer anything that does not depend on the visitor's history.

    Where to find the settings

    1. 1Go to Settings, then Channels, then Live Chat.
    2. 2Open the chat box you want to change.
    3. 3Go to the Rules tab.
    4. 4Scroll to Identity verification.

    There are three settings. They work independently, and all three are off when a chat box is created. Each chat box has its own settings, so a widget on your website can be set differently from one inside your product.

    Require identity verification

    Gruvi accepts a visitor only if their identity is signed with a valid token from your server. Visitors without a valid token are rejected.

    The visitor does not type an address, so the identity comes from your own sign-in. This needs a developer and a product that people log into. See how to set up the identity token.

    Trust the typed email

    Gruvi treats any typed address as confirmed. The chat joins the customer with that address, and Chloe and your connected apps treat the visitor as that customer.

    Anyone who types an address will see the requests linked to it. Use this option where the widget is already behind a sign-in of your own, such as a product or an internal tool.

    How the session is remembered

    With Trust the typed email on, the visitor's browser keeps the session.

    • If the visitor comes back on the same device and the cookies are still there, they are not asked for their email again. Their previous requests are already available.
    • If the cookies or cache are cleared, they are asked for their email again. Once they enter it, their previous requests are shown.

    The session therefore depends on the device, and on an address that anyone could type. This is a light form of sign-in, which is why the setting is intended for a widget behind your own secured environment.

    Ask for a code

    Gruvi emails a 6-digit code to the address. The visitor enters it before the chat starts, and the chat then joins the customer with that address.

    This works on any website and needs no development work. It adds a step before the conversation begins, and some visitors will not complete it.

    Verifying someone by hand

    When an unverified address appears on a conversation, a Verify button sits beside it. Click it to mark the address as verified.

    Use it when you already know who you are talking to, for example because you recognise the person or have confirmed their identity another way.

    Was this helpful?