Overview
Give customers a place to ask for help inside your mobile app. The installation guides teach embedding Voiceflow’s text-chat widget. Custom chat and voice interfaces use the agent APIs; platform walkthroughs for those approaches are planned. Your app team owns navigation, identity boundaries and the app release.
Start with an existing agent that can answer a public support question. If you are building the agent too, begin with Build and Knowledge.
Choose your implementation
Planned platform guides remain listed separately at the end of each widget manual. The API references own custom session, message and audio contracts.
Guides
These workflows assume the mobile chat screen is already installed:
- Pass app context — start help with an appropriate topic or language, while treating app-supplied values as hints.
- Separate app conversations — choose retention and handle logout, shared devices and account changes.
- Recover interrupted conversations — handle suspension, lost connections and uncertain delivery without repeating customer actions automatically.
Test and release
Test a real customer question through your app’s Help screen and check the visible answer. A successful API request, browser preview or mounted WebView proves a different part of the journey. Each installation manual includes the app test and nearby troubleshooting.
For the widget installation, keep three releases distinct:
- Agent release: publish the intended agent and widget settings to the chosen Environment.
- Hosted page release: deploy the widget page and its configuration. Remote changes can affect installed apps without an app update.
- App release: distribute the platform build with the correct widget URL and lifecycle behavior. Test that distributed build with a fresh conversation.
Returning conversations can retain an earlier execution context. Use a fresh conversation to verify a new release, then check continuity separately. Record the app version, hosted-page version and selected Environment when diagnosing a mismatch.
Continue with Developers
Use Sessions for runtime identity and routing, Handling responses for a native renderer, and Authentication for credential boundaries. The platform manuals own app deployment; exact runtime contracts stay in Developers.