01
Inbound Sources
Buyer inquiries can enter through approved portal emails, CRM-connected workflows, or WhatsApp. Conversa normalizes the lead into a customer conversation while preserving the agency's source of truth.
The public integration model is source-agnostic: the customer should not need to learn internal infrastructure.
Lead details are checked against configured agency context before the assistant starts a buyer-facing flow.
Customer-specific routing, authentication, and infrastructure details are kept private.
02
Message Lifecycle
New buyer messages are stored with conversation context so duplicate delivery or retries do not create duplicate AI actions.
Outbound WhatsApp replies are tied to lead state, property context, and handoff rules.
Delivery and read status are used as operational evidence, without exposing provider-specific event names in public docs.
03
Security Boundary
This page intentionally does not list webhook URLs, secret names, internal signatures, queue names, or tenant identifiers. Those belong in private onboarding and runbooks, not public documentation.
Keep reading
Related Docs
Getting Started
Welcome to SME Analytica
A public guide to the SME Analytica suite: Conversa for real estate, Facturia for WhatsApp-first invoicing, MenuFlow for restaurant operations, and consulting for custom agentic business systems.
Real Estate
Conversa Product Guide
How Conversa helps real-estate agencies turn portal and CRM leads into qualified WhatsApp conversations, viewings, and clean human handoffs.
E-Invoicing
Facturia Product Guide
A practical guide to Facturia: WhatsApp-first invoicing, receipt capture, IVA support, and VeriFactu-ready workflows for Spanish autónomos and small businesses.