Spoki vs Wassist (2026)

More than 100 native integrations include Shopify, WooCommerce, HubSpot and Salesforce, with thousands more reachable through Zapier, Make and n8n, and a public REST API with signed webhooks covers anything else. The agent writes into commerce systems with authenticated actions instead of only looking things up. Product catalogs sync into the chat, checkout completes in the conversation, and cart recovery and payment confirmation events flow both ways between the store and the agent. Spoki Voice adds telephony, dialing out and booking appointments.

Sourcespoki.com/en/featuresread 2026-09-05

Agents connect to any external API to book appointments, check inventory or process payments. WhatsMCP is an MCP client that connects to and switches between any remote MCP server, so the product can use third party tools. Named integrations are a native Shopify integration that takes one line of code, plus Klaviyo, Yotpo and Recharge, all within the Shopify commerce stack.

Agents use native WhatsApp interactive types, including buttons, lists, product cards and payments. Purchases complete through website checkout within the thread, and receipts and shipping updates return to the same conversation. Wassist does not say whether WhatsMCP is part of the agent product or a separate offering.

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

Orchestration runs on two layers, one deterministic and one agentic. The visual drag and drop flow builder and automation engine sequence multi step journeys on event triggers such as cart abandonment and payment confirmation, with conditional logic branching the path and A/B variants running inside it. Above that sit two AI layers, both generally available.

Language models handle conversation, and autonomous agents take actions, handling complex multi turn conversations, qualifying leads and completing commerce journeys from catalog through checkout. Spoki Voice extends the same orchestration to telephony. Its predictive power dialer calls, qualifies and books an appointment and then continues the thread on WhatsApp, so one journey crosses channels without restarting.

Sourcespoki.com/en/featuresread 2026-09-05

Agents hold multi turn conversations, call any external API to book appointments, check inventory or process payments, and escalate to the appropriate human team. A purchase runs inside a single thread, from browsing through cart, payment, receipt and shipping updates. Wassist names no sub agents, agent to agent handoff, branching, looping or conditional construct, visual flow surface, or durable process that outlives a single conversation. Event triggers such as cart recovery and order updates carry work from one conversation to the next.

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

One inbox gathers WhatsApp on the official Meta Business API, Spoki Voice AI, Email, SMS and RCS, with Instagram and TikTok alongside. Spoki uses the WhatsApp Business API, not the mobile Business App, and only the API supports programmatic automation at volume. Work starts in three ways.

Conversations come in on any channel, the automation engine fires on cart abandonment, payment confirmation and similar commerce events, and outbound work runs through broadcast marketing campaigns and the Spoki Voice predictive power dialer, which places calls, qualifies prospects and books appointments. Spoki reports 15.3 million messages a month across 4,500 businesses in 120 countries.

Sourcespoki.com/en/identikitread 2026-09-05

Inbound WhatsApp messages from the business's own customers start the agents, with no one on the business side having to act. Customers reach the agents through footer links, buttons, QR codes and Click-to-WhatsApp ads. Store events such as abandoned carts and order and delivery updates also start work. Signed, retried webhooks deliver real time WhatsApp events and route inbound messages to the customer's own code. Wassist names no schedule and no channel other than WhatsApp.

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

Agents are trained on the customer's product catalog, so they answer product questions, recommend items and complete a purchase from live inventory. Intent detection, sentiment analysis, auto replies, template generation and auto translation sit on top. There is no document knowledge base, website crawl, help center ingestion, retrieval architecture or source citation, so a support question that is not about an order or a product has no corpus behind it.

Sourcespoki.com/en/identikitread 2026-09-05

An agent is created and grounded from a text description, a website import, uploaded documents or a connected Shopify store, and the platform generates 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.

An integrated knowledge base sits alongside tool integrations. Wassist names no vector store, embedding model, chunking strategy, reindexing cadence or retrieval configuration, and does not say whether answers cite their sources or how the Shopify catalog connection syncs. Brand voice is set in the agent's prompt configuration.

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

