Build an agent once, rent it to many clients
Build a contained agent that does one specific job well, such as answering for a clinic, a shop or a club. Then rent it to each client for their website, their Canvas pages or their team. Each conversation runs sealed off from the rest of the client's server.
What you get
Shape the agent around one specific job and the knowledge it needs, then reuse that setup for every client in the same line of work.
On the client's website for their visitors, in a chat block on a page of their Canvas theme, or in the app for their team.
Caps per answer, per person or visitor per day, per agent per day and per server per month keep usage inside what you sell. Contained agents run on a separate Anthropic API key added for them.
When a website visitor asks for a person, the conversation shows up as waiting in that server's settings, and a person replies in the same chat.
Each conversation runs in its own sealed space. The agent can read only the knowledge granted to it, write its reply and, on websites, ask for a person.
You decide what you charge each client. CRHQ bills the server, and the model usage runs on the Anthropic API key added for contained agents on that server.
> Visitor: Are you open on Sundays?
> Agent: Yes, from 10:00 to 16:00. Would you like to book a table?
> Visitor: For six people, is that possible?
> Agent: Groups of six or more are booked by our team. I've asked a person to join this chat.
✓ Answered from the client's own knowledge
✓ Group booking handed to a person
For CRHQ clients
Give each client their own server
The cleanest setup is one CRHQ server per client: its own knowledge, caps and conversations. With white label, clients see your brand. One server can also run several website chats, each with its own websites; spending caps belong to each agent, plus one monthly cap for the whole server. With white label, the chat itself is always served from the server's crhq.ai address, even when the client's app uses their own domain.
Build the agent with the client
Agree with the client what the agent may know, turn on Contained in its settings, then grant it a knowledge folder, project documents and approved skills.
Choose where it runs
In the client's app, in a chat block on a Canvas page, or on the client's website with “Anyone can talk to it” and “On websites”. On a website, add one script tag or a plain iframe. The script tag runs on the page with the page's rights; the plain iframe runs nothing on the page.
Hand over and keep improving
Follow the setup guide.
Read conversations together with the client and improve the agent's knowledge over time.
Get more out of it, safely
Agree what the agent may know
The agent only knows what you give it. Treat everything you give it as public: a determined visitor may get the agent to repeat it. Keep the client's private details, passwords, keys and tokens out of its knowledge.
Price on predictable caps
Set caps that match what you sell, so a busy month cannot surprise you or your client.
Make the privacy notice part of the setup
For website chats, your client decides what the chat is for, so their privacy notice should cover it and name the AI model provider (Anthropic) and Cloudflare Turnstile, which sees the visitor's IP address and browser information. Conversations are deleted after 90 days by default.
Show the off switch
Make sure someone at the client knows where the website chat's switch is. Turning it off stops it at once.