Your AI employee for customer conversations

A chatbot matches a question to an answer. An agent works out what you meant, looks it up in the business's own material, decides whether one of the business's systems could help, calls it if allowed, and then tells you what it did. A chatbot can tell you the returns policy; an agent can check your order against it and start the return.

No. Adding knowledge, writing instructions, setting approval rules and putting the widget on your site are all done through the dashboard. Connecting one of your own APIs needs somebody who knows that API — usually a developer for twenty minutes, once.

Your website, PDFs and documents you upload, individual URLs, plain text you paste in, and FAQ lists you type out. It answers from those and cites which one it used, so you can check it.

It says so and offers to pass the question to a person. It is instructed not to fill gaps with guesses, and every unanswered question is recorded so you can see what to write next.

Yes, for any system with an HTTP API. You describe what the call does and what it needs, and the agent uses it when a conversation calls for it. Read-only lookups usually run automatically; anything that changes something waits for permission.

Every connected action has one of four settings: run automatically, ask the customer to confirm, wait for your team to approve, or switched off. Separately, your staff have roles — a support agent can handle conversations without being able to approve a refund or change what the agent says.

Yes, and today that is the main way to connect anything. You give it a URL, an authentication header and a description. Credentials are encrypted before they are stored and never shown again.

Not as a one-click app yet. All three have public APIs, so you can connect them today using the custom connector — the packaged versions that skip the setup are being built.

Instagram DMs work today, against your own Instagram business account — the agent answers there, your team can reply there, and photos come through in both directions. WhatsApp is built and has not yet carried a live message, so we are not calling it available; email as a channel is in the same position. We would rather tell you that than have you discover it during a trial.

It hands the conversation to your team instead of guessing. The whole thread arrives in a shared inbox, and a colleague replies in the same conversation the customer is already in — no ticket number and no starting again. The customer is told when somebody joins and again when the conversation goes back to the agent, and while a person holds it the agent stops replying, so nobody gets two answers at once.

Yes, on the website widget and on Instagram, and your team can send files back the same way. Each file is identified by its actual contents rather than by its name or what the upload claimed, and anything not on the allow-list is refused rather than stored.

Yes — each client gets a separate workspace with its own knowledge, agents, tools and usage limits, and your team can be in all of them. White-label branding, a single cross-client console and consolidated billing are not built yet.

Every database query is scoped to one workspace, and that isolation is covered by tests written specifically to try to break it. Connected-system credentials are encrypted at rest, and no certification is claimed — if you need a security review, ask and we will go through it properly.

Nothing. The free plan covers one agent with enough messages to judge whether it works on your own material. No card is needed to start.