You connect your own account
WhatsApp Business through Meta's cloud API, Telegram through a bot you create. The credentials are yours, stored encrypted, and you can disconnect at any time.
Integrations
Your channels, your accounts, your data.
Blivo connects to the channels your customers already use. Connections run through your own provider accounts, so your numbers, your history, and your customer relationships stay yours. This page shows the true status of every integration, without decoration.
How connections work
Blivo verifies before it claims
Every connection is validated against the provider before it's marked as working. If validation fails, the platform says so; it never shows a green light that didn't happen.
Messages flow both ways
Customers write on the channel; your AI employees reply from the company's knowledge. People can step into any conversation, and the customer never knows the difference.
Your data never leaks sideways
Integration credentials are encrypted with a per-deployment key. Conversations stay attached to your company's records, isolated from every other company.
Every integration, honestly labeled
Every integration, honestly labeled
Four states, plainly defined. Anything not on this list isn't integrated at all.
AvailableWorking today. Connect your provider account and use it.
In developmentBeing built now. Not usable in production yet.
Coming soonPlanned and scheduled, but work hasn't started.
Not supportedWe have no honest implementation to offer. We won't fake one.
WhatsApp (Meta Cloud API)
AvailableFull two-way conversations through your WhatsApp Business account on Meta's cloud API. Voice notes and media are handled like any customer message.
Telegram
AvailableA Telegram bot you create and own, connected in minutes. Two-way conversations with full history in Blivo.
Webhooks (outbound)
AvailableBlivo can notify your other systems when things happen, with cryptographically signed requests you can verify.
REST API
AvailableThe same API our own application uses, documented with OpenAPI. Your integrations get the same data, under the same permissions.
Email is built into the platform and activates when the platform's email account is configured for your deployment. Until then, the platform shows email as not configured instead of pretending.
Instagram & Facebook
Coming soonCustomer identities from these networks are already recognized in the platform. Live message delivery is on the roadmap.
SMS
Not supportedNo SMS provider has a contract with this deployment, so SMS is honestly marked not supported. It will appear here the day it works.
Phone & SIP
Not supportedTelephony is a different kind of integration and isn't supported. We won't list it as available until it truly is.
Payment providers
Not supportedPayments in Blivo are recorded and reconciled by your team today. Automated payment processing is not integrated.
For your developers
For your developers
Blivo exposes a complete REST API with OpenAPI documentation and signed webhooks. The same API the platform's own applications use.
- Full OpenAPI specification, generated from the live service
- Signed webhooks with rotating secrets
- Your API access follows your account's permissions, exactly
- Rate limits protect the platform, and responses say when you hit them