The conversational CRM holds one customer record and one conversation thread across every channel, with deal pipelines, tickets and full interaction history. An agent picking up a returning contact on WhatsApp sees what happened on the previous call or campaign, so the customer does not repeat themselves. The business loads, segments and queries the CRM as a database. There is no separate memory product, and the agent keeps nothing of its own between conversations.

Sourcespoki.com/en/featuresread 2026-09-05

Agents follow context across a multi turn conversation within a session. Wassist names no memory store, retained attributes for each customer, context that carries across conversations, recall of purchase history or retention setting, and no way for an agent to write state in one conversation and read it in another. Brand voice is part of the agent's authored definition. WhatsApp threads themselves persist and are tied to each user's identity on WhatsApp.

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

Conversations can pass from the bot to a person, but customers cannot control what the agent does before that. Bot to human handoff feeds a shared inbox where several operators and the AI work the same conversation thread. Routing rules decide where a conversation lands, and supervisor roles govern which people see and do what.

Every plan has unlimited operators, so escalation is not limited by license cost. Customers can author when a bot stops through the visual flow builder and its conditional logic. There is no guardrail configuration, content policy, approval gate or autonomy setting for the agent itself.

Sourcespoki.com/en/featuresread 2026-09-05

Agents answer FAQs, handle inquiries and escalate to humans when needed, handing complex cases to the right team. They also complete payments and call external APIs for actions such as refunds and returns. Wassist names no runtime approval step, checkpoint, pause for confirmation, queue of pending actions, content policy, topic boundary, spend limit, action allowlist or confidence threshold. It does not say where escalations go or whether a human can take over a live thread.

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

Access is role based, with operator and supervisor roles in the shared inbox. Webhooks are signed, data handling is GDPR native with EU data residency, and Spoki holds Official Meta Tech Partner status with certified WhatsApp Business API access. Spoki holds no security certification or attestation. There is no SOC 2, no ISO 27001, no trust center and no report to request. Meta Tech Partner and Business Solution Provider status is a commercial accreditation for API access from Meta's program, not an audit of Spoki's own controls.

Sourcespoki.com/en/identikitread 2026-09-05

Personal information is protected within commercially acceptable means against loss, theft and unauthorized access. Wassist makes GDPR and UK GDPR disclosures as data controller, and data is stored or processed in the United Kingdom or where its providers operate. Wassist names no certification, attestation, auditor or report, and no access model such as roles, permissions, SSO or SCIM.

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

Real time dashboards show campaign analytics and revenue per conversation attribution, so a team can see what the platform earned and where. Spoki calls both AI layers, the conversational models and the autonomous agents, observable and generally available, but does not say what that covers. There is no reasoning trace per conversation, no tool call log, no source attribution on an answer and no audit trail of configuration changes.

Sourcespoki.com/en/identikitread 2026-09-05

Analytics come with the platform alongside templates and business profiles, and conversations with agents can be reviewed. Agents call external APIs for payments, inventory and fulfillment, but Wassist names no audit log, no record of which external API each action called with what parameters and result, and no reasoning trace, retention period or export path. It does not say what the analytics measure.

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

Data stays in the EU, with GDPR native handling and European data residency as a headline commitment. Spoki positions itself as the European alternative to US WhatsApp platforms. There is one region and nothing for the customer to select. Spoki names no data center, offers no other region and no self hosted or private cloud option, and publishes no DPA or subprocessor list.

Sourcespoki.com/en/identikitread 2026-09-05

The platform is hosted and has three usage paths. Customers can work in a no code dashboard, control it programmatically through the REST API and TypeScript SDK, or connect an existing agent to WhatsApp using Wassist's infrastructure.

No region selection, virtual private cloud, on premises option, self hosted path or data localization commitment is published. Agents are published to WhatsApp on the customer's own WhatsApp Business account or a number Wassist provides, and 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

