Question 1

What is a Mapped Issue?

Accepted Answer

A Mapped Issue is a structured bug report, or a code-actionable feature request, extracted from a customer support ticket and paired with the file(s) and function(s) in your codebase that our retrieval ranks as the most likely cause. Draft pull requests, RCA back to your customer, and tracker sync to Jira, Linear and GitHub Issues are bundled with every Mapped Issue and never billed. We do not claim the top-ranked file is always the right one: on our published benchmark the top-ranked file is correct 56.5% of the time, which is why the Mismapped credit below exists and why the whole benchmark is public.

Question 2

How often is the mapping right?

Accepted Answer

56.5% at rank 1 on out-of-sample public repositories, measured against a protocol we registered before running it. Published bug-localization research on customer-written reports lands between 28% and 42%, so we are ahead of it, and we would rather you read the number than take the word "mapped" on trust. Every case, every miss and the raw results are on our Proof page.

Question 3

When does the meter fire?

Accepted Answer

The meter fires the moment a Mapped Issue is persisted: extraction is confident and at least one candidate code location cleared our threshold. We never charge for downstream delivery (PR, RCA, sync), for a question, or for an open-ended feature request. A small, specific feature request that we map to your code counts the same as a bug, and only once however many tickets ask for it. If we map the wrong file or function, flag it as Mismapped within 7 days, from the bug itself, for a credit on your next invoice.

Question 4

After my trial ends?

Accepted Answer

Your subscription will begin on the plan you choose. You can change tier or cancel any time from the billing settings page.

Question 5

Can I change my plan later?

Accepted Answer

Yes. Upgrade or downgrade at any time from billing settings. Upgrades take effect immediately; downgrades take effect on the next billing cycle.

Question 6

What happens if I exceed my included Mapped Issues?

Accepted Answer

Growth and Scale flex with on-demand Mapped Issues at $25 / $20 / $15 per Mapped Issue. Starter pauses at the hard cap with an in-app upgrade prompt, no surprise bills. Design Partner is a flat fee with no on-demand Mapped Issues.

Question 7

Do you offer annual billing?

Accepted Answer

Yes. Starter, Growth, and Scale all offer annual billing for the equivalent of 2 months free (≈17% off). Design Partner is monthly only.

Question 8

What is “Ownership intelligence”?

Accepted Answer

Watari reads your repo’s CODEOWNERS to auto-route reviews on the PRs we draft. When you don’t have a CODEOWNERS file, we infer the right owners from your last 365 days of commit history (per-commit exponential decay, bots filtered, co-authors credited) and offer a one-click PR to add the synthesized file. Bundled, available on every plan.

Question 9

What if the same bug is reported by multiple customers?

Accepted Answer

Watari embeds every incoming bug and clusters duplicates from Zendesk + Intercom + Freshdesk + email into one canonical engineering bug. We draft one PR (with the customer reports surfaced inline) and fan the RCA back to every linked customer ticket, idempotent on each provider’s API so retries never double-post. You’re billed per fix, not per ticket. Bundled, available on every plan.

Features	Starter	Growth	Scale
Included Mapped Issues / month	20	60	150
On-demand Mapped Issue rate	$25	$20	$15
Hard cap (auto-pause)	50	150	400
Connected repositories	1	3	10
AI bug & feature extraction
Bug-to-code mapping
Draft pull requests
Customer-facing RCA
Slack, Microsoft Teams, Linear, Jira, GitHub Issues sync
80% / 100% spend alerts
Inferred CODEOWNERS (ownership map + 1-click PR)
Cross-channel bug clustering + RCA fan-out
Multi-repo bug fan-out
Slack support channel

Pricing built around Mapped Issues

Design Partner

Compare plans

Frequently asked questions