Integrations
Routing Rules
Route feedback to different integrations based on conditions
Routing Rules
Routing rules let you send different feedback to different destinations based on conditions like category, rating, or custom fields.
How It Works
When feedback arrives:
- Rules are evaluated in order
- First matching rule determines the destination
- If no rules match, default integration is used
Creating Rules
- Go to Integrations → Routing Rules
- Click "Add Rule"
- Configure:
- Name: Descriptive name
- Condition: When this rule applies
- Action: Where to send the feedback
Conditions
Field Types
| Field | Description | Operators |
|---|---|---|
category | Feedback category | equals, not equals |
rating | User rating | equals, less than, greater than |
pageUrl | Page URL | contains, starts with, equals |
message | Feedback text | contains |
metadata.* | Custom metadata | equals, contains |
Operators
| Operator | Description |
|---|---|
equals | Exact match |
not equals | Doesn't match |
contains | Includes substring |
starts with | Begins with |
less than | Numeric comparison |
greater than | Numeric comparison |
Example Rules
Route Bugs to Engineering
IF category equals "bug"
THEN send to #engineering-bugs (Slack)Urgent Low Ratings
IF rating less than 3
THEN send to #urgent-feedback (Slack)
AND email support@company.comFeature Requests to Product
IF category equals "feature"
THEN send to #product-ideas (Slack)VIP Users
IF metadata.plan equals "enterprise"
THEN send to #vip-feedback (Slack)
AND email vip-support@company.comCheckout Issues
IF pageUrl contains "/checkout"
THEN send to #checkout-bugs (Slack)Rule Priority
Rules are evaluated top-to-bottom. Drag to reorder:
1. IF rating < 2 → #urgent (highest priority)
2. IF category = bug → #bugs
3. IF category = feature → #features
4. Default → #feedback (catch-all)The first matching rule wins. Place more specific rules above general ones.
Multiple Actions
A single rule can trigger multiple actions:
IF rating equals 1
THEN:
• Send to #critical-feedback (Slack)
• Email support@company.com
• POST to webhook endpointCombining Conditions
Create complex rules with AND/OR:
All conditions must match (AND)
IF category equals "bug"
AND rating less than 3
AND metadata.plan equals "pro"
THEN send to #priority-bugsAny condition matches (OR)
IF category equals "bug"
OR rating less than 2
THEN send to #needs-attentionTesting Rules
Before saving, test your rules:
- Click "Test Rule"
- Enter sample data
- See which rules would match
Default Behavior
If no rules match:
- Feedback goes to your default integration channel
- If no default is set, no notification is sent
- Feedback is still stored in your inbox
Managing Rules
Edit Rule
- Click on the rule
- Modify conditions or actions
- Save
Disable Rule
- Toggle the rule's "Enabled" switch
- Rule is skipped during evaluation
Delete Rule
- Click the ⋯ menu
- Select "Delete"
- Confirm
Best Practices
- Start simple: Begin with 2-3 rules
- Use default fallback: Ensure nothing gets lost
- Test thoroughly: Use the test feature
- Review regularly: Adjust as your needs change
- Document purpose: Use descriptive rule names
Troubleshooting
Feedback Going to Wrong Channel
- Check rule order (priority)
- Verify condition values match exactly
- Test with sample feedback
- Check for conflicting rules
No Notifications
- Verify at least one rule matches
- Check default integration is configured
- Confirm integrations are connected