How do I handle support requests from the Customer Center?
The RevenueCat SDK's Customer Center can let customers write to you from inside your app. RevenueDot stores each request, emails it to your support address and lists it under Lifecycle > Support > Tickets. Your help desk can also show the customer's subscription next to the conversation.
Turn on tickets#
Open Lifecycle > Support > Customer Center.
- Enter the support email. Tickets are sent there, with Reply-To set to the customer's address, so you answer from your inbox.
- Turn on Let customers create tickets and choose who may (customers with an active subscription, without one, or everyone).
- Choose which details the email includes: app user ID, active entitlements, total spent, customer since, last opened, app version, country, device and more.
The SDK reads these settings with the rest of the Customer Center configuration. A customer can send up to 5 tickets an hour, one device (IP address) up to 20, and the whole project receives up to 100 an hour, so a leaked SDK key cannot flood your inbox. The customer's email must be one plain address, and the message is cut at 5,000 characters. If tickets are off, the SDK offers its email link instead.
Show subscription data in Intercom or Zendesk#
RevenueDot has a ready app for each help desk. Both show the customer's status, active entitlements, plan, store, renewal or expiry date, billing issue, total spent, customer since, refund requests and open tickets, with a link to the customer in the dashboard.
Intercom#
The Intercom inbox app is a Canvas Kit app that you create in your own Intercom workspace. Intercom calls RevenueDot directly, and RevenueDot checks every request's signature, so no API key is involved.
-
In the Intercom Developer Hub, create an app and open Canvas Kit. For the Inbox, set the initialize URL to:
- RevenueDot Cloud:
https://api.revenuedot.app/v1/support/intercom/{project_id}/canvas - Self-hosted:
<your server>/v1/support/intercom/{project_id}/canvas
Use your project ID, for example
https://api.revenuedot.app/v1/support/intercom/proj1a2b3c4d/canvas. The Integrations → Intercom inbox page in RevenueDot shows the exact URL to copy. - RevenueDot Cloud:
-
In the Developer Hub, open Basic information and copy the app's client secret. In RevenueDot, open Integrations → Intercom inbox, paste it as Intercom app client secret and click Connect Intercom inbox.
-
Install the app in your workspace and add it to the inbox sidebar.
How a request is checked: Intercom signs the raw request body with the client secret and sends the hex HMAC-SHA256 in X-Body-Signature. RevenueDot computes the same signature with the saved secret and answers 401 when it is missing or does not match. A project without a connected Intercom inbox answers 404.
How the customer is found: by the contact's user ID (external_id), which should be your app user ID, then by the contact's email against the customers' $email attribute. Without a match the sidebar says so. The answer is Canvas Kit components: a table of the fields above and an Open in RevenueDot button.
To send subscription events to Intercom contacts as well, use the separate Intercom integration.
Zendesk#
The Zendesk app is a private ticket sidebar app. Its source is in the RevenueDot repository: integrations/zendesk-app (manifest, sidebar page, translations and logos). It looks the ticket requester up by email with GET /v2/projects/{project_id}/support_summaries?email=.
- In RevenueDot, open API keys and create a secret key with only the
customer_information:customers:readpermission. - Download the integrations/zendesk-app folder, zip its contents (or run
zcli apps:packagein it) and upload the zip as a private app in Zendesk: Admin Center › Apps and integrations › Zendesk Support apps › Upload private app (Zendesk's guide).zcli apps:createin the folder does both. - Fill in the app's three settings:
- RevenueDot API URL:
https://api.revenuedot.appon RevenueDot Cloud, or your server's URL. - Project ID: from Project settings in the dashboard, or the Integrations → Zendesk page.
- Secret API key: the key from step 1. Zendesk keeps it as a secure setting and adds it to the request on Zendesk's servers, so agents' browsers never see it.
- RevenueDot API URL:
- In RevenueDot, open Integrations → Zendesk and click Mark as installed, so the card shows the app as active.
Self-hosted servers: Zendesk sends a secure setting only to the domains listed in the manifest's domainWhitelist (Zendesk's guide). Add your server's host name to domainWhitelist in manifest.json (it lists api.revenuedot.app) before you upload the app, for example "domainWhitelist": ["revenuedot.example.com"].
Use the support summary from your own app#
Any other help desk can call the support summary with a secret API key that has customer_information:customers:read:
curl "https://api.revenuedot.app/v2/projects/$PROJECT_ID/support_summaries?email=wren@example.com" \
-H "Authorization: Bearer $REVENUEDOT_SECRET_KEY"or, when you know the app user ID, GET /v2/projects/{project_id}/customers/{app_user_id}/support_summary. The answer has the customer's status, active entitlements, each subscription with its store, auto-renew state and expiry, total spent, refund requests, open tickets and a link to the customer in the dashboard (API reference). Call it from your app's backend, never from code that runs in an agent's browser, because the key is secret.