Widget settings

The widget studio (Widget) is split into seven tabs: Behaviour, Greeting and auto replies, Working hours, Contacts and privacy, Conversations, Appearance and Install. This page documents every field on those tabs, under the exact label shown in the product. For presets, the live preview, allowed origins, the install snippet, diagnostics, popups and Web Push, see Site widget and Widget quickstart.

Behaviour

Visibility

When to show the widget: on every page, only after you write to the visitor first, only if the visitor already has a conversation, or by an address list.

The address-list mode is set separately for desktop and tablets (wider than 480 px) and phones (480 px or narrower). Each device gets its own rule: show everywhere, show everywhere except the list, show only on the list, or do not show. The list holds up to 50 addresses, each at most 200 characters. An asterisk stands for any part of the address: /blog/* matches every blog page, while https://shop.example/cart matches one exact address. A plain pattern without http is matched against the page path and query string; a pattern starting with http is matched against the full address.

Visitor notifications

Three independent switches so the visitor notices your reply even after switching tabs: the unread counter on the launcher, a new-message sound, and flashing the browser tab title. Sound is No sound, Chat replies only or Replies and invitations (the invitation next to the launcher plays it too). The sound has its own Play button right in the studio.

Launcher and invitation

On top of the usual shape, size, position and offsets: separate offsets for phones (8-64 px on each axis). Without them, phones use exactly the same offsets as desktop. The custom icon and the launcher animation live on the Appearance tab, see below.

Invitation frequency: by default it follows the general dismissal pause (Do not disturb again for, hours, on this same tab), or you can pick Once per visit or On every page instead, independent of that pause.

Auto-open

Automatic chat opening, the delay in seconds, a desktop-only restriction, keeping an unfinished visitor message, the pause before re-inviting, and where the widget lands on reopen: the welcome screen or straight into the conversation.

Greeting and auto replies

Welcome screen and knowledge base

The welcome screen's heading and supporting text. Right there, an optional knowledge base link: a label up to 60 characters and an HTTPS address. The link appears on the welcome screen, next to the suggested questions.

Suggested questions

A handful of buttons whose text is sent into the conversation on click. Choose a reaction for each button, otherwise the visitor presses it and gets no useful automated reply. No keyword trigger is needed: the reaction fires immediately.

Statuses and reply expectation

Online status text, offline status text, and the reply-expectation text shown in the chat header.

Auto reply during working hours

While no operator has joined the conversation yet, the widget can reply on its own. The delay is configurable (5 seconds by default, 3-300), and the text differs depending on whether the visitor's contacts are already known. You can additionally ask for an email or phone number right inside this message: the contact field appears inside the message itself, with no separate form. It is sent once per conversation, only if nobody has answered within that time.

Auto reply outside working hours

A separate auto reply for when the widget is closed by the schedule (the Working hours tab). It is an ordinary conversation message, not a header caption: the visitor sees it, the operator sees it in their inbox, and it stays in the conversation history. It is sent once per closed period, not on every visitor message.

Messenger buttons

Up to eight buttons so the visitor can continue wherever suits them: Telegram, WhatsApp, VK, MAX, Viber, Instagram, Facebook, or a custom link with its own label. Fill in from connected channels pulls in the links of already-connected channels automatically; if a connected channel has no public link, add the address by hand. The Telegram button accepts either a regular https://t.me/... link or a tg:// deep link that opens the Telegram app directly, skipping the browser. The order of buttons in the list is the order they are shown in, and each one can be shown or hidden individually.

Working hours

The Working hours tab sets the weekly schedule, time zone and special dates, see Site widget for details. A separate switch, Show offline while nobody is at the console: if every operator has left the console, the chat shows the offline status even when the schedule says it is currently open. The schedule describes configured hours, not that an operator is at the keyboard right now — this switch adds a second, more honest check.

Contacts and privacy

Contact form

The pre-chat form, its fields (name, email, phone, order number) and whether they are required — unchanged from the previous release, see Site widget.

Personal data

A privacy policy link: one address shown both in the contact form and under the message box (Show the link under the message box). If left empty here, the widget falls back to the contact form's link.

Ask for consent before the first message — with a consent text up to 300 characters — shows a checkbox right inside the message box: without it the visitor cannot send their first message. That checkbox lives inside the message box, so if the text field is turned off on Conversations → Composer, nobody is left to confirm consent — keep the two switches in sync.

A cookie banner: its text and button label. The banner is shown once, until the visitor presses the button.

Conversations

Closing a conversation

A conversation is automatically marked resolved after a silent pause — 60 minutes by default, configurable from 5 to 1440. After that pause it leaves the active list.

Operator rating

Once a conversation is closed, the widget can ask the visitor to rate it: a three-emoji or a five-star scale, your own question (default: "How was this conversation?") and a thank-you text after the rating. The studio shows a live preview of how the rating card looks in the chat. The collected ratings are CSAT: find them in Support → analytics, alongside load, SLA and the per-operator breakdown.

Copy by email

If nobody has replied to the visitor within the chosen delay (1, 2, 4, 8 or 16 minutes), the widget emails a copy of the unread message. It needs a connected email channel; without one, nothing is sent. To keep one conversation from flooding the inbox, at most one copy per conversation is sent per hour.

Composer

Four independent switches: the text field, voice messages, attachments and emoji. Turn the text field off only if the visitor answers with buttons alone; with the field off, nobody is left to confirm consent from Contacts and privacy, if that is turned on.

Appearance

"Powered by GetMyBot"

The caption in the chat header can be hidden; the switch becomes active on a paid plan.

Custom icon and launcher animation

On the Launcher button card: a custom icon that replaces the default glyph (PNG, JPEG or WebP up to 64 KB), and up to three animations at once (wobble, pulse, wink). The button moves about once a minute, unless the visitor asked the browser for less motion.

Conversation background

A subtle pattern behind the messages: no pattern, dots, waves, diagonal, grid or confetti. It is drawn in the muted colour and stays barely visible.

Advanced

Both the brand card and the panel card have a collapsed-by-default Advanced section for fine tuning that not every site needs.

Install

Site platform

Choose your platform — Tilda, WordPress, 1C-Bitrix, GetCourse, Taplink, Wix, Webflow, or React / Next.js / Vue — and the studio shows three steps tailored to it: where to paste the snippet, when to run diagnostics, and the one pitfall that trips that platform up most often. Next to it is a link to the full guide: Tilda, WordPress, 1C-Bitrix, GetCourse, Taplink, Wix, Webflow, React / Next.js / Vue.

Send to developer

The Send to developer button copies a ready message to the clipboard: the link to the guide for the chosen platform, the install snippet itself, and the list of already-saved allowed sites. Handy to forward to whoever actually pastes the code on the site.

Tracking wizard

The Install tab links to the browser-events tracking studio. Its one-step wizard can create a rule for a page visit, an element click, or a form field fill. Scroll-to-end tracking is not supported, neither by the wizard nor by the full rule editor; it is not one of the trigger kinds available today.