Settings
Settings has seven sections, listed in the sidebar: AI assistant, Widget, Live chat, AI providers, Workspaces, API & MCP and Data & privacy. This page covers all of them except Live chat and AI providers, which have their own pages: Live chat and AI providers.
Settings are saved with the save bar that appears once you change something, and they take effect on the storefront immediately.
AI assistant
How the assistant thinks and speaks.
Behaviour
| Setting | Description |
|---|---|
| Instructions | Your business description, rules, prohibited topics, and any other standing context. This is the field to use for anything that must always apply. |
| Tone of voice | A free-text description of how replies should read, for example friendly and casual, professional and formal, or concise and direct. |
| Base prompt | The top-level framing of the assistant's role. Keep it short. Leave it empty to use the built-in default, which is the right choice for most stores. |
Language
| Setting | Description |
|---|---|
| Preferred language | The language the assistant answers in when it cannot tell the visitor's. The list holds 65 languages. The assistant answers each customer in the language that customer wrote in, so this is the fallback, not a restriction. |
For per-scenario procedure rather than standing rules, use Guidance.
Widget
How the chat looks and what it says before the customer types anything.
Widget
| Setting | Description |
|---|---|
| Show the chat widget | Turns the widget on or off for this workspace. |
| Hide the chat until the knowledge base has content | Keeps the widget hidden on the storefront until your catalog is synced. Without a knowledge base the assistant cannot answer catalog questions, so this avoids a first impression made by an assistant that knows nothing about your store. |
Assistant
| Setting | Description |
|---|---|
| Name | The name shown on the assistant's messages. |
| Avatar | An image shown next to the assistant's name: PNG, JPEG, WebP or GIF, up to 2 MB. Upload, replace, or remove it. |
Welcome
| Setting | Description |
|---|---|
| Welcome message | The greeting shown when the chat window opens. |
| Suggested questions | Questions shown as chips under the welcome message, one per row. A visitor who picks one sends it as their first message; typing instead hides the chips. Blank rows and duplicates are dropped on save. |
Chat window
| Setting | Description |
|---|---|
| Colour | The accent colour of the chat window. Pick from the presets or enter a hex colour. |
| Position | Bottom right or Bottom left. |
| Title | The heading of the chat window. |
| Subtitle | The line under the heading. |
| Invitation message | The message that invites a visitor to start chatting. |
Chat button
| Setting | Description |
|---|---|
| Colour | The colour of the launcher button. |
| Position | Bottom right or Bottom left. |
| Label | The text on the launcher button. |
Conversation
| Setting | Description |
|---|---|
| Allow file attachments | Lets visitors attach a file to a message, so the assistant can answer about a document or a photo. On by default. Turning it off removes the attach control from the composer and makes the service reject uploads for this workspace, so it cannot be bypassed from the storefront. Individual files are capped at 10 MB. The assistant understands what an image shows, but finds products from it by keywords, not by comparing pictures - see Images and screenshots. Your team can still attach files to live chat replies. |
| Play a sound on new messages | Plays a short chime when the assistant replies. Off by default. When it is on, the visitor still gets a mute button in the chat window header, and their choice is remembered in their browser. |
| Open links in | How links in the chat's messages open: A new tab or The same window. |
Anything not on these lists - the distance from the screen edge, the width of the chat window, its stacking order against your own fixed elements - is done with CSS in your theme, against the widget's stable selectors. See Customize widget appearance.
Which storefront pages the widget loads on is not set here - it is a Magento-side setting, because on an excluded page no widget script is injected and no request reaches eChat at all. See General Settings.
Workspaces
One Magento installation can connect several store views, and each connection is a workspace. This section groups them under one account so you can see and manage them together.
Each workspace keeps its own knowledge base, its own settings, and its own conversations. Grouping is for management only - it does not merge any data.
Each workspace card shows its name, its storefront domain, the Magento admin URL it was registered from, its live status, whether its Mirasvit license is active, and when it was last used for a chat.
| Action | What it does |
|---|---|
| Rename | Gives the workspace a recognizable name instead of a bare domain. |
| Delete | Removes the workspace. Its knowledge base, settings, and conversations are kept for 30 days, so an accidental removal can be undone on request, and are then permanently deleted. |
| Get a link code | Mints a code you paste into another workspace to group the two. The code is valid for 15 minutes and can be used once. |
| Add a workspace by code | Pastes a link code from another workspace and links it into this account. |
| Merge into this account | Appears as a warning banner when another account already holds workspaces for this store. Merging keeps every workspace for the store together. |
Stores connected before version 1.2.0 join their account automatically on the next sync. No reconnection is needed, and a change of domain is picked up the same way.
Data & privacy
This section holds the controls for your shoppers' data. See Privacy and GDPR for what eChat stores and where.
-
Keep conversations for - how long a conversation is kept after its last message: Until deleted (default), 30 days, 90 days, 180 days, 1 year or 2 years. Every day eChat deletes the conversations older than that, with their messages and attachments, and the visitor data they leave behind: browsing history, location and device. Click Save to apply.
-
Erase a shopper's data - for a GDPR erasure request. Enter the shopper's email and click Erase data. eChat first shows how many conversations and messages it found, then deletes them whole, with their attachments and the browsing history they leave behind. It finds:
- all conversations of a visitor eChat has that email on file for: a signed-in customer, a visitor who left a message for your team, or one whose email your team saved in live chat;
- every conversation where a guest typed that email or gave it for an order lookup, a verification code or a ticket. The guest's other conversations stay, and so does their browsing history while those remain.
The assistant's replies are not searched, so your own contact address in them does not pull in other chats. The match ignores upper and lower case.
Deleted data cannot be restored.
API & MCP
How an AI assistant or a script reaches this workspace from outside the eChat backend: the MCP server URL, the GraphQL endpoint and its access key, the assistants you have connected, and Regenerate key. See API & MCP for how to connect and what a connection can do.