Create Accountor Login
Docs

Chat Widgets

Part of the MountDev Ops Chat documentation. Updated November 16, 2026

MountDev Ops Chat documentation | Updated November 16, 2026

Our Commitment

MountDev Ops is built security first. Your business data belongs to you, and you can export all of it at any time. We never use analytics or tracking of any kind inside MountDev Ops.

Every update passes all 4,888 automated checks before it ships, and every screen change is walked through before release.

Many Widgets, Each Its Own

A widget is the chat bubble on a website. Make as many as you like, up to 50. Each widget lands its chats in one customer (External) group, and has its own snippet, its own key, its own look, its own questions, and its own messages. Every chat from every widget arrives in the one Chat panel and is answered there. There is no separate inbox for a widget.

Owners and admins open Chat Widgets in the Chat app's menu, above its Settings (action chat.widgets.list). Each widget is a card with its name, a state (Published, Draft, or Off), Changes Waiting when edits are saved but not published, the group its chats land in, the websites it runs on, and a small picture of how it looks. Add Widget makes a new one (action chat.widgets.create). Edit opens the editor. Get Snippet opens that widget's snippet.

Your Original Widget

The widget you had before this page is now your first widget, marked Your Original Widget. It lands its chats in Website Visitors. Its title, greeting, color, position, name and email choice (now its first two questions, optional or required as they were), offline message (now its After Hours message), and websites carry over, and its snippet and key do not change. Nothing already installed breaks, and nothing on a website changes until a person edits and publishes it. Chat Settings still holds your office hours, closed days, emails, and the switch that turns all chat on or off.

The Editor

The editor is one page: the form on the left and a live preview on the right (below the form on a phone). The preview changes as you type and has four views: Chat Form, Away, After Hours, and Bubble Only.

  • Widget Name and Chats Land In: only customer groups are listed. Changing the group moves who sees the widget's chats at once. No chat is deleted or moved.
  • Title, Greeting, and Button Text: the words on the bubble, like Chat With Us. Empty shows the round chat button.
  • Color, with Use My Brand Color (your Brand Kit color, or your company's color) and a check that says Readable or Hard to Read. Text on the color is white when it reads at 4.5 to 1 or better, else dark. A color that is Hard to Read cannot be published until it is changed.
  • Position on the Page: bottom right or bottom left.
  • Logo or Avatar Letters: up to three letters. Empty uses the first letters of the title.
  • Questions Before Chatting: up to five, so a chat starts quickly. Each is a name, an email, a short answer, or a pick-one with 2 to 8 choices, and each can be Required. A widget asks for a name once and an email once. The answers to short-answer and pick-one questions reach your team as one internal note on the chat. The visitor never sees that note.
  • When Nobody Is Online: shown while your office hours are open and nobody is set Available (when Chat Settings need someone available).
  • After Hours: shown outside your office hours.
  • Websites: where the widget may run. Empty lets it run wherever its snippet is.

Office hours, closed days, and the abuse limits stay the company's, in Chat Settings. They are not set per widget.

Draft, Publish, and Turn Off

These are a person's steps. A new widget is a Draft and shows nothing until Publish Widget (action chat.widgets.publish). The save bar (Save, action chat.widgets.save) keeps your work, and Publish saves it first. Editing a live widget saves changes that wait: the widget shows Changes Waiting and visitors keep seeing the live look until Publish Changes. Discard Changes (action chat.widgets.discard) throws the waiting changes away. Turn Off Widget (action chat.widgets.off) asks once and stops the widget showing on every page. It can be published again, and its chats and settings stay.

The Website Snippet for One Widget

Get Snippet opens a pop up for that widget (action chat.widgets.snippet): the line to paste, Copy, three short steps, and Make a New Snippet (action chat.widgets.snippet.reset). Making a new snippet asks once ("Turn Off Old Snippet") and turns off this widget's snippet only. Your other widgets keep working. It also opens after a widget's first publish.

Chats from Many Widgets in One Place

Every widget's chats show in the Chat tab of the panel, in the group the widget lands in. Each chat row and its band say where it came from, like "Shop widget | /checkout". When you can see two or more External groups, All Customer Chats shows them together, waiting ones first. A chat opens in the panel like any other conversation, with the customer overlay and the Customer label. The Chat page remains as the same conversations at a larger size.

A chat shows only to people in the External group its widget lands in, and to owners and admins. A person in other groups does not see it in the panel, on the Chat page, or among the visitors on the websites, and cannot read or reply to it.

Workflows and AI Assistants

Workflows and AI assistants can list widgets (chat.widgets.list) and make a new one (chat.widgets.create), which starts as a draft. They cannot change a widget, publish one, turn one off, or make a new snippet: those decide what customers see, so only a person does them.

Ask Us Anything

We’d love to hear from you!