Skip to main content

What you get

For each new support ticket, CodeRabbit summarizes the problem and customer impact, says whether it looks like a bug, expected behavior, a known issue, or needs more information, and cites docs, issues, and pull requests. It suggests severity and next steps and ends with a draft customer reply for a support engineer to review. It doesn’t send the reply or change the ticket. Pick the route by where tickets show up:

Before you start

Runs that post to Slack are billed like CodeRabbit Agent for Slack. See Who can use Automations.

Set it up

Tickets already post to a Slack channel

In the channel, run /automations and start a new automation. In Purpose, choose Investigate support tickets, in When to run, choose New channel message, and select Save and activate. The automation is active right away, without a trial run, and runs on every new top-level message in the channel. To run only on ticket messages, see Channel messages.

Trigger on new tickets in the support tool

1

Create the automation

Open Automations > Home and select Create Automation.
2

Choose the trigger

In the Trigger card, select Zendesk, Intercom, or Pylon, and choose the event: Ticket created for Zendesk, Customer started conversation for Intercom, or Issue created for Pylon.
3

Write the agent instructions

In Agent instructions, describe the triage, for example:
4

Choose the destination

In the Target card, choose the Slack channel where support engineers review the result. To also write to the ticket, select Add target, add the support tool’s connection, and say what to write in its Target instructions.
5

Save and connect the webhook

Select Save automation. The editor shows the webhook URL and setup steps for your support tool; for Pylon, that’s a Pylon trigger with a Send webhook action. Configure the webhook in the support tool. See Other providers.

Test it

Create a test ticket in the support tool, or post a test ticket message in the channel. See Test a trigger.

Check the runs

Each run is listed on the automation’s page. See Automation details. A successful run posts the summary, classification, severity, next steps, and draft reply as a reply in the ticket message’s thread, or as a new thread in the destination channel for the support tool trigger. If you added a support tool target, check the ticket for what its Target instructions asked for. If no run appears for a support tool event, check that the automation is active, that the event type matches, and that the webhook in the support tool points at the URL from the editor.

What’s next

Triage new engineering tickets

Investigate new Linear, Jira, or GitHub issues against your code.

Automation destinations

Write results back to the ticket as well as to Slack.

Knowledge Base in Slack

Teach CodeRabbit product facts so triage gets them right.