Teach it your business logic.
A chatbot answers questions. Give yours skills and it starts doing things — checking an order, booking a slot, calling your API — then wire those skills into workflows that run the moment an event lands.
No credit card required · 7-day free trial

“Where’s my order?”
Find the customer’s order in your system and return its delivery status.
Skills that act. Workflows that run them.
Install ready-made skills or write your own, then let events kick off workflows that use them, all inside a sandbox you control.
If this happens, do that. Workflows start from an event, then branch, wait and act, with your skills as steps.
Skill Sets, ready made. Install a set, add your key, and your agent can use it.
Two kinds of skill. Look things up safely, or create, update and book.
One trigger, many paths. Start from inbox events or any incoming webhook.
Plain language first. Code when you need it. Describe when to use it, then write the handler.
On a short leash. Skills run in a sandbox, and keys stay masked secrets.
Automation that earns its keep.
Cloodot’s AI now handles the flood of WhatsApp queries across our stores and routes only what needs a person to the team. Faster replies, more sales, fewer agents on the clock.
Akhil · MyG
Skills & workflows, answered.
What's the difference between a skill and a workflow?
Do I have to write code?
How do skills reach my own systems?
Is it safe to give a skill my API keys?
What can trigger a workflow?
Try the whole thing, today.
Start free. Connect a channel, train an agent on your own content, and you'll have a working deployment in your inbox the same afternoon.