Spoki ships AI agent types for sales, support and voice, plus a custom option. The visual builder adds message templates and reusable flow templates. WhatsApp requires outbound templates to be approved in advance, so template management is a core part of the product. There is no catalog of agents for a customer to browse and put into service.

Sourcespoki.com/en/featuresread 2026-09-05

Templates and a community gallery of agents crafted by other users can be discovered and used as a starting point. A quick start generates a working agent from a store URL in under a minute, preconfigured for ecommerce with cart recovery, order updates and product recommendations built in. The platform includes full access to templates and business profiles.

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

Customers get no model selector, routing configuration or way to bring their own key, and no provider is named. Spoki has two AI layers, language models for conversation and autonomous agents that take actions, without saying whose models sit underneath either. The product is sold as a managed outcome, measured in open rates, recovery rates and attributed revenue, not as a configurable runtime.

Sourcespoki.com/en/identikitread 2026-09-05

The AI is configured automatically, and a working agent is generated from a store URL, text description, website or documents with no coding and no API keys required. Wassist names no model provider, and no model picker, bring your own key arrangement, endpoint configuration or routing. Each agent message uses one credit, and image generation credits vary by model. A customer can connect their own existing agent over Wassist's infrastructure and keep full model control, with Wassist serving as the transport.

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

Outside systems can call Spoki through a public REST API with signed webhooks. The API documentation is public as a Postman collection at a named URL, so an integrator can read the endpoints without a sales conversation. Spoki also supports MCP and WebMCP for AI agents, exposing ten tools at /api/webmcp so an external AI agent such as ChatGPT, Claude or Cursor can operate Spoki directly. Around these sit 100+ native integrations plus thousands more through Zapier, Make and n8n.

Sourcespoki.com/en/identikitread 2026-09-05

A fully typed TypeScript SDK and comprehensive REST API documentation expose the same interfaces Wassist uses internally, alongside event subscriptions for custom integrations. Customers have three usage paths. They can work in a no code dashboard, take full programmatic control through the REST API and SDK, or connect an existing external AI agent to WhatsApp using Wassist's infrastructure. Wassist names no MCP server of its own that exposes its agents to outside assistants. WhatsMCP is an MCP client through which Wassist calls remote servers, so it lets the agents use outside tools.

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

Testing covers campaigns, not agents. A/B tests run on message variants inside flows, and predictive send time optimization picks when to send, with real time dashboards and revenue per conversation attribution reading the result. A marketer can show one message outperformed another on a readable number. There is no simulation, staging environment, scenario suite, regression run or scored evaluation of an agent before it goes live.

Sourcespoki.com/en/featuresread 2026-09-05

The platform is built for creating, testing and publishing agents. Creators preview how an agent responds and refine it before publication, and a guided tutorial builds a first agent in five minutes. Wassist names no scoring of outputs, judge, retained test set, expected answers or regression harness, and no way to compare one agent version against another on the same inputs. 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 programmatic routes, with no browser control, hosted session or interface automation. Those routes are 100+ native integrations, a public REST API with signed webhooks, and catalog and checkout flows that write into the customer's commerce platform, reaching people over WhatsApp, Voice, Email, SMS, RCS, Instagram and TikTok. The WebMCP endpoint works the other way round. Its ten tools let an external AI browser agent operate Spoki, so another company's agent drives Spoki, and Spoki's own agent drives no interface.

Sourcespoki.com/en/identikitread 2026-09-05

Agents act through WhatsApp messages on Meta's Business Platform, calls to any external API, native Shopify and commerce stack integrations, and remote MCP servers through WhatsMCP, all programmatic interfaces. Purchases complete through the website checkout, which the agent shows the shopper inside the WhatsApp thread using native WhatsApp payment message types. Website import is a one time content ingestion for grounding. Wassist makes no claim of browser control, navigation, form filling, screen interaction, visual grounding or desktop automation.

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