One team, every channel
Connect several agents to the same flow. One is the default; the rest take over their domain the moment the conversation calls for it — without ever losing context.
Sales, Workshop, Billing… each agent is a specialist. When the request belongs to someone else, it hands the conversation off automatically — same chat, no restart.
Every person gets their own session with a rolling summary and long-term memory. The agent remembers their name, company and preferences across visits and channels.
Before returning invoices or order status, require the customer to verify their email with a one-time code — using your branded email template.
Agents query your DataStores and reply with real records, scoped to the verified customer. No hallucinated invoices, no wrong data.
The agent is the conversational front-end of your automation. Through skills, tools and workflows it can act across your entire Floogos — not just chat.
The agent activates the right capability for each request — Billing, Support, Sales — each with its own instructions and tools.
Each skill runs real actions: any of the 600+ Floogos nodes — CRM, ERP, databases, payments, email and more.
Or it launches a whole flow and returns the result: issue an e-invoice, create a ticket, run an onboarding.
The agent reaches everything in your stack
The default agent (e.g. Sales) picks up the first message.
They ask about an invoice — out of Sales' scope.
Sales hands the chat to Billing, which knows its job.
Billing verifies the email by OTP and returns the real invoice.
Route questions to the right specialist, answer from your knowledge base, and escalate to a human only when needed.
Answer pricing and availability, qualify the lead and capture contact details straight into your CRM.
Give account holders their invoices and order status safely, gated behind email verification.
Handle repairs, appointments and follow-ups with an agent that remembers the whole history.
Hand-off is decided by each agent's purpose. You describe what it does — Floogos routes the conversation.
Verified tools filter to the customer's own records. One user never sees another's data.
Each agent can run on OpenAI, Claude, Gemini, Mistral or a local model. Use the right brain per role.
Publish a public URL, drop the embed on your site, or connect Telegram and WhatsApp from the same flow.
Get a public chat URL, a floating widget for WordPress or your store, and an iframe — all from the chat trigger. Rename or regenerate the token whenever you need.
A shareable link, ready to open in any browser.
A single <script> adds a chat button to any HTML page.
Embed the chat as a panel inside an existing page.
What is a multi-agent system?
A set of specialized AI agents (e.g. sales, support and admin) that share one conversation and hand it off to each other based on what the customer needs, without them repeating anything.
How is a conversation handed off between agents?
An entry agent handles the first message and, if the topic belongs to another specialty, hands off to the right agent carrying the transcript and context. The customer stays in the same chat.
Which channels does it support?
The same agent serves on Web, Telegram, WhatsApp and Instagram, with continuous memory across channels.
How does it protect customer data?
With OTP identity verification before exposing sensitive data, granting access only to the authenticated customer's data and logging every query.
Can it transfer the conversation to a person?
Yes. A human can step in at any time with all the context in front of them, whether to supervise or to resolve handed-off cases.
Which AI models can be used?
Floogos is multi-provider: you can use different language models per agent and per need, including the option of local models.
How do you embed the chat on a website?
From the chat trigger you get a public URL, a floating widget for your site or store, and an iframe. You can rename or regenerate the token whenever you need.
Build your multi-agent chat today. No code required.