// live chat for agencies

Live chat built
for agencies.

Multi-site from one dashboard — one account, every client's site.

Why generic live chat fails agencies

Most chat tools assume one company, one widget, one inbox. Agencies juggle 5–50 client sites — each with its own brand, AI persona, knowledge base, and (often) its own team. Installing a separate chat tool per client means separate logins, separate billing, separate dashboards. Generic live chat doesn't fit the agency workflow.

What Agentbot does differently

Unlimited sites per account

One Agentbot account hosts every client site. Each gets its own widget snippet, brand color, header copy, AI persona, knowledge base, availability schedule — all configured separately. Switch between sites from the sidebar.

Per-client team access

Invite the client's in-house team to their site's inbox (and only their site's inbox). They get to take over conversations, mark tickets, and reply alongside the AI without seeing other clients' data. Your agency team has access across all sites.

Webhooks let you white-label downstream

Pipe every conversation, message, and ticket event into the client's existing CRM, Slack, or HubSpot via signed webhooks. The agency owns the chat layer; the client's existing tools stay the source of truth for contacts and tickets.

Install in 60 seconds

Drop one line of script into your site head. The widget is live immediately; the AI starts answering once you upload your knowledge base. Full install docs →

<script src="agenbot.vercel.app/w/YOUR_SITE_KEY" defer></script>

Flows the AI handles out of the box

  • Project status questions — AI pulls from the client docs you uploaded
  • Scope / pricing questions on the client site — AI answers from the client-specific knowledge base
  • New-lead intake — AI captures name, email, project brief and files a ticket
  • Routing — webhook fires to the client team's Slack the second a human is needed
  • Multi-language — AI handles whatever language the visitor writes in

Built for the tools agencies already uses

FAQ

How many client sites can I host on one Agentbot account?

Unlimited during open beta. The dashboard is built around a site picker — switch between client sites with one click, each with its own settings, conversations, and knowledge base. When paid lands, the agency model is the assumed shape; we will not gate site count behind a per-site fee.

Can I give my client access to just their site?

Yes. Invite the client (or their team) to a specific site as an agent or owner; they see only that site's inbox, tickets, and settings. Your agency team retains cross-site access.

Can I white-label the widget so it doesn't show 'Agentbot'?

The visitor-facing widget already ships with no 'Powered by' banner on every tier — including free. The dashboard itself is the Agentbot UI; full white-label dashboard skinning is on the roadmap (a paid-tier feature when it lands).

How does billing work if I install on a client's site?

Agentbot is free during beta — there is no billing yet. Post-beta, the planned model is per-account (the agency account) rather than per-site or per-seat, so you can install on 20 client sites without 20× the bill. If a client wants to take over billing later, the site can be migrated to their own Agentbot account.

Do I have to set up the AI persona separately for each client?

Yes — and that is the point. Each client gets their own brand voice, persona name, and knowledge base. A site for a law firm should not have the same AI tone as a site for a SaaS startup. Configuration is 5 minutes per site.

What if a client wants to move off Agentbot — is their data exportable?

Yes. Every site's conversations, tickets, and knowledge base uploads are exportable from the dashboard. The widget is one script tag — removing it cleanly detaches the integration. No lock-in for you or the client.

Try Agentbot — free during beta.

One <script> tag. No credit card. See pricing.

Get Agentbot — Free →

Also for: SaaS · Startups