Skip to content
For the complete documentation index, see llms.txt. This page is also available as Markdown.

Webchat

Learn about Hablla's Webchat channel: what it is, how search mode identifies each visitor on your site, and what visual customization options are available.

What is Webchat

The Hablla's Webchat is a support channel that allows your customers to talk to your company directly through the website, without needing to leave the page. In practice, it works the same way as the other channels on the platform, such as WhatsApp, Instagram and Telegram: it is one more connection within Hablla. This means that Webchat can use:

  • Flows

  • Artificial Intelligence

  • Bots

  • Human support

  • Automation

The only difference is the point of contact: instead of a messaging app, the conversation happens within your company's website.


Important to Know

Before configuring the channel, it is worth understanding two concepts that define Webchat's behavior: how it identifies who is chatting and how it appears on your website.

1. Search mode

Just as WhatsApp uses the phone number to know who is on the other side, Webchat also needs a unique identifier to recognize the visitor.

This identifier is what ensures:

  • the preservation of the conversation history;

  • recognition of the user who has already spoken with you;

  • that duplicate leads are not created;

  • continuity of service even after refreshing the page.

The field Search mode, on the channel settings screen, defines which of these behaviors will be used. Next, we will talk about each of the modes available for configuring your Webchat channel in Hablla:

1.1. Automatic Search Mode

In this mode, your Webchat automatically generates an ID for the visitor and saves it in the Local Storage of the user's browser, that is, the person who sends you a message through Webchat on your website.

With this, the user can refresh the page, leave and come back later, and the conversation continues normally. It is the simplest mode to set up and does not require any development on your website.

1.2. Manual Search Mode

Here, you define which information will be used as the identifier of the user communicating with you and where that information will be obtained. For example:

  • CPF

  • Email

  • Internal system ID

  • Registration number

  • User code

In this mode, you must also define what the search source, that is, where the system will look for the information you defined as the identifier:

Search source
Where Webchat looks for the identifier

Local Storage

Browser storage that remains saved even after closing the tab or the browser.

Session Storage

Temporary browser storage used during the Webchat session. The data remains available while the session is active, respecting the expiration time configured by the system.

Cookies

Cookies stored in the user's browser by your own website.

Custom

Your website's own system sends the identifier to Webchat, initializing the messaging system based on the ID provided by your system.


2. Visual customization

The Webchat connection also allows you to customize the appearance of the button and the support window, so that the channel matches your website's visual identity. Among the available options, you can customize the Layout, Typography, and Colors of your Webchat.

Layout and Design

  • Chat display format

  • Screen placement (the four corners)

  • Entrance animation

  • Vertical and horizontal spacing

  • Height and width of the chat and button

  • Chat image and button image

Typography

  • Font

  • Size

  • Font weight

  • Message text color

Colors

  • Light, Dark, or Automatic mode

  • Chat header in solid color or gradient

  • Customer message color

  • Button color

While you make adjustments, the platform displays a real-time preview in the bottom right corner of the screen or in the position you chose for the widget to load. This makes it much easier to get the details right without needing to publish anything.

The preview is only meant to show the widget's appearance. It does not perform real tests of sending and receiving messages.

Best practices

  • Confirm that there is already a department registered before you begin creating your Webchat connection.

  • Use descriptive names for connections and credentials to make management easier when there is more than one Webchat.

  • We recommend using search mode in the Automatic mode when there is no login on the website; use Manual only when there is a reliable identifier available on the page.

  • Test locally before publishing the script on the production website.


Note: This documentation covers only how the feature works. For information about billing, costs, or commercial terms, consult the current contract or contact the responsible department.

Last updated

Was this helpful?