DocsGetting started

Quickstart

Build a support agent, connect it to Chatwoot, and ask your first operational question. This takes about 20 minutes end to end.

Updated Nov 2026·12 min read· Tested on v12

Before you start

A Chatwoot account with admin access (Cloud or self-hosted).

A website or help center we can crawl.

Optional: a read-only database replica for reports.

1

Connect Chatwoot

In Tandem, open Integrations → Chatwoot. Enter your Chatwoot URL and an API access token with inbox and conversation scopes. Tandem verifies the token and lists the inboxes you can map.

# Required Chatwoot token scopes
inbox:read
conversation:read
conversation:write
contact:read

Chatwoot remains the canonical inbox. Tandem never deletes a conversation or reassigns one without an explicit agent action.

2

Add a knowledge source

Add a website, help center, or PDF. Tandem crawls, chunks, and indexes the source. A source is only available to agents you bind it to.

SourceRefreshStatus
Help centerDailyIndexed
Product docsWeeklyIndexed
Migration guide (PDF)ManualIndexed
3

Build the agent

Write instructions in plain language. Be explicit about verification, refusal, and escalation. Bind only the sources the agent needs. Choose a fallback for low confidence.

You are Suncoast Support. Answer from the bound sources only.

- Verify account ownership before any billing change.
- Cite the source for every factual claim.
- If confidence is below 0.75, hand off with a summary.
- Never promise a refund timeline beyond the policy.
4

Test and publish

Use the Test tab against a real conversation. Check citations, the fallback path, and the handoff summary. Publishing creates an immutable version; running conversations remain on the version they started with.

5

Ask your first question

Open internal chat and ask a question with a timeframe: “How did revenue look last week compared with the week before, by team?” Tandem resolves it to an approved template and shows the interpreted window before running anything.

Resolved spec
  template   revenue_by_team_range
  timeframe  Nov 3 – Nov 9, 2026
  compare    prior equivalent period
  timezone   America/New_York

[Preview] [Save as report] [Edit spec]

Save the validated answer as a report, then add a schedule and a destination. The spec — not the chart — is what gets stored.

What to check next

Coverage gaps in Analytics → Coverage

Citation failures in Quality

Delivery failures in Schedules

Connection health in Connections

Audit events after each publish

Usage against your plan