Your customers don't pick one channel. Neither does the agent.
One ZINQ agent runs on WhatsApp, Instagram DMs, web chat, Telegram and email — same memory, same workflows. Enquire on Instagram, book on WhatsApp, get follow-ups by email: one conversation.
The launch channel set
WhatsApp — the lead channel
An AI agent on the official WhatsApp Business API, live in production today, with Meta's per-message cost passed through at cost. For most businesses, this is where customers already are.
Instagram DM
Where a lot of enquiries actually start. The agent answers, qualifies and books straight from the DM — no more unread pile while your team is busy.
Web chat
The agent on your own site, with the same knowledge and booking skills — not a separate widget bot with a separate brain.
Slower-paced but still the agent: enquiry replies, booking confirmations and follow-up sequences that thread into the same conversation history.
Telegram
Supported for the businesses whose customers live there — the same agent, one more door.
Phone
The same agent takes customer calls too — answering, qualifying and connecting outcomes to your workflows and your team.
Why one agent across channels beats one bot per channel
One identity
The same person on Instagram and WhatsApp resolves to one contact — the agent never asks a returning customer who they are.
One memory
Context carries across channels: the question asked on web chat informs the WhatsApp follow-up.
One playbook
Skills, knowledge and workflows are configured once and run everywhere — no per-channel re-wiring.
One inbox for your team
Handoffs from every channel land in the same place, with the full cross-channel history attached.
See one conversation travel across channels.
The demo runs a real scenario — enquiry on one channel, booking on another, follow-up on a third.
Book a demo