Home FAQ
AI Employees

FAQ

Quick answers about AI employees, WhatsApp automation, integrations, security, timelines and pricing.

Frequently asked questions

Everything you need to know

If you don’t see your question, send us a message and we’ll respond with a clear recommendation.

Ask a question
Is this just a chatbot?
No, we build AI employees that follow workflows, capture structured data, and can trigger actions in your systems. They also escalate to humans when needed.
Can it work on WhatsApp?
Yes. We can deploy WhatsApp-first experiences for customer support, sales, notifications and document exchange, with a clear handover path to your team.
Which channels are supported?
Common rollouts include WhatsApp, webchat, Telegram, websites and email. We can also support internal channels like Teams/Slack for approvals and workflows, depending on your environment.
Can it integrate with our CRM / ticketing / ERP?
Yes. We integrate via APIs, webhooks and databases. We’ll start with one integration in the pilot (e.g., ticket creation or CRM lead capture) and expand from there.
How do you keep it safe and accurate?
We use guardrails: validation rules, required fields, escalation triggers and knowledge grounding (RAG). For sensitive workflows, we add approvals before messages/actions are executed.
How does human handover work?
When the AI detects uncertainty, exceptions or high-risk requests, it escalates to a human with a summary, extracted fields and a recommended next step, while preserving conversation context.
How long does a pilot take?
A typical pilot is delivered in a few weeks depending on scope and integration complexity. We’ll agree on milestones: workflow mapping → build → testing → launch → measurement.
How does pricing work?
Pricing depends on channels, message volume, number of workflows and integrations. Many teams start with a fixed-scope pilot and then move to an ongoing plan once value is proven.
Where is data stored?
Data handling depends on deployment. We minimise retention, enforce access controls, and document how data flows through integrations. See our Data Privacy page for details.

Still unsure?

Tell us one workflow and one channel and we’ll recommend the simplest pilot approach.