Route conversations to the right account, Agent, or person based on market, sales owner, customer stage, or business role.
A Chat API for Building Agents on WhatsApp Personal-Account Matrices
SocialEpoch Chat API connects WhatsApp personal-account matrices. It is different from Meta's official WhatsApp Business Platform Cloud API, often referred to as the WABA API. Agent builders, product teams, and technology partners can use it to connect multi-account conversations, customer context, and human handoff with their own applications.
- WhatsApp personal-account matrix
- Conversation and customer context
- Agent collaboration and human handoff
From personal-account conversations to Agent appsSocialEpoch Chat API
Personal-account matrix
Multiple WhatsApp personal accounts
SocialEpochChat APIConversations · Customers · Events
Application layer
SalesAgentIndustry AgentsCRM / Internal Apps
Choose the Right API Before Designing the System
SocialEpoch Chat API and the official WhatsApp Business Platform Cloud API are different technical routes. SocialEpoch connects WhatsApp personal-account matrices and supports both one-to-one and group API calls; WABA is Meta's official business messaging infrastructure.
01One-to-One API
Connect personal-account conversations for sales, long-term follow-up, and customer service.
02WhatsApp Group API
Connect group conversations so Agents, community operations, and business systems can work together.
03Agent-Human Collaboration
Coordinate automation, reminders, suggestions, and human handoff with continuous customer context.
| Dimension | SocialEpochWhatsApp Personal-Account Matrix | Official MetaWhatsApp Business Platform (Cloud API / WABA) |
|---|---|---|
| Foundation & Account Type | Connects personal accounts on WhatsApp Messenger App / WhatsApp Business App and organizes multiple accounts into a managed matrix. | Connects business phone numbers and related assets on the WhatsApp Business Platform, subject to Meta onboarding and review requirements. |
| Core Scenarios | Proactive sales, long-term customer follow-up, customer retention, and Agent-human collaboration. | Official notifications, customer service, authentication, structured business messaging, and service at scale. |
| Conversation Types | Supports API calls for both one-to-one conversations and WhatsApp groups. | The standard Cloud API is primarily built around business-to-user messaging. Meta Groups API is available to eligible accounts and remains subject to Meta's access and product limits. |
| Messaging Capability | Can support personalized sales outreach and continued follow-up through personal-account workflows. Account use, outreach cadence, consent, and data processing must follow WhatsApp rules and applicable market requirements. | Business-initiated messages use approved templates; free-form replies are allowed within the 24-hour customer service window after the user's last message. |
| Customer Connection | Can combine lead imports, customer records, and personal-account conversations into a continuous follow-up workflow. Exact capability depends on the API documentation. | Communicates through official business messaging; outreach, pricing, and consent follow Meta's current rules. |
| Account Management | Connects, assigns, and routes multiple personal accounts as a matrix for teams and Agents. | Centers on business phone numbers and WABA assets managed through Meta's official tools and APIs. |
| Data & Context | Uses accounts, customer records, conversation history, tags, and customer journeys as continuous context for Agents and business workflows. | Exposes messaging, template, status, and business-phone-number data through official APIs and webhooks; exact fields follow Meta documentation. |
| WhatsApp Groups | Can call group capabilities within the confirmed interface scope for group-conversation Agents, community service, group replies, and business-system coordination. | Official Groups API is not a default capability for every WABA account. Availability and limits must be confirmed against current Meta documentation and account eligibility. |
| Agent Design | Design around real conversation context, account roles, customer journeys, group scenarios, and human handoff. | Design around message templates, service windows, webhooks, Flows, and official business messaging rules. |
| Best Fit | Agent studios, sales-tech teams, cross-border service providers, and companies already operating personal-account matrices. | Brands and platforms that need official business messaging infrastructure, notifications, and customer-service automation. |
| Can They Coexist? | Yes. WABA can handle official notifications and service, while personal-account matrices can support sales follow-up, group scenarios, and customer relationship operations. | |
For official WABA capabilities and rules, refer to Meta's WhatsApp Business Platform developer resources, the Meta Groups API documentation, and the WhatsApp Business Messaging Policy. Before integration, we confirm available accounts, fields, events, and group capabilities with your team.
A Conversation Layer Designed for Agent Builders
A personal-account matrix lets an Agent work beyond a single message. With clear permissions and human-handoff rules, it can understand the customer journey, assist follow-up, and connect actions with business systems.
Use customer profiles, conversation history, tags, and follow-up status as context for Agent decisions and reply suggestions.
Let Agents organize, remind, and suggest while people review pricing, commitments, sensitive replies, and key deal actions.
Combine the Chat API with models, knowledge bases, CRM, tickets, workflows, and internal applications.
Agent Applications You Can Explore on a Personal-Account Matrix
Start with one of these Agent scenarios, then define the delivery scope around account access, data permissions, and human-handoff rules.
Organize inquiries, complete customer records, suggest next steps, and remind sales reps to move opportunities forward.
Use product materials, FAQs, and industry knowledge to assist technical answers and identify conversations that need an expert.
Assist intent understanding, reply suggestions, and conversation summaries across markets and languages.
Use customer stages, order history, and service records to assist reactivation, repurchase, and after-sales follow-up.
Support distributors, resellers, and service partners with content retrieval, policy Q&A, lead handoff, and progress reminders.
Route online inquiries to the right store or advisor and assist booking, requirement capture, and human continuation.
Compose the Stack from Connection to Agent Application
The Chat API provides the personal-account-matrix connection layer. SocialEpoch products and ecosystem capabilities serve different builders and users above it.
Connect WhatsApp personal-account matrices, conversations, customer context, and events.
Help technical teams aggregate and manage access to large language models.
Automated replies, reminders, suggestions, and human handoff for sales teams.
Explore and experience industry Agent applications built on SocialEpoch capabilities.
Confirm Accounts, Data, Actions, and Human Handoff
Before integration, we confirm the available fields, events, messaging capabilities, and account scope with your team.
Confirm account quantity, teams, markets, roles, and how conversations should be assigned.
Confirm which events, customer fields, tags, and follow-up states need to be read, synchronized, or stored.
Confirm the models, knowledge bases, company tools, action permissions, and quality measures used by the Agent.
Confirm which actions can run automatically, which require review, and how exceptions should be escalated.
Start with One Real Scenario and Build a Four-Step Pilot
Define the business action and technical route first, then validate interface capability. Customer data, automated actions, and AI suggestions need clear permissions, human review, and exception handling.
- 01
Select the Business Scenario
Clarify customer sources, account matrix, Agent task, human roles, and the workflow you want to improve.
- 02
Define Technical and Data Boundaries
Confirm events, fields, system connections, action permissions, WhatsApp rules, and applicable market requirements.
- 03
Build a Small Pilot
Use a limited set of accounts and one team to validate the conversation path, Agent quality, human handoff, and exception handling.
- 04
Evaluate Before Expanding
Use pilot results to decide whether to add accounts, Agents, markets, and systems, then establish ongoing evaluation.
Bring One Agent Scenario to an API Integration Discussion
Share your account quantity, customer sources, Agent task, existing systems, and human-handoff design. We will identify the technical route before defining a pilot.