Wassist

The vendor's documentation states agents connect to any external API to book appointments, check inventory or process payments, and WhatsMCP is an MCP client connecting and switching between any remote MCP server, which is the vendor's product consuming third-party tools. Named integrations are a native one-line Shopify integration plus Klaviyo, Yotpo and Recharge, which sit within the Shopify commerce stack as a single ecosystem class.

Agents surface native WhatsApp interactive types including buttons, lists, product cards and payments, completing purchases through website checkout within the thread with receipts and shipping updates returning to the same conversation. Whether WhatsMCP is a component of the agent product or a separate offering was not established.

Sourcedocs.wassist.app, wassist.app home, agents and mcp pagesread 2026-08-31

The vendor documents agents holding multi-turn conversations, calling any external API to book appointments, check inventory or process payments, and escalating to the appropriate human team, with a purchase sequenced inside a single thread from browsing through cart, payment, receipt and shipping updates.

No sub-agents, agent-to-agent handoff, branching, looping or conditional construct, visual flow surface, or durable process object outliving a single conversation is documented. Continuity across conversations comes from event triggers such as cart recovery and order updates rather than from orchestration.

Sourcedocs.wassist.app, wassist.app home and agents pagesread 2026-08-31

The vendor documents that an agent is created and grounded from a text description, a website import, uploaded documents, or a connected Shopify store, with the platform generating a first version grounded in the business's own products and content.

Agents answer questions on returns, order updates, sizing and products and make catalog recommendations, and the documentation describes an integrated knowledge base alongside tool integrations. No vector store, embedding model, chunking strategy, re-indexing cadence, retrieval configuration or citation behavior is documented, and the sync model for the Shopify catalog connection is not stated. Brand voice configuration is prompt configuration rather than knowledge.

Sourcedocs.wassist.app, wassist.app home and agents pagesread 2026-08-31

The vendor's documentation states agents answer FAQs, handle inquiries and escalate to humans when needed, handing off to the right team for complex cases. No runtime approval step, checkpoint, pause-for-confirmation, pending-action queue, content policy, topic boundary, spend limit, action allowlist or confidence threshold is documented, even though agents complete payments and call external APIs for actions such as refunds and returns. Where escalations go, and whether a human can take over a live thread, is not stated.

Sourcedocs.wassist.app, wassist.app home and agents pagesread 2026-08-31

The vendor's privacy notice, linked from the site footer, states personal information is protected within commercially acceptable means against loss, theft and unauthorized access, sets out GDPR and UK GDPR disclosures as data controller, and states data is stored or processed in the United Kingdom or where its providers operate.

No certification, attestation, auditor or report is named, and no access model such as roles, permissions, SSO or SCIM appears on the privacy notice, the homepage or the documentation index, which has no security section. GDPR compliance statements are legal cover, not an attestation.

Sourcewassist.app privacy notice and home page, docs.wassist.app documentation indexread 2026-09-29

The vendor's documentation lists analytics alongside templates and business profiles as part of the platform, and conversations with agents are reviewable. No audit log, per-action record identifying which external API was called with what parameters and result, reasoning trace, retention period or export path is documented, even though agents call external APIs for payments, inventory and fulfillment. What the analytics measure is not described.

Sourcedocs.wassist.app, wassist.app home and agents pagesread 2026-08-31

The vendor documents agents following context across a multi-turn conversation, which is state within a session. No memory store, retained per-customer attributes, cross-conversation context object, purchase-history recall, retention configuration or way for an agent to write state in one conversation and read it in another is documented. Brand-voice configuration is the agent's authored definition rather than state the agent writes. WhatsApp threads are themselves persistent and identity-bound, but that is the messaging platform's property rather than a Wassist mechanism.

Sourcedocs.wassist.app, wassist.app home and agents pagesread 2026-08-31

