Quickstart
Sign up, connect one support tool, install the GitHub App, and see your first Mapped Bug — in under ten minutes.
TL;DR
Quickstart
Connect your support tool, install the GitHub App, and see your first Mapped Bug — the whole setup takes under ten minutes for a typical SaaS team.
Watari processes real tickets from your connected support tool. If you want to dry-run the pipeline before it touches live customer tickets, connect a sandbox subdomain (Zendesk) or a test workspace (Intercom) first.
Before you begin
You need:
- A Zendesk or Intercom account with an active support queue.
- A GitHub organization with at least one repository you want Watari to index.
- A Watari account (create one at the next step).
Steps
Sign up
Go to watari.ai/signup. You can sign up with Google OAuth or with an email address and password. If you use email, you will receive a confirmation link — click it before continuing.
After email confirmation, Watari walks you through a short onboarding form: your organization name, your role, and the support tool you use. Complete it and you land on the Watari dashboard.
Your account starts with a 14-day free trial — 10 Mapped Bugs included, no credit card required.
Connect a support tool
From the dashboard, go to Settings → Integrations. Connect either Zendesk or Intercom:
-
Zendesk — click "Connect Zendesk", enter your subdomain (the part before
.zendesk.com), and authorize on the Zendesk OAuth screen. Watari registers a webhook on your account automatically. Full walkthrough: Zendesk and Intercom OAuth setup walkthrough. -
Intercom — click "Connect Intercom", authorize on the Intercom OAuth screen, and select the workspace. Watari subscribes to your conversation events. Full walkthrough: Zendesk and Intercom OAuth setup walkthrough.
Only one support tool per Watari workspace. If you run separate Zendesk and Intercom deployments, use separate Watari workspaces.
Install the GitHub App
From Settings → Integrations, click "Install GitHub App". You will be redirected to GitHub.
On the GitHub screen, choose your organization and select the repositories you want Watari to index. You can choose "All repositories" or pick specific ones. Watari only reads repos you explicitly include here.
After authorization, you are returned to the Watari dashboard and indexing starts immediately.
Wait for indexing
Watari parses your repository and builds a searchable index. For a typical SaaS codebase (tens of thousands of lines), the first index completes in a few minutes. Large monorepos take longer — the dashboard shows progress under Codebase.
You can move on while indexing runs. Bug extraction works immediately; code mapping runs once the index is ready.
Receive your first ticket
Once your support tool is connected, Watari processes incoming tickets automatically. You do not need to take any action — tickets flow in via webhook.
When a qualifying ticket arrives, Watari extracts a structured bug and (once the index is ready) maps it to a file and function in your repository. The bug appears in the Tickets view at /tickets.
If you want to trigger the pipeline immediately without waiting for a live ticket, send a test ticket through your support tool using your normal support email or intake form.
Review the draft PR
When a Mapped Bug is confirmed, Watari opens a draft pull request in the mapped repository. You will see a link to it on the bug detail page at /tickets.
Open the PR in GitHub. Review the patch and the test. You have three options:
- Approve and merge — the PR moves through your normal review process.
- Request changes — leave a comment on the PR and Watari re-generates the fix.
- Close without merging — if the bug is out of scope or handled another way.
After the PR merges and a successful production deploy is confirmed via GitHub, Watari posts the customer-facing RCA back to the original ticket.
What happens if something goes wrong during setup
OAuth fails mid-flow — go back to Settings → Integrations and try the connection again. OAuth state is short-lived; starting a fresh flow is the right fix.
Indexing stalls — the Codebase view shows the status of each repository. If a repo is stuck in "Indexing" for more than 15 minutes, disconnect and reconnect it from Settings → Integrations → GitHub.
No bugs appear after a ticket comes in — the ticket may not have contained a reportable bug (billing questions, account requests, and feature requests are not extracted as bugs), or the extraction confidence was below threshold. Check the Tickets view for the ticket status.
Next: Core concepts — Mapped Bug, confidence thresholds, and the ticket lifecycle for a deeper look at the pipeline, or Zendesk and Intercom OAuth setup walkthrough for detailed Zendesk and Intercom setup.