> ## Documentation Index
> Fetch the complete documentation index at: https://docs.appreply.co/llms.txt
> Use this file to discover all available pages before exploring further.

# Helpdesk escalation

> Automatically create support tickets from app reviews

Helpdesk escalation lets you automatically create support tickets from reviews that match certain conditions. When a review needs more than a public reply, AppReply sends it to your connected helpdesk so your support team can follow up directly.

## Supported helpdesk providers

<CardGroup cols={2}>
  <Card title="Zendesk" icon="headset">
    OAuth connection. Requires your Zendesk subdomain.
  </Card>

  <Card title="Intercom" icon="comments">
    OAuth connection. Requires a default requester email.
  </Card>
</CardGroup>

Connect your helpdesk provider in **Settings > Integrations** before creating escalation rules.

## Setting up an escalation rule

<Steps>
  <Step title="Connect your helpdesk">
    Go to **Settings > Integrations** and connect your Zendesk or Intercom account.
  </Step>

  <Step title="Create an escalation rule">
    Go to **Automations** and create a new escalation rule. This works alongside your auto-reply rules but creates a support ticket instead of (or in addition to) posting a response.
  </Step>

  <Step title="Set conditions">
    Define which reviews trigger escalation. You can use the same conditions as auto-reply triggers: rating, keywords, language, and review length.

    Common examples:

    * Rating is less than 3 stars
    * Contains keywords like "refund", "cancel", or "broken"
    * Review is longer than 200 characters (detailed complaints)
  </Step>

  <Step title="Configure ticket details">
    Set the ticket subject, priority, and tags. The subject can include template variables that pull in review metadata.
  </Step>

  <Step title="Set a cooldown period">
    Choose a cooldown in hours to prevent duplicate tickets for the same reviewer.
  </Step>
</Steps>

## Ticket details

Each escalated ticket includes the full review text and metadata so your support team has context without switching tools.

### Subject templates

The ticket subject can use template variables to include review details. This helps your support team triage tickets at a glance.

### Priority levels

Priority maps to your helpdesk's native priority system. Set higher priority for low-star reviews or reviews containing urgent keywords, and lower priority for general feedback.

### Tags

Add tags to escalated tickets to help your support team categorize and route them. For example, tag tickets by review rating, platform, or topic.

## Cooldown

The cooldown period prevents creating multiple tickets for the same reviewer within a set time window. If a user updates their review during the cooldown period, no new ticket is created.

<Tip>
  Start with a cooldown of 24 to 48 hours. This covers most cases where a user edits their review shortly after posting, while still catching genuinely new complaints later.
</Tip>

## Combining escalation with auto-replies

Escalation rules and auto-reply rules can work together. For example, you might auto-reply to a 1-star review with an empathetic response while simultaneously creating a Zendesk ticket for your support team to investigate.

This gives the reviewer an immediate public acknowledgment and ensures your team follows up privately.

<Warning>
  Make sure your support team knows that escalated tickets come from app reviews. The user may not have provided an email address, so replies through the helpdesk may not reach them directly.
</Warning>

## Next steps

<CardGroup cols={2}>
  <Card title="Triggers" icon="settings" href="/auto-replies/triggers">
    Learn more about the conditions you can use to target specific reviews
  </Card>

  <Card title="Actions" icon="bolt" href="/auto-replies/actions">
    Configure the response methods for your auto-reply automations
  </Card>
</CardGroup>