# Review requests Send a review card from a Reception conversation so the customer can open your app’s App Store review page. Configure the App Store ID and localized templates in the dashboard, then prepare and send each request from the inbox. ## How review requests work A review request is an agent message with a button, **Rate on the App Store** by default. The built-in label follows the app’s language; custom labels appear as written. ReceptionKit displays the card automatically in the conversation. Tapping the button opens the App Store URL supplied by Reception. After the normal [ReceptionKit integration](/docs/get-started), no additional SDK configuration, StoreKit method, or host-app review button is required. Requests are sent explicitly by a team member; saving templates or resolving a conversation does not send one. Push configuration is optional for displaying the card in chat. If [push notifications](/docs/push-notifications) are configured and the device is eligible, sending a review card also follows the normal reply notification flow. Keep requests optional. Do not offer incentives or make support conditional on leaving a review. Apple prohibits manipulating reviews; see its [App Review Guidelines](https://developer.apple.com/app-store/review/guidelines/#business). ## Configure the App Store ID An organization Owner configures reviews; both Owners and Agents can send configured review cards in the inbox. 1. Open **Settings → Apps**, then select your app. 2. Open **App Store Reviews**. The same dialog is available in the optional Integrations step during setup. 3. Enter the numeric **App Store ID**: the number after `id` in your app’s App Store link. Enter only digits, without the `id` prefix or the rest of the URL. This is separate from your bundle identifier. 4. Preview the messages and optionally customize them as described below. 5. Select **Save**. Saving configures the app; it does not send a request or verify that the ID belongs to the intended listing. Check the ID against your own app’s listing before sending a card. An empty ID disables new review requests. Cards use the saved App Store ID. Changing or clearing it can change or remove the button on older cards after they refresh.  ## Customize templates The scenario menu selects one of three templates. These are drafting choices, not automatic triggers. | Scenario | Built-in English text | | --- | --- | | General | Enjoying the app? A rating really helps. | | After helping | If we helped, we'd love a review! | | After feedback | Thanks for your feedback! If you like the app, a rating would mean a lot. | 1. Select a scenario and a preview language in **App Store Reviews**. 2. Select **Customize** to edit that scenario’s message in the selected language. 3. Enter up to 500 characters. Use `{app}` wherever you want the saved app name inserted. 4. Use the back control to inspect the preview, or switch scenario or language to edit another translation. 5. Select **Save** to save the settings. **Cancel** discards unsaved changes. For example, enter this text in the **General** template editor for English: ```text Thanks for using {app}. You can share your experience in an App Store review. ``` For an app named Example App, the preview replaces `{app}` with `Example App`. This sample is only template text; entering it does not send anything. The preview’s App Store button is inert. **Reset to default** clears only the selected scenario and language override. Blank text or text identical to the built-in default also uses the default. Opening the editor does not create an override, and drafts remain available when switching languages or scenarios within the dialog. The **Custom** indicators identify combinations with an override. ### Template languages The menu includes all [48 supported languages](/docs/language). Custom text applies only to its selected language and scenario; other languages keep their defaults. For a real conversation, Reception selects the template language from the device’s last reported **App language**. Supported regional and script variants are matched using the [language selection rules](/docs/language); unsupported app languages fall back to English. Only older devices without an app-language report use their device locale as the fallback input. The preview language changes what you edit, not the customer's app language. Reception does not translate your custom text. ## Draft and send a review card {#send-review-card} 1. Open the device’s latest iOS conversation in **Inbox**. If it is closed, select **Reopen** first. Cards sent to an older thread do not appear in the app’s current conversation. 2. Select **Ask for review**, the star beside **Mark resolved**, to open **Ask for a review**. If a review was requested before, the dialog shows **Sent [date]** and either **no reply yet** or **they’ve replied since**. 3. Under **Button**, choose one of the app’s saved labels. **Auto translated** marks the built-in **Rate on the App Store** label; custom labels are sent exactly as written. 4. Leave **Message (optional)** empty to send only the button, or choose **General**, **After helping**, or **After feedback** to fill in a template. Check **Templates in [language]**, then edit up to 1,000 characters. Choosing another template replaces your message. Cards cannot include images. 5. Check the live **Preview** as you change the message or button. If **Already sent, no reply yet** appears, type **send review** to confirm the repeat. 6. Select **Send review request**. The dialog closes after a successful send. Check the card in the transcript and **Review asked** in the customer’s details. Select **Mark resolved** separately when finished. An Owner manages each app’s labels in **Settings → Review & Offer CTAs → Review card**. The first label is selected by default. **Cancel** closes the dialog without sending; your ordinary reply draft stays separate.  ### When the recipient’s language changes If the recipient’s reported language changes before you send a card with text, the send stops and the dialog shows the new language. Your message stays intact. Check it, edit it or choose a template in the new language, then select **Send review request** again. A card without text does not require this check. Offline app-language changes reach Reception after the device synchronizes. Sent messages and custom button labels are not translated later. The built-in button follows the app’s current language. ## Repeat requests Each review card updates the device’s **Review asked** date, which **Reset support** preserves. The dialog requires **send review** only when the customer has not written since the last request. Once they reply, that confirmation is no longer required. Review cards still require an App Store ID and an open conversation.  ## What a click receipt proves After the customer taps the card, the dashboard can show **User tapped to leave you a review on the App Store**. Its timestamp records when Reception received the first report, which may be later than the tap if the device was offline. A card can still be tapped after its conversation is closed. A receipt does not prove the App Store opened, a review was submitted, or a particular rating was given. Missing receipts are also inconclusive: connectivity and SDK version affect reporting. Opening a review link from the dashboard does not record a customer tap. The optional [SDK event](/docs/events) `.reviewOpened` reports the same button action to your app. No extra integration is needed for dashboard reporting. App settings → **Chat actions** shows sent counts, first opens, and open rate for cards sent in the last 7, 30, or 90 days, with a breakdown by sending agent. [Paywall cards](/docs/paywalls) use the same reporting. Neither metric confirms a completed review or purchase. ## Verify the setup ### Preview without sending Open **App Store Reviews**, check the numeric ID, and preview the scenarios and languages you use. The preview does not send a card or open the App Store. Select **Cancel** to discard sample edits. ### Verify delivery on your own test device 1. Send a test support message from your app and find its latest conversation in Inbox. 2. Check **App language**. 3. Send a review card and confirm it appears in the device's chat. 4. Tap the card’s button and verify the intended listing. You can return without submitting a review. 5. Check the dashboard receipt once the device is connected. Open **Ask for review** again to check the last-request date; the repeat warning appears if you have not sent a customer message since the request. A simulator can check card rendering; use a real device to verify App Store behavior. ## Troubleshooting | Symptom | Check | | --- | --- | | Ask for review is disabled | Inspect its tooltip: add the App Store ID in app settings or reopen the conversation. Wait if a status change is still saving. | | Settings are unavailable | App configuration requires an Owner. Agents can send cards after an Owner configures reviews. | | I need to send an image with a card | Send the image as a separate reply from the conversation composer. The card dialog accepts only a button and optional text. | | Sending pauses after a language change | Check the new language in the dialog, review your message or choose a template, then send again. | | The template is in the wrong language | Check the last reported App language, the exact language override, and device synchronization. Changing the preview language does not change the recipient. | | The card has text but no review button | Check the saved App Store ID. Without an ID, newly fetched review messages have no review URL. | | The destination is wrong | Correct the app’s numeric ID. It is not the bundle identifier; numeric validation alone does not verify the listing. | | The card sent, but there is no push | Check push eligibility separately. A saved card is not confirmation of notification delivery. | | No click receipt appears | Tap from the device, use an SDK with click reporting, and check connectivity. A dashboard link click or a submitted review outside the card does not generate this receipt. | For general conversation delivery issues, see [Troubleshooting](/docs/troubleshooting).