Is Chatwoot ready for the Japanese market?
— a Tokyo native's gap map

The app has a Japanese locale (ja.yml), but chatwoot.com and the pricing page render only in English. The footer language selector shows English with no other reachable option.

chatwoot.com/pricing — English only confirmed

This is the exact point where foreign products lose Japan. A buyer reaches the translated product through an all-English evaluation path — but most never get that far, because the marketing and pricing they read first are English. They assume the whole thing is English and leave before seeing that the app is localized. The work is half done, and the missing half is the half that converts.

Japanese landing, pricing, and signup pages, plus a real language toggle, so the funnel matches what the product already delivers. This has the highest leverage because the asset (a translated app) already exists and just isn't being surfaced.

Footer has Privacy, Security, and Terms. No 特商法に基づく表記 page found. Hosting is noted as US-based AWS, with GDPR and SOC 2 referenced — neither of which is the Japan-specific trust signal a Japanese buyer looks for.

chatwoot.com/privacy-policy (footer links checked)

Japanese buyers look for 特商法 disclosure before paying. GDPR and SOC 2 are reassuring globally but aren't the Japan-specific signal a local buyer checks for. Without 特商法, a careful buyer hesitates to put a recurring charge through.

A 特商法に基づく表記 page with the required fields. It's a known template — not a build, not a legal engagement, just a page.

Issue #13765 (filed by frafeju) reports that in the AI input fields, pressing Enter to confirm a CJK IME conversion immediately submits the prompt, sending unfinished phonetic text. Marked closed with a fix proposed (an isComposing check), but confirmation across all input fields is worth verifying.

github.com/chatwoot/chatwoot/issues/13765

Japanese is entered through an IME where Enter confirms the conversion. If Enter also submits, agents send half-typed garbage to customers or to the AI. A support team that hits this in a trial concludes the product wasn't built for Japanese input — and for a customer support tool, that's a hard stop.

Apply the isComposing guard consistently across every Enter-to-submit field, and add a quick IME pass to QA so it doesn't regress.

Plans in USD: Hacker $0, Startups $19, Business $39, Enterprise $99 per agent/month; Captain AI add-on $20 per 1,000 credits.

chatwoot.com/pricing — USD confirmed

A USD recurring charge means exchange-rate uncertainty and a messy line on a Japanese invoice. For finance approval, a clean JPY figure is much easier to push through — especially for a per-agent subscription at scale.

JPY display pricing and, where possible, a JPY invoice for the buyer's accounting.

App UI is localized. Onboarding flows, docs, and the support funnel are English-only.

A buyer for a support tool is, by definition, sensitive to support quality. If onboarding and help are only in English while their own customers expect Japanese, they doubt they'll get help in their language when something breaks. That doubt blocks the purchase even when the product itself is fine.

Japanese onboarding copy and at least a core slice of Japanese docs, plus a clearly stated support-language expectation (even "English support only, app in Japanese" is more honest than silence).

With no Japanese marketing pages, there's nothing indexed against the terms a Japanese team searches. The Japanese-locale app is invisible at the discovery moment.

A team wanting an open-source support tool searches 「intercom 代替」 or 「問い合わせ管理 オープンソース」. With no Japanese content, they land on a local roundup or a domestic tool instead, never learning the app is already in their language.

A few Japanese pages targeting those queries, including an 「intercom 代替」 comparison. The existing Japanese app locale gives you authentic material to reference.