If you’d rather read the explained summary instead of this plain list, start with Key concepts.
Access to everything — an agent switch that grants access to every resource in your account (documents, templates, MCP servers) without needing tags. See AI agents.
Account (tenant) — your agency or business inside Aymar Agents, an isolated compartment. See Key concepts.
AI agent — the configurable identity that handles your conversations: instructions, model and assigned resources. See Key concepts.
API key — a secret credential for calling /public/v1 from your own code. See
API keys and access media.
Appointment — a scheduled event in the Calendar, created by hand or by the AI, with a slot computed by the availability engine. See Calendar and appointments.
Audience — Internal or Both; decides whether an anonymous visitor on a public channel can reach an
action, template or document. See Agent control: resources and permissions.
BYO-MCP — an external MCP server you register yourself in Settings to give your agent access to a system of your own with no native connector; under your own responsibility. See Integrations.
Campaign — sending an approved WhatsApp template to a list or a selection of contacts. See Contacts and marketing.
Channel — the type of path your agent talks through (WhatsApp, Telegram, Web widget, Messenger / Instagram Direct). See Channels.
Confirmation (MCP) — the confirm: true argument every write tool of the MCP server requires before
touching the API. See Confirmation on writes.
Connector — a first-party integration resolved live (HubSpot, for example): a token or credential, a real verification, and actions enabled one at a time. See Integrations.
Contact — the customer’s own record (phone, verification, marketing lists), shared across all their leads and conversations. See Contacts and marketing.
Conversation — the message thread with a customer on a channel instance; AI, HUMAN or QUEUED modes. See Conversations.
Editor (role) — a role with day-to-day operation (conversations, leads, appointments…) with no access to billing. See Team and roles.
Escalation — when the AI stops answering and hands the conversation to someone on your team, either because the customer asks or a rule fires. See Conversations.
Flow — a multi-step process, with optional branching, that your digital team runs on its own. See Jobs and flows.
Funnel — the sequence of stages a lead moves through, with its kanban board. See Leads.
Hand-off (between agents) — passing a conversation from one agent to another, with configured rules and destinations. See Hand-off between agents.
Instance — one concrete connection of a channel (a WhatsApp number, a widget); several instances of the same type can coexist. See Channels.
Instruction (“consigna”) — a flow you ask your assistant to build over chat, in your own words; it’s generated and edited exactly like one built by hand. See Jobs and flows.
Job — a standalone task your assistant runs, once or repeated, with its own step-by-step history. See Jobs and flows.
Lead — an opportunity in your sales funnel, captured automatically by the AI or entered by hand. See Leads.
MCP (Model Context Protocol) — the open standard used both by Aymar Agents’s own MCP server and by any external MCP server (BYO-MCP). See MCP.
MCP server — a server that exposes tools over the MCP protocol; either Aymar Agents’s own (exposes your account to your external AI) or an external one you register (BYO-MCP, plugs third-party tools into your agent). See MCP.
Memory (customer) — the automatic summary the agent keeps per contact, shared across channels; visible, editable and deletable from their record, with configurable retention in Settings. See Marketing and contacts.
Mode: AI / HUMAN / QUEUED — the three states a conversation can be in, depending on who is answering right now. See Conversations.
On-screen assistant (Copilot) — the assistant that navigates, highlights and, with your explicit confirmation, fills in and clicks real buttons on your own website or Platform. See Support and on-screen assistant.
Permission — the fine-grained catalog that decides what an identified caller (person, channel employee, API key) can do, per area of the account. See Agent control: resources and permissions.
Plan — your account’s subscription tier (Starter, Pro, Enterprise), which decides what’s available (the public API and MCP, for example, only on Pro and Enterprise). See Billing and plans.
Quality (lead) — an interest rating: Hot, Warm, Cold or Unrated. See Leads.
Resource — anything an agent can use: a document, a template, or an MCP server. See Key concepts.
Responsible person — the person (or whole team, if none is assigned) who’s notified when a conversation on a given channel escalates. See Channels.
Role — Admin, Editor or Viewer; decides which screens and actions each person on your team can reach. See Team and roles.
Scope — the specific permission (read or manage, per resource) sealed into an API key. See Authentication.
Tag — a word or phrase that groups resources (documents, templates, MCP servers) to decide which agent can see them. See Key concepts.
Task — see Job.
Template — a WhatsApp message pre-approved by Meta for messaging outside an ongoing conversation, or a reusable knowledge-base document. See Contacts and marketing and Knowledge and documents.
Tenant — see Account.
Ticket (internal) — an internal case your team runs about a contact, linked to their lead or conversation when relevant. Different from a Support ticket (to ask your provider for help). See Tickets.
Viewer (role) — a role that can see most screens but change nothing. See Team and roles.
Web widget — the chat embedded on your own website; each instance has its own snippet and language. See Web widget.