Alert destinations

Connect a chat app

• Slack: click Connect on the Slack row. Slack asks you to approve AppReply and choose a workspace channel. When you approve, you return to the Channels page with the new channel added. Alerts in a channel connected this way have Reply from Slack and Reply in AppReply buttons under each review: see Reply to a review from Slack.
• Discord: click Connect on the Discord row, then choose a server channel and approve. You return to the Channels page with the new channel added. The Discord row appears only when Discord installs are available. If you don’t see it, use the webhook steps in the Discord section.
• Microsoft Teams: click Install on the Microsoft Teams row. This opens the AppReply app in Microsoft Teams. Add it to the team, channel or chat where you want alerts. The app posts a setup message there: select Finish setup in AppReply, sign in, check that the Microsoft tenant ID shown is your own, and click Connect next to the organization that should send alerts to that conversation. The setup link expires after 15 minutes. If it expires, install the app again in Teams to get a new link.

Slack

Reply to a review from Slack

Before you start

• A channel connected with the Slack app. Only channels added with Connect on the Slack row of Connect a chat app get the Reply from Slack and Reply in AppReply buttons. A channel added with Add channel and a pasted webhook URL keeps its link that opens the review in AppReply. A channel that was already connected with the Slack app needs nothing new: its alerts get the buttons by themselves.
• The channel in an alert rule. Add it under Alerts > Alert rules if it is not in one yet.
• An AppReply account for each person who replies. They must be a member of the AppReply workspace that sent the alert (a pending invitation does not count) and be in the Slack workspace that connected AppReply. Every member role can reply.

Link your Slack account

1

Press Reply from Slack on any review

In Slack, press Reply from Slack on a review in an AppReply alert. The first time, a message that only you can see asks you to link your accounts. Press Link Slack account.

2

Continue with Slack

Your browser opens AppReply. Sign in if asked. The page Link your Slack account names the AppReply account you are signed in to. Press Continue with Slack.

3

Accept in Slack

Slack shows Sign in to AppReply Alerts with Slack. Press Accept and Continue. Slack skips this screen if you accepted it before.

4

Go back to Slack

AppReply confirms that your Slack account is linked. Your Slack name and workspace are listed under Linked Slack accounts. Press Back to Slack to open the Slack app, then press Reply from Slack on the alert again. The page also says “You can close this tab.” To link a different Slack account, use the small Link another Slack account link.

Reply to a review

1

Press Reply from Slack

Press Reply from Slack under the review. A reply box appears at the bottom of the channel, marked Only visible to you. It shows the review, the store’s length limit and the AppReply account you reply as.

2

Write the reply and press Send reply

Type the reply in Your reply and press Send reply. Cancel removes the box.

3

Check that it was queued

The box turns into “Reply queued. AppReply posts it to Google Play in the next few minutes, as a reply by” your name followed by (Slack), with an Open in AppReply button.

Limits

• Your own apps, connected to their store. A reply needs the store’s API. Reviews of competitor apps you track, and of your own apps with no store connection, have no Reply from Slack button.
• The store’s length limit: Google Play 350 characters, App Store 2,000, Samsung Galaxy Store 700, Huawei AppGallery 800, RuStore 500. A longer reply is refused and your text stays in the box, so you can shorten it and send again.
• One reply per review. A review that AppReply knows has a reply, queued or published, can’t be answered again from Slack. To change a reply, press Open in AppReply.
• Google Play reviews you already answered. In an alert that comes straight from Google Play, a review that already shows a developer reply has no Reply from Slack button, because a second reply would replace the first. It says Already replied and shows only Open in AppReply. AppReply only knows what Google Play showed when the alert was made. It fetches Google Play reviews every six hours, so a reply posted in Play Console after the alert and before the next fetch is not known to AppReply, and a reply from Slack would replace it on the store.
• Countries you don’t monitor. A Google Play review from a country the app does not monitor in AppReply has no Reply from Slack button in an alert that comes straight from Google Play. It says Country not monitored and shows only Open in AppReply. In other alerts, pressing Reply from Slack on such a review is refused with a message.
• No editing or deleting from Slack, and no drafts written for you. The box is for typing a reply.
• Your plan’s replies. Each reply from Slack counts towards your plan’s replies for the period, like any other reply.
• The box lasts 30 minutes. After that, press Reply from Slack again.
• Older alerts sent before replies from Slack were available have no buttons. Alerts sent before the current layout have a single Reply button beside each review, which works like Reply from Slack.
• Slack does not show when a reply is published or fails. If the store refuses the reply, the failure shows on the review in AppReply, and the Slack alert keeps Reply queued by.
• Shared channels. People who are in the channel from another Slack workspace can’t reply from Slack. They can open the review in AppReply instead.
• Two-step sign-in. If your AppReply account uses a second factor, the link page asks you to verify it in the browser before you can link Slack.
• Reply in AppReply and Open in AppReply open the Reviews feed on the dates that contain the review, with that review in focus.

Messages you may see

Unlink, leave or reconnect

• To unlink, link your Slack account to a different AppReply account from the Link your Slack account page, or remove the app’s access for yourself in Slack. AppReply then forgets the link.
• Removing a person from the AppReply workspace stops their replies from Slack at once, whether they are linked or not.
• When Slack deactivates a person’s account, AppReply forgets their link. The channel’s alerts keep running.
• If the Slack app is removed from your Slack workspace, the channels stop and so do replies. After you connect Slack again, each person links again.

Questions about replying from Slack

Discord

Telegram

Microsoft Teams

Email

Unsubscribe links

• Unsubscribe from this alert (or Unsubscribe from this report) stops that one rule’s emails to that address.
• Unsubscribe from all emails from your organization stops every alert and summary email your organization sends to that address.

Custom webhook

Payload format

{
  "event": "review_alert_grouped",
  "timestamp": "2026-04-08T12:00:00Z",
  "rule": {
    "id": "...",
    "name": "Low rating alert"
  },
  "application": {
    "id": "...",
    "name": "My App",
    "developer_name": "My Company",
    "photo_url": "https://...",
    "platform": "google_play"
  },
  "reviews": [
    {
      "id": "...",
      "author_name": "Anna",
      "rating": 2,
      "text": "Die App stürzt beim Öffnen ab.",
      "title": null,
      "language": "de",
      "country": "de",
      "created_at": "2026-04-08T11:55:00Z",
      "app_version": "3.4.1",
      "platform_url": "https://...",
      "translated_text": "The app crashes when opening.",
      "translated_title": null,
      "translation_language": "en",
      "original_text": "Die App stürzt beim Öffnen ab.",
      "is_update": false,
      "previous_rating": null,
      "previous_text": null,
      "previous_title": null
    }
  ],
  "organization": {
    "id": "...",
    "name": "My Org"
  },
  "dashboard_url": "https://..."
}

• text and original_text are always the review as written. original_text is always present and always equals text.
• translated_text, translated_title, and translation_language are null when the review has no translation into the rule’s language. That is the case when Translate reviews in alert messages is off, when the review is already in that language, or when translation failed. The keys are always present.
• is_update is true when the review is an edit of an earlier review, and previous_rating, previous_text, and previous_title then carry the earlier values. For a review that is not an edit, these fields can be false or null, or left out.
• Some fields (for example developer_name, photo_url, app_version, device, thumbs_up, and thumbs_down) are left out when the store does not provide them.
• Earlier versions could include an overflow_count field. It has been removed.

Delivery and failure handling