Knowledge Bases

Ground your agent in your own content.

How retrieval works

Upload documents in the Knowledge tab. On each turn, the most relevant passages are retrieved and injected into the agent's prompt, so answers are grounded in your content rather than the model's general knowledge.

Tip · Keep documents focused and well-structured — clear headings and short sections retrieve far better than one long wall of text.

Client knowledge portals (white-label)

Agencies and teams managing several clients can let each client maintain their own knowledge — without giving them access to your dashboard. In the Knowledge tab, press Create and choose Client portal to spin one up.

Note · Client portals are included on the Business and Enterprise plans.

Setting one up

  1. Knowledge → Create → Client portal. Name it after the client and pick an access method.
  2. Open the portal, connect the agents it should feed, and customize the branding (logo, name, accent color).
  3. Generate a portal link (or add an email/OTP login) and share it with your client.

Access methods

  • Magic link — a long, single-use-style link (shown once) with optional expiry and instant revocation.
  • Email + password — you provision a login per client user.
  • Email OTP — passwordless; the client gets a one-time code by email.

What the client can do

  • Add, edit, and remove knowledge entries (text, or uploaded PDF / DOCX / text files), organized by category.
  • Connect websites and sync them — manually or on a daily / weekly / monthly schedule — so changes flow into the agent automatically.
  • See full version history and roll any entry back.

Approval workflow

Choose how client changes go live: Publish immediately, or Review before publish — where each change waits in your review queue until you approve it. Either way, every approved change propagates to the connected voice, website, SMS, and workflow agents with no retraining.

Note · Each portal is scoped to one client — cross-client access is impossible. Token hashes and login credentials are stored hashed, and all portal activity is logged.

Custom domain (white-label URL)

Give each portal its own URL (e.g. knowledge.yourclient.com) so clients never see customweb.ai in the address bar.

  1. In the portal's Branding tab, enter the domain in the "Your domain" field and save.
  2. Log in to your DNS provider and add a CNAME record pointing your subdomain (e.g. knowledge.yourclient.com) to your-app.vercel.app.
  3. In the Vercel dashboard for the project, go to Settings → Domains and add the same domain.
  4. Vercel will issue a TLS certificate automatically within a few minutes.
  5. Test by opening the custom URL — the client's branded portal should load.
Important · DNS propagation can take up to 48 hours depending on your provider, though it's usually under 10 minutes.

Notify email

Set a Notify email in the portal Settings to receive an email at your address (not the client's) whenever a client uploads or changes a document. Useful for staying on top of client activity without manually checking the dashboard.

Automation API

Agencies can manage client knowledge programmatically with a standard API key.

curl -H "Authorization: Bearer cwk_…" \
  "https://agents.customweb.ai/api/v1/knowledge?kb=<knowledgeBaseId>"