Create Accountor Login
Docs

MountDev Ops Chat

How MountDev Ops Chat works, page by page. Updated November 17, 2026

MountDev Ops Chat documentation | Updated November 17, 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 8,865 automated checks before it ships, and every screen change is walked through before release.

Tested Every Release

All 67 of Chat's own automated checks run on every update.

What they cover: Live chat | Email | Files and attachments | Spam and abuse protection

What Chat Is

Chat puts a chat bubble on any of your websites. Visitors write to your team from it, and your team answers live from the workspace: new messages appear on their own, without reloading. Outside your office hours the bubble says when you are back and offers a form instead, which becomes a Helpdesk ticket when Helpdesk is added. A chat becomes a Helpdesk ticket or a CRM lead in one click, and a visitor can get the transcript of their chat by email.

Chat is your company's own website chat, with your visitors. Your team talks to itself in Channels, which visitors never see.

Chat starts with the modules below, and every one of them can be changed, given its own icon, turned off, or deleted on Chat's Settings page, the last item of its menu, the same as any module (Modules and Fields). Chat works on its own; Helpdesk and CRM are needed only for turning chats into tickets and leads.

In These Docs

  • Answering Chats: the Chat page, who is on your websites now, being available or away, replying, notes, closing, assigning, tickets and leads in one click, files from visitors, transcripts, and the emails visitors get.
  • Chat Widgets: as many widgets as you like, each with its own snippet, look, questions, and messages, landing in one customer group, and answered in one place.
  • The Website Snippet: putting the chat on your websites, what visitors see, files from visitors, how visitors are known, and how the chat is protected from abuse.
  • Chat Settings: the bubble's look and words, name and email, your websites, office hours and closed days, who hears about new chats, and the address emails go from.
  • Permissions for Connections: every permission an app or an AI assistant can be given in this app, with its level.

Starting Modules

  • Conversations: listed on the Chat page rather than in the menu. The visitor's name and email, status (Open or Closed), source (Chat or Offline Form), the website and page it started on, who it is assigned to, when it started and closed, the visitor's random id, the Helpdesk ticket and CRM lead it became, and its transcript.
  • Messages: shown in each conversation rather than in the menu. The conversation, who it is from (Visitor, Team, Note, or Notice), their name, the message, and when it was sent. Notes are for your team only; notices are lines both sides see, such as who closed the chat.

Who Can Do What

  • Answer website chats (owners, admins, and members): the Chat page, replying, notes, closing, taking a chat, making tickets and leads, and emailing transcripts.
  • Change Chat Settings (owners and admins): Chat Settings, the website snippet, and giving a chat to someone else.
  • Roles decide which conversations each person sees, as in every app (Roles).

AI Agents

A connected AI agent can see the Chat page and a chat (chat.home, chat.conversation.get), add notes (chat.note), make a Helpdesk ticket or CRM lead from a chat (chat.ticket, chat.lead), and read Chat Settings (chat.settings.get). It never replies to a visitor, closes a chat, emails a transcript, changes who a chat is assigned to, or changes settings or the snippet: those reach your visitors or your setup, so they stay with people. It sees that a visitor shared a file (its name, kind, and size) but never opens it; a ticket or lead it makes from a chat carries the chat's files along, as one a person makes does.

Moving from Another System

Website chats from another system move in with Settings, Import and its Export for MountDev Ops file (Importing): each chat with its visitor's name and email, the page it started on, whether it was closed, and every message, including the team's notes. Chat is added for them. Images shared in the old chats stay there; their messages say so. Files visitors share in Chat itself are kept with each conversation in your workspace (Files on Records). Importing never deletes anything, here or in the old system, and running it again updates instead of copying.

Ask Us Anything

We’d love to hear from you!