Mobile client for the Chatwoot customer support platform, built with React Native and Expo, aimed at support agents and teams who need to answer customer conversations from Android and iOS devices instead of a desktop browser.
What it is
chatwoot-mobile-app is the official mobile application for Chatwoot, the open-source customer engagement platform. It is written in TypeScript with React Native and Expo, distributed under the MIT License, and carries the topics android, ios, react-native, conversations, and customer-support. The repository holds the client only: it pairs with a Chatwoot server and states a supported Chatwoot version of 3.13.0 or later, plus minimum runtime versions of iOS 13.4 and Android 6.0. Its published homepage is the Chatwoot mobile apps page, and the project is maintained by Chatwoot Inc.
The concrete problem it solves is agent mobility. A browser-based support inbox ties an agent to a desk, so new customers and follow-ups wait until someone returns to a laptop. This app replaces that browser session on the phone: agents take a conversation on the move, answer from canned responses, read realtime notifications about system activity, coordinate with colleagues through private notes, and move conversations between statuses. It also replaces the unofficial third-party mobile clients that Chatwoot users would otherwise depend on, since it ships from the same organisation that maintains the platform and tracks the server version.
Key capabilities
- Follow up on customer conversations while away from a desk, with the repository's own framing being that agents "do not miss out on the new customers."
- Reply to customers using canned responses rather than retyping common answers.
- Receive realtime notifications about system activities so new customer messages surface on the device.
- Communicate with other team members through private notes attached to a conversation.
- Assign statuses to conversations to move them through the support workflow.
- Targets Android 6.0+ and iOS 13.4+ against a Chatwoot server on version 3.13.0 or later.
- Distributed as a build under the MIT License, with
CONTRIBUTING.md linking to the mobile app setup guide for contributors.
Who uses it and how
- Support agents at organisations running a Chatwoot instance who need to answer tickets outside working hours or off-site.
- Small support teams where the same people handle triage and replies, and status assignment is how work is split.
- Teams that already rely on canned responses in the web inbox and want the same answers available on mobile.
- Operators evaluating the app before rollout, who can join the beta channels rather than wait for a store release.
- Teams that standardise on a self-managed Chatwoot deployment and therefore need a client that tracks a declared server version.
Getting started
The README points to the Android and iOS application downloads, and contributors are directed to the mobile app setup guide linked from CONTRIBUTING.md for the React Native and Expo development setup. Beta builds are reached through the Google Play testing programme for com.chatwoot.app and through TestFlight on iOS.
How it compares
No competing products are named in the facts supplied, so this project stands alone in this registry: it is a first-party companion client to the Chatwoot platform rather than an alternative to any other support tool. Its distinguishing property, as far as the facts go, is that it is MIT-licensed and maintained by the same organisation as the server it talks to.
When to use it — and when not to
Use it only if there is a Chatwoot server to connect to, on version 3.13.0 or later; without that instance the app has nothing to talk to. Read the README closely before adopting: it documents features, supported versions, download links, and beta channels, but it does not name a package, image, or build command, leaving the actual setup steps to the external contributing guide. The repository shows 74 open issues and a last push in September 2026, which is a signal to check recent activity against the server version in use before committing a support team to it.
