Native in-app support chat
Users can send text and up to five photos in a message from a native chat interface. The SDK shows delivery states, supports retries after failures, and updates read status while an active conversation is visible.
reception
Reception provides native in-app support chat for iOS apps, giving teams a shared inbox for customer conversations, context, and follow-up actions. It also supports review links and registered paywall offers within a support thread.
In-app support for iOS apps
Reception is an in-app support product for iOS applications. It embeds a native chat so users can ask for help without leaving the app, while teams manage conversations in a shared inbox.
Beyond troubleshooting, the chat can support retention and conversion workflows: agents can send App Store review links or registered paywall offers during a conversation. Apps can pass user identity and metadata into Reception so support teams have relevant context when responding.
Core capabilities
Shared inbox with customer context
Teams work from a shared inbox that can cover multiple apps. Conversation context can include user details, plans, and custom metadata; the homepage also names RevenueCat, Superwall, and Adapty among supported connections.
Review request cards
Agents can send review cards after an App Store ID is configured. The card opens the supplied App Store review URL and records a click receipt; it does not verify that a review was submitted.
Paywall cards
Agents can send a registered paywall card from the dashboard. The app receives the tap through an onPaywall handler, then presents its own purchase screen and handles the transaction.
Configurable chat appearance
Apps can set the accent color, chat title, welcome message, and chat entry point. Remote configuration lets teams change colors and text without publishing an app update.
Telegram and documentation-based AI replies
Reception can route new support messages to a connected Telegram chat, where a team can reply. It also offers an AI workflow that uses supplied documentation, responds when confident, and hands uncertain conversations to the team.
Where it fits
Resolve support issues inside the app
Give users a direct way to report a failed purchase, ask about a feature, or share screenshots from the point where they encounter the issue. Teams can respond later if the user writes outside staffed hours.
Guide plan and offer conversations
When a customer asks about a lower-cost plan, renewal, or available option, an agent can send a registered paywall card that opens the app's existing purchase flow.
Request App Store reviews after support
After resolving an issue or helping a satisfied user, an agent can send a review card linking to the app's App Store review page.
Support signed-in account holders
For apps with account systems, connect sign-in, sign-out, and deletion events to Reception. A backend can add JWT-based verification for workflows where teams need stronger assurance of identity.
Coordinate a small support team
Route new conversations to a Telegram group or use documentation-based automated replies for common questions, with escalation when the AI is unsure.
Pros and Cons
Pros
- Native iOS chat accepts text, photos, and mixed text-and-photo messages, with delivery feedback and retry behavior.
- A single organization inbox can manage conversations from several apps while retaining app-specific IDs and context.
- Chat appearance and entry placement can be tailored to the host app, with remote changes to colors and text.
- Optional verified identity uses server-signed JWTs, helping teams distinguish verified account data from app-supplied labels.
- Support can be handled in the web inbox or through connected Telegram notifications and replies.
Cons
- The SDK is limited to iOS 17 and later; React Native/Expo support requires a development build rather than Expo Go.
- Chat history is scoped to the device registration and is not merged when the same user is identified on another device.
- The SDK has no built-in camera capture, document picker, video/audio messaging, arbitrary file attachments, message editing, or individual message deletion.
- Review-card clicks indicate intent to open an App Store URL, not a completed review or rating; paywall-card opens likewise do not confirm a purchase.
FAQ
Do users need a separate support account?
No. Users can open the chat and send a message without creating a separate support account. Apps with sign-in can identify users with their existing name, email, and user ID.
Can Reception be used with more than one app?
Yes. Each app can be added to an organization with its own App ID, while conversations are managed from one inbox.
What happens when a support team is offline?
Users can leave a message while the team is offline. Teams can reply later, and users who have allowed configured push notifications can be notified of the reply.
Which platforms and languages are supported?
The SDK supports iOS 17 and later in native iOS and React Native/Expo development builds. Expo Go is not supported. The chat interface supports 48 languages; custom app text is localized by the host app and messages are not automatically translated.
Can a support conversation direct a user to an offer?
Yes. An agent can send a paywall card for a paywall registered by the app. Tapping the card calls the app's handler, which presents the purchase screen and manages the purchase.
Quick Facts
- Category
- Customer Support / In-App Messaging
- Primary platform
- iOS 17 and later
- Framework support
- Native iOS and React Native/Expo development builds
- Chat languages
- 48 interface languages
- Team workflow
- One shared inbox across multiple apps
- Pricing evidence
- Homepage lists a $25/month flat price and directs enterprise-scale apps to contact Reception for pricing