Make room for your app.
Create your workspace and add an app.
Give people a reason to keep going
Help people get unstuck. Explain a plan. Invite an honest review.
All inside the app they already use.
Human replies, useful actions and explicit support rules · AI requires configuration
I moved to a new phone. Where’s my purchase?
Hi Maya! Let’s check Restore purchases in your settings. I’m here if you need a hand.
I moved to a new phone. Where’s my purchase?
DeliveredHi Maya! Let’s check Restore purchases in your settings. I’m here if you need a hand.
Answer the question where it happens. Keep the context and give people a way forward, without sending them out of your app. Read the guide
Fictional Luteal examples · controls work locally · nothing is sentGood support is good for your app
A question about access. A plan that needs explaining.
A chance to listen before someone leaves.
When something gets in the way, give people somewhere to turn.
Pick up the conversation
Keep account history scoped
Cross-device history needs your host’s verification.Explain the options. Open the plan your app already owns. Let the customer decide.
Host-owned actionsOffer an optional review to eligible users. No sentiment filter. No incentives.
Neutral review requestsNo separate customer password. A conversation inside your app.
App-specific access. Private notes. One team inbox.
Built for these moments. Retention, revenue and reviews depend on your app and the care you give.
Create your workspace and add an app.
LobbyHelpRow(client: support) {
showHelp = true
}Install the SDK and follow your setup guide.
Customer question received
Your reply displayed in the app
Illustrated setup checklistSend a question. Reply. Check both ends.
Let people ask in their own words.
Keep the conversation close to home.
Start with native chat. Configure the connections you need, per app and environment. These are interfaces and adapters, not customer logos or proof of a live connection.
Read app-scoped public conversations through an MCP connection. Choose the apps and environments a token can access, set its expiry, and revoke it when it is no longer needed.
Set up read-only accessClient setup and verification are separate. No client is connected by this example.Current workspace permissions are checked on every request. A token is access, never a claim that a client has connected.
A plan you can understand
One workspace for a family of apps.
Clear allowances. No automatic overages.
The monthly subscription renews monthly at $15 USD. Checkout availability is shown in your workspace. Live payment activation is a separate gate; no charge is taken when you create a workspace.
How allowances workBilled monthly. Renews monthly.
Choose $15 USD per month or $150 USD per year. These are recurring subscriptions: the monthly plan renews monthly, and the yearly plan renews annually. Checkout availability and the final billing terms are shown in your workspace. Sandbox testing is separate from activating paid production access.
Create a workspace and development app, install the native source SDK and complete a real two-way conversation. The pilot includes private photos, registered action cards, team access, saved replies and explicit support rules. External provider connections have separate setup requirements.
It gives your team a way to respond where customers get confused: explain a feature, help restore access or point someone toward a plan that fits. Retention and revenue depend on your app, response and customer need; we do not claim measured gains.
Configured AI can draft replies or summarize public conversation context with source references. A person reviews human drafts. Optional automatic replies are separately enabled and restricted to complete published navigation answers; configuration and live quality checks remain separate. The inbox works without AI.
Register the paywall, screen or approved link your app can open, then send a card from the inbox. Your app owns the purchase flow. Review actions are optional and neutral, available to all otherwise-eligible users without sentiment filtering or incentives. A tap is not a completed purchase or review.
No. Guests can ask for help inside your app. Verified history uses an assertion signed by your backend, with separate app and environment boundaries. The local API and Swift implementation are tested; hosted account exchange has its own readiness gate.
Choose Native, Soft or Compact conversation appearance, then set your colors and support copy. Your app retains its navigation, purchase flow and notification delegates. The Swift SDK supports iOS 17 and later through SwiftUI and UIKit. Expo and Flutter source clients also provide native foreground text chat; their guides list the current platform limits.
Enabled support rules can send a clearly labelled reply after checking timing and conversation activity. Preview a rule before enabling it. Push notifications and Telegram still need separate provider setup.
There are no automatic overages. Already-counted eligible threads can continue; newly active threads use your configured support email fallback at the cap. Production threads and assists reset monthly. Storage is current stock. Checkout is in isolated testing; paid production access is not enabled.
Make the next question easier to answer
Start with one app and one real conversation.
Build the rest of the workflow from there.