Vivollo
Demo

Unified Inbox

Every channel. One brain.

WhatsApp, Instagram, Messenger, your website, your help desk — Vivollo unifies them into one agent and one inbox, with the customer's context following them everywhere.

Request a demo
Unified inboxlive
WhatsApp
Instagram
Messenger
Web
Connexease

One customer, every channel — context follows.

One inbox. The thread, the customer, the tools — on one screen.

The Vivollo inbox: a web-chat conversation with product cards, the conversation list and the details rail
Messages · a web-chat thread with the product cards the assistant sent, and the customer's session on the right.

01Channels

Wherever they write, it is the same assistant.

WhatsApp, Instagram, Messenger, your website and your help desk connect to one assistant with one memory. A channel is a setting, not a separate build.

  • WhatsApp

    Through Gupshup or the Cloud API; templates and media included.

  • Instagram

    DMs and comments, with the 24-hour window handled for you.

  • Web and help desk

    The chat widget on your site; Connexease, Grispi and Zendesk on the desk side.

The Channels list: Instagram, web chat and WhatsApp, each connected to a flow

02Store

It reads your store as it is right now.

Stock, order status, shipping, returns — from the store, live. Whatever you run beside it connects over REST and webhooks; nothing has to be migrated.

The Integrations list with connected stores

Connected stores

Shopify, WooCommerce, Ticimax and Trendyol, with what each one lets the assistant do.

stock
live
orders
status + tracking
returns
policy + window
customers
by phone or email

What it reads

Live, from the store — never from a copy.

key
ws_live_••••
scope
read + write
webhook signature
HMAC

REST API

Keys per workspace; call your own systems from a flow.

message.received
on
conversation.resolved
on
handoff.requested
on

Webhooks

Events your systems can subscribe to.

Connexease
assign + sync
Grispi
tickets
Zendesk
tickets

Help desks

Two-way with the desks your team already uses.

03Context

The customer switches channel. The conversation doesn't.

Yesterday on Instagram, today on WhatsApp — one person, one thread. The assistant matches them by phone or email and picks up where it left off.

FIG 3Panel · MessagesWhat the customer saw · WhatsApp
The details rail of a conversation: session, activity and other conversations
Unified inbox
I wrote on Instagram yesterday — did the 38 come back in stock?load_context · instagram→1 conversation · yesterdayYes — the black stiletto you asked about is back in 38. Want me to hold a pair?Continued from Instagram
One identity
Matched by phone or email across channels and to the store's customer record.
Other conversations
The rail lists the customer's earlier threads on every channel.
Same memory
Size, address, language — learned once, used everywhere.

Proof of control

One conversation, two channels, one thread.

The customer asked on Instagram, then again on WhatsApp. The assistant matched the contact, loaded yesterday's thread and answered — and when Instagram's 24-hour window had closed, it sent the reply on WhatsApp instead.

  1. 1identify_contact60 msInputphone · +90 5•• ••• 42 18matched · Instagram @elif.k
  2. 2load_context90 msInputinstagram · 1 threadyesterday · 'black stiletto 38'
  3. 3check_stock210 msInputSKU-4471 · 386 in stock
  4. 4send_message30 msInputinstagram24-hour window closed
  5. 5send_message410 msInputwhatsappdelivered · 1 thread
Example conversation; latencies are illustrative.

Connected channels and stores

All integrations
  • WhatsApp
  • Instagram
  • Messenger
  • Web widget
  • ConnexeaseConnexease
  • GrispiGrispi
  • Shopify
  • TrendyolTrendyol

Ready to meet your AI agent?

Book a demo and we'll build a working agent on your real data — across WhatsApp, Instagram and your website. Live in days.

Request a demo