The vendor's documentation describes a hosted platform with three usage paths: a no-code dashboard, programmatic control through the REST API and TypeScript SDK, and connecting an existing agent to WhatsApp using Wassist's infrastructure. No region selection, virtual private cloud, on-premises option, self-hosting path or data localization commitment is documented.

Publishing agents to WhatsApp is a distribution channel, and using the customer's own WhatsApp Business account or a Wassist-provided number is a telephony and account arrangement rather than a deployment option, since messages are processed on Wassist infrastructure either way. The platform depends on Meta's WhatsApp Business Platform for message transport.

Sourcedocs.wassist.app, wassist.app home and pricing pagesread 2026-08-31

The vendor documents templates and a community gallery of agents crafted by other users that can be discovered and used as a starting point, alongside a quick start that generates a working agent from a store URL in under a minute, pre-configured for ecommerce with cart recovery, order updates and product recommendations built in. Full access to templates and business profiles is described as part of the platform. How large the gallery is and how ready its agents are to adopt rest on the vendor's own description.

Sourcedocs.wassist.app, wassist.app home and agents pagesread 2026-08-31

Wassist agents are woken by inbound WhatsApp messages from the business's own customers, reached through footer links, buttons, QR codes and Click-to-WhatsApp ads, and by store events such as abandoned carts and order and delivery updates. The documentation adds signed, retried webhooks delivering real-time WhatsApp events and routing of inbound messages to the customer's own code. A message from the buyer's customers starts the agent without anyone on the business side acting. No schedule and no channel other than WhatsApp is documented.

Sourcedocs.wassist.app Webhooks, Quickstart and Ad Attribution entries, wassist.app home pageread 2026-09-29

The vendor configures the AI automatically, generating a working agent from a store URL, text description, website or documents with no coding and no API keys required, which is advertised as a feature. No model provider is named, and no model picker, bring-your-own-key arrangement, endpoint configuration or routing capability is documented.

The pricing page states each agent message uses one credit and that image generation credits vary by model, which acknowledges multiple models for image generation without documenting selection for the conversational agent. A customer can connect their own existing agent over Wassist's infrastructure and keep full model control, but on that path Wassist is the transport rather than the agent platform.

Sourcedocs.wassist.app, wassist.app home and pricing pagesread 2026-08-31

The vendor's documentation names a fully typed TypeScript SDK with comprehensive REST API documentation, described as the same interfaces used internally, alongside event subscriptions for custom integrations.

Three usage paths are documented: a no-code dashboard, full programmatic control via the REST API and SDK, and connecting an existing external AI agent to WhatsApp using Wassist's infrastructure.

No first-party MCP server exposing Wassist agents to external assistants is documented; WhatsMCP is an MCP client through which Wassist calls remote servers, so it lets the agents use outside tools rather than letting outside assistants call the agents.

Sourcedocs.wassist.app, wassist.app home and mcp pagesread 2026-08-31

The vendor describes the platform's purpose as creating, testing and publishing agents, with creators previewing how an agent responds and refining it before publication, supported by a guided tutorial building a first agent in five minutes. No scoring of outputs, judge, retained test set, expected answers, regression harness or means of comparing one agent version against another on the same inputs is documented, while the agent's grounding is a live Shopify catalog that changes without operator edits.

Sourcedocs.wassist.app, wassist.app home and agents pagesread 2026-08-31

Agents act through WhatsApp message exchange on Meta's Business Platform, calls to any external API, native Shopify and commerce-stack integrations, and remote MCP servers via WhatsMCP, all documented programmatic interfaces.

Purchases complete through the website checkout surfaced to the shopper inside the WhatsApp thread using native WhatsApp payment message types, so the agent presents a payment surface rather than operating one. Website import is one-time content ingestion for grounding.

No browser control, navigation, form filling, screen interaction, visual grounding or desktop automation is documented, and the vendor makes no claim in that territory.

Sourcedocs.wassist.app, wassist.app home, agents and mcp pagesread 2026-08-31