SERVIIIS CONVERSATION INFRASTRUCTURE

WhatsApp Engine

One transport and routing engine. Two primary commercial conversation roots.

META: NOT_CONNECTED

ROUTE 1

Partner

From informed outreach to relationship, agreement, onboarding and growth.

Agent: Partner Agent

Memory: ai.partner.serviiis.com

Context: Gold Digger · Business Twin · Service AI · proposal · relationship history

WhatsApp → Engine → Partner Agent → Partner Memory → OpenAI/tools → reply

ROUTE 2

Customer

Deal Closer route: qualified buying intent to booking, payment and completion.

Agent: Deal Closer

Memory: ai.customer.serviiis.com

Context: Buyer intent · Service AI · offer truth · commerce state · customer memory

WhatsApp → Engine → Deal Closer → Customer Memory → OpenAI/tools → reply

Buyer Assistant AI remains separate. It handles search, discovery, matching and personalization. When the customer moves into transactional intent, the Deal Closer can take over while both share Customer Intelligence.

ROUTING CORE

Conversation identity & dispatch

Every WhatsApp conversation receives a persistent conversation ID, route, agent, memory source and event history before any model response is generated.

PhoneRouteMessagesStatus

No conversations yet. Routing core is ready for simulation and Meta webhook connection.

META WEBHOOK CONTRACT

Ready, not connected

Verification endpoint: /webhook/meta
Inbound webhook endpoint: POST /webhook/meta
Simulation endpoint: POST /api/simulate/inbound

The engine will not send external WhatsApp messages until Meta credentials and verification are deliberately configured.