Chat Support Automation on New Relic, Powered by AI
Run Chat Support on top of New Relic with a DeskFerry agent. Faster execution, fewer errors, zero manual busywork.
84 chats handled overnight. Sample resolution:
Customer
“Hey — my Slack agent stopped firing after I rotated the workspace token yesterday. Anything I need to do on my end?”
Agent draft · in your tone
Hi Lara — totally normal, the new token needs a quick re-auth. I've sent a one-click reconnect link to your DeskFerry inbox; once you tap it the agent will pick up where it left off (no re-training needed).
How does New Relic work for Chat Support automation?
New Relic works for Chat Support automation by powering a DeskFerry agent that runs the workflow end-to-end inside your existing tools — no code, no custom build.
- 01
Trigger fires
The agent connects to New Relic alongside the other apps your team already uses, watches for the triggers that matter for Chat Support, and takes the next step on its own while keeping a complete audit trail for review.
- 02
Answer live @Intercom chats using @New Relic in our brand voice
AI handles common questions immediately, reducing wait times to zero for routine inquiries.
- 03
Escalate the rest with full context to @Zendesk
Teams typically see instant around the clock once the agent is in production.
- 04
You approve
You stay in control: every action is logged, confidence thresholds are configurable, and anything ambiguous is queued for a human instead of being silently auto-completed.
How you tell it what to do
Built in plain English.
You write the rule the way you'd describe it to a teammate. The agent reads the rule, breaks it into the actions it'll take, and confirms the apps it'll touch — before it does anything.
- 1Answer live @Intercom chats using @New Relic in our brand voice
- 2Escalate the rest with full context to @Zendesk
How it connects
Connect New Relic. The agent does the rest.
Claude and ChatGPT are already running on our side. You connect New Relic with one click, and chat support runs inside it.
Claude and ChatGPT run on our keys. Nothing for you to configure.
- New RelicConnect
- IntercomConnect
- ZendeskConnect
Runs on your data, in your apps.
Nothing to deploy. Nothing to maintain.
Actions
What New Relic + DeskFerry can do
Real New Relic actions your AI agent can perform automatically — no manual work required.
Create issues from alerts
Automatically open issues in New Relic when monitoring systems detect errors, outages, or performance regressions.
Manage pull requests
Post review reminders, enforce labeling conventions, and auto-merge approved pull requests in New Relic.
Trigger CI/CD pipelines
Kick off build and deployment pipelines in New Relic when code is pushed or a pull request is merged.
Track release milestones
Update milestone progress in New Relic as issues are closed and pull requests are merged toward a release.
Sync project boards
Keep issue status and priority in New Relic aligned with your project management tool in real-time.
Generate changelogs
Compile merged pull requests and closed issues from New Relic into formatted release notes automatically.
Assign reviewers automatically
Route new pull requests in New Relic to the appropriate code reviewers based on file ownership and team rules.
Monitor repository activity
Watch for commits, branch creations, and tag events in New Relic and notify the team of significant changes.
Hi Lara — totally normal, the new token needs a quick re-auth. I've sent a one-click reconnect link to your DeskFerry inbox; once you tap it the agent will pick up where it left off (no re-training needed).
Customer reports a duplicate charge; refund queued, awaiting confirmation.
Customer asking what's included on the Growth plan vs. Pro.
Human in the loop
Approve before it sends.
Every draft lands in a review queue. You approve, edit, or reject — the agent never acts on its own unless you explicitly turn that on for a workflow you trust.
Governance
Every action, with the reasoning attached.
Each step the agent takes is logged with what it did, why it did it, and which app it touched. Audit-ready, so security and compliance can sign off without backfilling.
- Lara Knight9:14 AM
Customer marked the resolution as helpful.
- Agent9:12 AM
Sent reply on ticket #9281.
Reason: Confidence above auto-send threshold; voice match passed; SLA at-risk.
- Agent9:11 AM
Drafted reply in your team's voice.
- Agent9:10 AM
Pulled customer plan, prior tickets, and account context.
- Agent9:09 AM
Triaged #9281 as the matching topic.
How it works
Get started in three steps
Step 01
Connect New Relic
Authorize New Relic and DeskFerry hooks into your issues, repos, and deployment pipelines.
Step 02
Configure Dev Workflows
Define triggers for New Relic events — new issues, PR merges, build failures — and the AI actions to take.
Step 03
Ship Faster with Less Toil
AI automates the tedious parts of your New Relic workflow. Track issues triaged, alerts handled, and developer time saved.
Start automating Chat Support for New Relic
7-day free trial. Works with the tools you already use.
FAQ
Frequently asked questions
How does New Relic data stay secure during Chat Support automation?
All data exchanged between New Relic and DeskFerry during Chat Support processing is encrypted in transit and at rest. We use OAuth tokens for New Relic access, never store raw credentials, and maintain full audit logs of every Chat Support action.
Can I customize which New Relic events trigger Chat Support actions?
Yes. You define exactly which New Relic events start Chat Support workflows — new records, status changes, messages, or custom triggers. Each trigger can have conditions so Chat Support actions only fire when your specific criteria are met in New Relic.
Can I run multiple Chat Support workflows with different New Relic triggers?
Yes. You can create parallel Chat Support workflows that respond to different New Relic events or conditions. For example, one Chat Support flow for new New Relic records and another for updated ones — each with independent rules and actions.
What happens when the Chat Support agent encounters an issue in New Relic?
When the AI hits an edge case during Chat Support processing in New Relic, it escalates to your team with full context — the New Relic record, what was attempted, and why it needs review. Your Chat Support pipeline never stalls or loses data.
How does Chat Support automation scale with increased New Relic volume?
The Chat Support agent scales automatically as your New Relic activity grows. Whether you process 10 or 10,000 Chat Support tasks per day from New Relic, the AI handles the volume without slowdowns or additional configuration.
Explore more