Moveo.AI

AI Agents call tools in the form of webhooks and external MCP servers, which the customer adds and tests, and Dialogs connect to external services via webhooks and run task automation such as sending emails and updating databases. The plans page adds custom webhooks connecting to the customer's own APIs, maintained by Moveo, alongside native Zendesk, Intercom and messaging channels. Through these custom tools the agents take authenticated action in outside systems.

Sourcedocs.moveo.ai Moveo MCP server page, moveo.ai our-plans pageread 2026-09-29

The vendor's documentation states Dialogs provide multi-step workflows guiding users through complex processes, conditional logic creating branching paths based on user input, API integrations connecting to external services via webhooks, and task automation executing specific actions including sending emails and updating databases.

Dialogs are documented as complementing the knowledge and guidelines approach when deterministic structured workflows are required. Agents are documented as proactive and goal-driven, initiating conversations, managing objections and driving toward outcomes such as completing a payment, activating a card or retaining a customer, with handoff to live agents for complex cases.

Sourcedocs.moveo.ai AI Agents overview and Dialogs documentation, moveo.ai product pagesread 2026-08-31

The vendor's documentation states AI Agents operate using a knowledge-based system combining a knowledge base of curated information from various sources with customizable guidelines, answering user queries using retrieval augmented generation.

The Collections knowledge layer accepts data sources including a website re-crawled every 24 hours, a help center, and CSV, PDF or HTML documents, so the corpus tracks its sources on a schedule rather than being loaded once. Past chat logs can be uploaded as training and grounding material. Agents additionally draw real-time customer data from CRM and internal systems for personalization.

Sourcedocs.moveo.ai AI Agents overview and knowledge documentation, moveo.ai product pagesread 2026-08-31

Autonomous payment-recovery campaigns run under a required compliance profile that enforces quiet hours, frequency caps and stop-contact requests, and changes to an AI Agent or knowledge base go to a draft that customers do not see until published. The plans page lists smart escalation and live agent transfer, and simulation criteria test that an agent hands over when a customer asks for a human. Those are constraints, a design-time publish step and agent-initiated escalation. No approval step or pending-action queue in the run path before an agent acts is described.

Sourcedocs.moveo.ai Campaigns overview, Moveo MCP server and Simulations pages, moveo.ai our-plans pageread 2026-09-29

SOC 2 Type II covering security, availability and confidentiality, ISO 27001, and HIPAA compliance with a BAA available are all stated in the documentation, which points to a Trust Center carrying certifications and reports, security practices, data protection measures and penetration test summaries. The same page links Single Sign-On configuration and role-based access control through Permissions, and the MCP server documentation states only Admins and Owners can create API keys and that browser sign-in cannot change account settings, members, billing or keys.

Sourcedocs.moveo.ai Security and Compliance and Moveo MCP server pagesread 2026-09-29

Logs replay production conversations in the administrator view, showing for each turn the predicted intents with their confidence scores and the conversation context including variables and user information, with an AI Agent log view intended for debugging individual agents and filters by channel, coverage, containment, tags and ratings.

That is a per-turn record of the agent's own decisions rather than a transcript alone. The Moveo MCP server can read session transcripts, and the API reference index lists session and log-content endpoints. The logs page does not say whether webhook or tool calls appear in the production log.

Sourcedocs.moveo.ai Logs and Moveo MCP server pagesread 2026-09-29

Conversation context is held as variables and user information through a session, visible per turn in the logs, and simulation criteria can assert on the final session context. The vendor's marketing states memory travels with the customer rather than the ticket and that agents learn from every interaction. No agent-written store that persists across sessions with a defined scope, lifetime or purge path and customer review or deletion is documented.

Sourcedocs.moveo.ai Logs and Simulations pagesread 2026-09-29

Private Deployment on the Enterprise plan, as the plans page lists it, installs Moveo.AI on any cloud such as Google Cloud or in on-premises environments, with a customized data processing agreement and data isolation. The documentation names three hosting regions for accounts, Europe, the United States and Brazil, each with its own service endpoint.

Sourcemoveo.ai our-plans page, docs.moveo.ai Moveo MCP server pageread 2026-09-29

Pre-built templates appear on the plans page as customizable templates for industry-specific use cases, and the AI Agents overview states agents come in types each trained for a specific use case, some with predefined guidelines the customer completes. The campaigns documentation ships two campaign types, Outreach and Payment recovery, the latter with selectable goals such as promise to pay and compliance profiles, each doing its own job independently of the other. How many templates and agent types there are rests on the vendor's description.

Sourcemoveo.ai our-plans page, docs.moveo.ai Campaigns overviewread 2026-09-29

Campaigns can send immediately or be scheduled for a future launch with date, time and timezone, outreach campaigns retry with a fallback when delivery fails and follow up when a contact stays silent, and with autonomous actions enabled the AI Agent chooses channel, message and timing per contact toward a set goal. The scheduled launch and the follow ups fire without a user prompt. Replies across channels route to the AI Agent, and the plans page lists web, SMS, email, WhatsApp, Viber, Facebook, Google Chat, Intercom and Zendesk channels with a custom channel API.

Sourcedocs.moveo.ai Campaigns overview, moveo.ai our-plans pageread 2026-09-29

Customers can connect large language models from external providers, among them OpenAI, Azure OpenAI, Anthropic, Gemini and DeepSeek, by adding a provider under Deploy, Developer Tools, LLMs with their own API key and choosing the model from a dropdown. Connected models are listed with provider, model, creator and last use, and the model strategy guide configures which models power an AI Agent on each channel. The vendor's plans page still markets proprietary large language models, which remain one option among the connected providers.

Sourcedocs.moveo.ai Language Models page, moveo.ai our-plans pageread 2026-09-29

A first party MCP server offers regional endpoints for Europe, the United States and Brazil, browser sign-in or an API key of type Manage sent as documented headers, and about 100 tools covering the platform's own objects: creating, cloning, training, publishing, comparing and rolling back AI Agents, changing guidelines and workflows, managing knowledge bases, environments and routing rules, and running simulations.

The documentation site also carries a REST and analytics API reference, with endpoints for brains, dialogs, collections, campaigns and API keys listed in the vendor's docs index. Both routes let an outside caller drive the platform.

Sourcedocs.moveo.ai Moveo MCP server page and API reference indexread 2026-09-29

Simulations work as regression tests for an AI Agent: the customer writes a scenario and success criteria, a simulated customer plays the scenario through the agent's real production pipeline over chat, email or voice, and an evaluator grades the finished conversation pass or fail with written reasoning. Criteria can assert on tool calls, webhooks fired, handover, fallback responses and final context variables. Runs can be launched singly, in bulk or on a weekday, weekly or monthly schedule, and the Runs tab reports success rate, failures and duration per run. Simulations require a paid plan.

Sourcedocs.moveo.ai Simulations pageread 2026-09-29

Agents answer using retrieval over a knowledge base, and Dialogs handle deterministic requirements through API integrations connecting to external services via webhooks and task automation executing actions such as sending emails and updating databases, all of which are programmatic interfaces. Channels are conversational surfaces including chat, voice, email, SMS, WhatsApp, Messenger and Viber. No browser control, navigation, form filling, screen interaction, desktop automation or interface-level operation of third-party software is documented, and the vendor makes no such claim.

Sourcedocs.moveo.ai AI Agents and Dialogs documentation, moveo.ai home and product pagesread 2026-08-31