Glossary
Terms you will see in the admin and in these docs that may be new to you, and what each one means in SupaTalker
When you first use SupaTalker you will run into a lot of unfamiliar terms. Some are concepts of this system (skills, knowledge base, host sites), some come from external platforms such as LINE and Meta (Webhook, rich menu, persistent menu), and some are AI terms (MCP, RAG). This page collects them in one place, and each term points to the page that explains it in detail.
The three pairs people mix up most
- Sync vs. list — syncing puts content where the AI can find it; listing decides whether visitors can find it right now. The two are managed separately; see Content status
- MCP connectors vs. MCP API keys — they go in opposite directions: a connector lets this platform reach out to someone else's service, while a key lets an external AI tool connect in
- Anonymous embed vs. member embed — the two ways to add the chat window to your website, and visitors can use different features in each
AI customer support basics
| Term | What it is | Details |
|---|---|---|
| Visitor | Anyone who chats with the AI, whether an anonymous visitor on your website, a signed-in member, or someone who came in from LINE, Messenger or Instagram | Visitors / memory |
| Member | A visitor who has signed in on your website and chats as a member. Members can use more skills than anonymous visitors | Platform overview |
| Skill | A type of question the AI can handle, such as answering questions about the business or looking up orders. When a visitor sends a message, the system decides which skill should handle it | Skills |
| Knowledge base | The site's frequently asked questions and answers, the main source the AI answers from | Knowledge base |
| Entry | One item in the knowledge base, made up of a question, an answer and a category | Knowledge base |
| Golden question | A set of questions the platform has already tested. Applying them creates drafts that have the question but still need an answer | Golden question templates |
| RAG (retrieval-augmented generation) | Before answering, the AI first retrieves the relevant content from your data and then answers based on it, instead of relying only on what it already knows. This is how SupaTalker uses the knowledge base: once an entry is synced it enters the retrieval index, and only then can the chat find it. This term does not appear anywhere in the admin | The four states |
| Memory | Facts the system keeps for each visitor, for example "Plans to check in on May 25, 2 people". The AI refers to them when it chats with this visitor later, so it does not have to ask again | Visitors / memory |
| Decide | Memory extracted from conversations starts as drafts; in this step you choose, one by one, whether to include each one | Memory |
| Thread | One unit of conversation. After the visitor has been idle for a while, or a threshold is reached, the visitor's later messages are recorded in a new thread | Conversations |
MCP and external AI tools
| Term | What it is | Details |
|---|---|---|
| MCP | Short for Model Context Protocol, an open standard that lets AI tools connect to external systems and use their features. Official site: modelcontextprotocol.io | — |
| MCP API key | A key issued to an external AI tool (such as Claude Code, Codex or claude.ai) so it can connect in to this platform over MCP and manage the knowledge base | MCP API keys |
| MCP connector | Lets the AI reach out over MCP and use an external service's features, such as checking the weather forecast | Skills: MCP connectors |
| Data source | A skill that lets the AI look up external data, for example checking performance dates in a public Google Sheet | Skills: Data sources |
Channels and external platforms
| Term | What it is | Details |
|---|---|---|
| Channel | A way for visitors to chat with the AI. LINE, Messenger, Instagram and the chat window on your website are each a channel | Platform overview |
| Channels page | The admin page where you connect the AI to Messenger, Instagram and LINE | Channels |
| Facebook Page | The Facebook Page you need before connecting Messenger. You need permission to manage messages on that Page | Channels: Before you start |
| Instagram professional account | The account type you need before connecting Instagram (business or creator). A personal account has to be switched first | Channels: Before you start |
| LINE Official Account | A business's account on LINE. Once visitors add it as a friend, they can chat with the AI on LINE. You need to apply for one before connecting LINE | LINE: Before you start |
| LINE Developers / Messaging API | LINE's console for developers, and the LINE feature that lets the system send and receive LINE messages. You get the two keys here | LINE: Before you start |
| Webhook | The URL an external platform automatically forwards messages to. When LINE receives a message from a visitor, it forwards it to the Webhook URL shown in the admin, and only then can the system reply | LINE: Webhook URL |
| Channel Access Token / Channel Secret | LINE's two keys. The first lets the system send messages on behalf of the Official Account; the second verifies that messages really come from LINE | LINE: The two keys |
| Rich menu | The row of image buttons at the bottom of a LINE chat. Visitors tap one to send a message or open a web page. Only visible in the LINE mobile app | LINE rich menus |
| Persistent menu | A fixed menu in Messenger and Instagram chats. Visitors tap an item to send a message | Channels: Persistent menu |
| LINE broadcast | Proactively sending a message from your LINE Official Account to visitors who have chatted with it, such as a new product launch or an event notice | LINE broadcast |
| OTA / PMS | OTAs are booking platforms such as Airbnb and Booking.com; a PMS is a property management system. Sites using a related industry template can receive messages from booking platforms through a PMS | Platform overview |
The chat window on your website
| Term | What it is | Details |
|---|---|---|
| Chat widget | The chat window embedded on your website, where visitors can chat with the AI without leaving the site | Host sites |
| Host site | A website you embed the chat widget into. Only registered websites can embed it | Host sites |
| Embed code | A snippet of code you paste into your web page; once it is there, the chat widget appears on your website | Code integration |
| Anonymous embed | Visitors can chat without signing in, but can only use the knowledge base | Anonymous embed |
| Member embed | After a member signs in on your website, they chat as a member, with more skills available than anonymous visitors. Needs your website's developer to integrate it | Member embed |
| Entry ticket | In a member embed, a credential your website's backend issues for a signed-in member to show who this visitor is | Code integration |
| Host ID / secret | The two things a member embed host site gets when you create it; your website's backend uses them to issue entry tickets | Member embed |
Content status
The knowledge base, products, rich menus and store settings are all designed so that editing something does not make it live. These terms tell you how far a piece of content has gone:
| Term | What it is | Used in |
|---|---|---|
| Save / draft | Stores your changes, but they do not affect the AI or what visitors see yet | Throughout the admin |
| Sync | Puts saved content where the AI can find it, or uploads it to an external platform (for example, syncing to LINE) | Knowledge base, product Q&A, rich menus, persistent menus |
| List / unlist | Decides whether visitors can see the content, and the AI can find it, right now. To stop using something for a while without deleting it, unlist it | Knowledge base, products |
| Publish | Applies the whole store settings draft to the store page customers see | Store settings |
| Set as default | After a rich menu is synced to LINE, it still has to be set as default before all LINE users see it | LINE rich menus |
| Layout | How things are arranged, for example how many cells a rich menu has and how they are laid out | LINE rich menus |
| Template | Ready-made content you can apply directly, such as golden question templates or the template catalog for beautified images | AI-generate beautified image |
Saving or syncing can be blocked
Content the AI refers to, such as the knowledge base, products and visitor memory, is reviewed by AI when you save or sync it. Sentences that read like instructions to the AI are blocked, for example asking the AI to use a certain tone or play a certain role; content such as passwords or personal data may also be blocked. See Content review before syncing for examples.
Security and accounts
| Term | What it is | Details |
|---|---|---|
| Owner / Admin | The two roles of admin accounts. An Owner can use every feature, including managing other admin accounts; an Admin can use the general features but cannot manage accounts | Admin accounts: Two roles |
| Human verification | The Cloudflare check below the password field on the sign-in page. It runs on its own and confirms that a person is signing in | Sign-in & password |
| Protection rules | Set which messages or behaviors count as a hit, and the action on a hit: log only, reject, mask or block | Security |
| Security events | The record of protection rule hits, which also includes the admin's own activity log | Security |
| Blocklist | Who is currently blocked; all messages they send while blocked are stopped | Security |
| Voice input (STT) | STT stands for speech-to-text. Visitors send a message by voice, and the system converts it to text before the AI handles it | Settings: Voice input |
Sign-in & password
Signing in to the admin, setting your password the first time, resetting a forgotten password, and the account menu and My account page after you sign in
Dashboard
The home page after you sign in to the admin — the conversations, orders and support requests that need attention now, and trends over a period