In-app AI support for mobile apps
In-app AI support for iOS and Android apps: a React Native SDK and web messenger on npm, signed user tokens, app store refund and subscription questions handled by your policy, privacy first.
In short: OctaDezx is AI support for mobile apps. Today an iOS or Android app opens the OctaDezx chat link or web widget from its Help screen in a WebView or in-app browser, and the agent answers account, subscription and how-to questions from your help content in the user's language, reads screenshots, explains App Store and Google Play refund and subscription rules from your policy, and hands real problems to your team. The React Native messenger SDK and the web messenger SDK are published on npm at version 0.1.0 under the MIT license, and signed user tokens let the agent treat a signed-in user as that user. Native iOS and Android SDKs are on the roadmap and not shipped.
App users want help without leaving the app and without waiting days for an email reply. OctaDezx puts an AI support agent behind your Help screen that answers from your own help centre and policies, explains what the app stores decide and what you decide, and escalates bugs, account problems and refund requests with the conversation attached.
The everyday problem
Mobile support usually means a contact form, a long queue and a one-star review from someone who could not find help. Subscription and refund questions are especially confusing, because the app store, not the developer, often processes the refund.
How OctaDezx helps
Start with what works today: the chat link or widget in a WebView, your help content as the knowledge source and your helpdesk for escalations. React Native apps can use @octadezx/messenger-react-native from npm, and your backend can sign user tokens and use the Agent API and signed webhooks for deeper integration.
Mobile app support it handles
- In-app help chat today. Open the shareable chat link in an in-app browser or load the web widget in a WebView from your Help or Contact screen. No native code is needed to start.
- React Native SDK on npm. npm install @octadezx/messenger-react-native react-native-webview. Version 0.1.0, MIT licensed, with push token registration. Native iOS and Android SDKs are on the roadmap; native apps use the WebView path until they ship.
- App store refunds and subscriptions by policy. Explain how to request a refund or cancel through the App Store or Google Play, what your own policy covers and what the store decides. Where your policy allows, the agent files a refund request for your team to review.
- Verified signed-in users. Your server signs a short-lived user token with signUserToken from @octadezx/sdk, and the SDK refreshes it. Without one, the agent treats users as anonymous and hands account-specific requests to staff.
- Screenshots of errors. Users can attach a screenshot in web chat. The agent reads it as part of the question before answering from your docs or escalating.
- Every user's language. Replies in 50+ languages, detected per user, including code-switched messages that mix two languages in one sentence.
- Escalation into your helpdesk. Bugs and account problems hand over to your team with the conversation and any screenshot, and can open a ticket in Zendesk, Freshdesk or Intercom.
- Follow-ups from your backend. The messenger SDKs register push tokens for verified users, but OctaDezx does not send push notifications for new replies yet. Your backend can react to signed webhooks, such as an escalation, and send your own push or email.
A subscription question from inside the app
Illustrative flow, not a customer transcript.
- 1. Open help. A user taps Help, which opens your OctaDezx chat link in an in-app browser.
- 2. Subscription. "I was charged after I cancelled." The agent explains, from your policy, that store subscriptions are cancelled and refunded through the store, and links your written instructions.
- 3. Bug. The user attaches a screenshot of a sync error. The agent recognises the documented error and gives the fix from your help article.
- 4. Handoff. When the user says the fix did not work, the conversation and screenshot are escalated to your team, and your backend receives a webhook.
Answers from your help content, checked before they are sent
The agent answers from the help articles, FAQs and policies you import. A question that asks several things at once is split into separate steps, each with its own lookup, and a final verifier refuses any amount, promise or action no verified fact supports. Every written reply is then checked against your verified facts before it reaches the user.
When a step cannot be answered, for example because it needs the user's account, the agent asks a targeted question or hands off. The method and the current holdout safety measures, including privacy cases, are published.
How to integrate it into an app
- WebView or in-app browser. Load the chat link or widget from your Help screen. This works in native iOS and Android apps, React Native, Flutter and other cross-platform frameworks.
- REST API from your backend. Send a message and read the transcript with a business-bound key from your server. Never ship an API key inside the app binary.
- Signed webhooks. HMAC-signed events for escalations and refund requests let your backend notify the user or open an internal task.
- Helpdesk and MCP. Escalations can file tickets in Zendesk, Freshdesk or Intercom, and your team can work conversations through the MCP server.
- SDKs on npm. @octadezx/messenger-react-native and @octadezx/messenger at 0.1.0, MIT licensed, plus @octadezx/sdk on your server for user tokens. Native iOS and Android SDKs are on the roadmap.
What to know before integrating
- There is no native iOS or Android SDK today. Native apps use the chat link or widget inside a WebView or in-app browser; React Native apps can use the npm package, which is at version 0.1.
- App store refunds are processed by Apple or Google, not by OctaDezx. The agent explains the process and your policy and can file a request for your own refunds; it cannot issue or reverse a store charge.
- The agent does not see user accounts, purchases or your database unless you supply that information as knowledge. Do not put one user's private data into shared knowledge.
- Files attached in customer chat are stored with the message and the current upload flow uses a public file URL. Ask users not to upload identity documents or other sensitive material.
Frequently asked questions
- Can I add an AI chatbot to my mobile app? Yes. Open the OctaDezx chat link or web widget from your app's Help screen in a WebView or in-app browser, train the agent on your help content and connect your helpdesk for escalations.
- Is there an in-app AI support SDK for iOS, Android or React Native? Yes for React Native: @octadezx/messenger-react-native is published on npm at version 0.1.0 under the MIT license. Native iOS and Android SDKs are on the roadmap and have not shipped; the WebView path works in every app today.
- Can it handle App Store and Google Play refund questions? Yes, by policy. It explains that store purchases are refunded through Apple or Google, gives your written steps and files a request for your team when your own policy applies. It cannot issue a store refund.
- How does the AI know who the user is? Your server signs a short-lived user token for each signed-in user, and the SDK passes and refreshes it. Without a valid token, chat users are treated as anonymous, and account-specific requests are handed to your team.
- Does it send push notifications? Not yet. The SDKs register push tokens for verified users, and sending pushes for new replies is planned. Today your backend can receive signed webhooks, for example when a conversation is escalated, and send your own push notification or email.
- Can app users send screenshots? Yes, in web chat. The agent reads an attached screenshot as part of the question.
- Is it safe to put the API key in my app? No. Keep API keys on your server. The app should only open the chat link or widget; your backend calls the REST API.
- Which languages does it support? Replies are written in 50+ languages, detected per user. Multi-step questions are planned in English, Spanish, Portuguese, French, German, Italian, Dutch and Polish.
Explore the connected tools
- Mobile apps industry overview
- AI player support for games
- AI support for SaaS
- Enterprise AI support
- Ecommerce customer care
- How to add AI support inside your app
- Multimodal AI agent
- Integrations directory
- Plans and pricing
Read more on this
- How to add AI support inside your mobile app
A practical guide to in-app AI support: where the help entry point goes, WebView versus SDK, identity, app store refunds, privacy, escalation and what to measure. - Answering customers in 50 languages without hiring for it
Language is the cheapest expansion lever most stores never pull. What actually changes when your support answers in the customer's own language, and what to watch out for. - What happens to your customer data when you use AI support?
Handing customer conversations to an AI raises a fair question about where that data goes. Here is what to actually ask, what good handling looks like, and the difference between data used to help your customers and data used for something else.