Skip to main content
Raya - Customer Service

Escalation Rules

Configure when and how Raya hands conversations to human teammates, with topic-based routing and priority controls.

5 min readUpdated 2026-02-01

What It Is

Escalation rules are a rules engine that determines when Raya should route a conversation to a human teammate. You define the topics, keywords, and conditions that trigger an escalation, and Raya follows them across all channels (chat, email, WhatsApp, social). Well-configured escalation rules ensure that sensitive or complex issues reach the right person fast, while routine questions stay with Raya.

How It Works

Raya evaluates escalation rules in three steps for every incoming message.

  1. 1

    Classify the message

    Raya analyzes the customer's message to identify the topic, sentiment, and intent. She uses natural language understanding, not just keyword matching.

  2. 2

    Check rules

    Raya compares the classification against your escalation rules. Rules are evaluated in priority order, and the first matching rule wins.

  3. 3

    Action on match

    When a rule matches, Raya forwards the conversation to the specified destination (email address, Slack channel, or CRM queue). She includes the full conversation history and her classification summary.

Rule Configuration

Each escalation rule has the following fields.

FieldDescriptionExample
match_topics_anyList of topics that trigger this rule (match any one)["billing", "refund", "cancellation"]
priorityRule evaluation order (lower number = higher priority)1 (highest), 2, 3, etc.
forward_toDestination for escalated conversationsfinance@company.com, #slack-channel
custom escalation promptOptional message Raya sends to the customer when escalating"I'm connecting you with our billing team."
stop processingWhether Raya stops replying after escalationtrue (default) / false

Example Rules

Below are common escalation configurations for a support team.

TopicPriorityForward To
Billing, Refund1finance@company.com
Outage, Downtime1eng-oncall@company.com
VIP Customer2vip-support@company.com
Legal, Compliance1legal@company.com

Limitations

Escalation rules evaluate topics and intent, not exact keyword matches. Raya may classify a message differently than expected if the customer uses indirect language. Review the escalation log regularly and adjust topic lists as needed. Rules do not support time-based conditions (e.g., "escalate after 5 PM") at this time. Use business hours settings in the widget for time-based behavior.

Frequently Asked Questions

Can I escalate to a Slack channel instead of an email address?
Yes. Set the "forward_to" field to a Slack channel (e.g., #billing-escalations). Raya posts the conversation context and classification directly in the channel. Requires the Slack integration to be connected.
What happens if no escalation rule matches?
Raya handles the conversation herself using the knowledge base and policy instructions. She only escalates when a rule explicitly matches. If you want a catch-all rule, add a low-priority rule with a broad topic list.
Can Raya escalate a conversation to Adam for sales follow-up?
Yes. Raya supports auto-handoff to Adam. When she detects a sales opportunity (purchase intent, pricing questions, upgrade interest), she can route the conversation to Adam for sales follow-up. Configure this in your escalation rules with a "sales" topic.

Related Articles

Still need help?

Contact our team
Escalation Rules | Help Center | Teammates.ai