Keep Your Helpdesk. Add IrisAgent.

A helpdesk overlay is AI that sits beside the ticket in the desk you already run. You do not need a new inbox to get AI that resolves. Add IrisAgent as a helpdesk overlay for grounded assist, automation, and quality on Zendesk, Salesforce, Freshworks, or Intercom without rip-and-replace. Buyers searching for a Zendesk AI overlay or Salesforce helpdesk AI without a migration usually want this shape: one ticket timeline, one console, and AI that resolves or hands off clean.

You do not need a new inbox

A helpdesk overlay starts from the opposite assumption: the inbox is fine; the missing layer is grounded AI next to the ticket.

Most AI support projects start as a new system of record.

New workspace. New queues. New "platform" before a single high-volume intent is live on the tickets customers already open.

Operators do not fail because they lack another inbox. They fail when AI cannot sit next to the work, resolve when it can, and hand off with context when it cannot.

IrisAgent is built for the other path: keep the helpdesk. Add IrisAgent as a helpdesk overlay.

That path is not anti-AI. It is anti-migration theater. Your agents already know the console. Your macros, Guide articles, and routing rules already encode how you work. The useful move is to put grounded AI beside that work, not to ask the team to learn a second house before the first intent resolves.

The rip-and-replace trap

Rip-and-replace sounds clean in a slide.

In production it means re-training agents, migrating macros, rebuilding routing, and pausing automation until the new stack feels safe. That delay is the real cost. While the program runs, volume still arrives in the desk you already have. Customers still open tickets there. Agents still live there.

Teams that already run Zendesk, Salesforce, Intercom, or Freshworks usually need a Zendesk AI overlay, Freshworks AI support layer, or Salesforce helpdesk AI path that:

• reads the ticket and knowledge you already have

• drafts or resolves with sources cited

• writes outcomes back into the same case

• keeps humans in the console they open every day

That is a helpdesk overlay, not a second helpdesk. A helpdesk overlay earns trust when agents never leave the console they already open, and when every resolved or escalated turn writes back to the same case.

The difference shows up in the first week. Overlay teams ship a scoped intent on the desk agents already open. Rip-and-replace teams spend that week arguing about workspace structure, seat mapping, and which macros survive the move. One path produces resolved tickets. The other produces a program plan.

If your roadmap starts with "which platform do we buy," you bought a program. If it starts with "which intents can we resolve on the desk we already have this month," you bought an operator tool.

What a helpdesk overlay means

System of record stays. Tickets, macros, Guide / KB, and agent workflows remain where they are. You do not migrate the house to get AI that resolves.

IrisAgent sits beside the ticket. Marketplace install. Sidebar and automation on the desk you already run. Most teams go live in about 24 hours when the path is marketplace plus scoped intents.

Same procedures for AI and humans. Grounded answers, handoff rules, and quality rubrics should not fork into "bot world" vs "agent world." Customers should feel one standard of care whether a draft came from assist or a human finished the reply.

For the platform framing, see AI customer support software for the helpdesk you already run. For a Zendesk-specific path, see AI for Zendesk without rip-and-replace. Freshworks teams can start from the Freshworks integration. Integrations live at irisagent.com/integrations.

What a helpdesk overlay adds (not replaces)

On the helpdesk you keep, IrisAgent can add:

Start narrow. One channel. High-volume, low-risk intents. Expand after you can name failure modes.

Deeper reads: support agent assist, AutoQA, AI Agents for Text, Voice AI.

The point of the table is not feature bingo. It is a reminder that helpdesk overlay value shows up next to the ticket: resolution when policy allows, assist when a human should stay in the loop, tagging that reduces swivel, quality that does not wait for a sample week, and channels that share context instead of splitting the story.

Resolve or hand off clean

A helpdesk overlay is only useful if it knows when to stop. Helpful AI is not "always autonomous."

The useful bar is:

1. Resolve on the thread when confidence and policy allow.

2. Stop when confidence drops.

3. Hand to a human with full ticket context so the customer does not restart the story.

That is the same promise as our Short Helpful AI that stays on your helpdesk: stay on the desk; resolve or hand off clean. No second inbox required.

Warm handoff is not a soft courtesy. It is how you protect CSAT when automation should stop. If the customer has to re-explain the account, the order, and the last three replies, you did not hand off. You restarted.

Operators already know this bar from human-to-human transfers. The overlay version is the same requirement with better tooling: the AI stops, the case stays open in the same helpdesk, and the next agent sees what was tried, what was cited, and why confidence dropped. That is resolve or hand off clean in practice, not as a slogan.

Boring deploy beats demo theater

A useful week-one plan for a helpdesk overlay looks boring on purpose. The goal is resolved work on the desk you keep, not a polished demo in a blank workspace:

1. Install from the marketplace for the helpdesk you already run.

2. Connect KB + recent ticket history for the pilot intents.

3. Turn on assist or autonomous only for intents you can ground.

4. Define the handoff rule before you expand volume.

5. Review misses as content and workflow fixes, not as a monthly blame meeting.

Pay per resolved keeps the economics honest: you are buying resolved work on the desk you already run, not a year of platform seats before the first intent is live. Time-to-value depends on KB cleanliness for the pilot intents and a clear human handoff path, not on ripping out the helpdesk.

Skip the bake-off theater that starts with a blank workspace and a promise to "migrate later." Later is where macros die and agents lose trust. Start where the tickets already are, then expand the helpdesk overlay after you can name failure modes.

A boring deploy also forces honest scope. You name the intents. You name the handoff. You name what "done" looks like for week one. Demo theater skips those names because the slide is easier than the pilot. Overlay work rewards the opposite habit.

Proof on the overlay you keep (scoped)

Proof for a helpdesk overlay should stay scoped to the channels where it was measured. Named outcomes belong on the channels they were measured on:

• Dropbox: 160k email AHT minutes saved with IrisAgent on the helpdesk they already run (Dropbox story). Email / chat overlay scope only.

• Zuora: 40% fewer escalations with IrisAgent overlayed on the helpdesk (platform page). Case-tied 10x only where you already publish that framing.

Do not stretch these proofs onto Voice, Support Analyst, or AutoQA creatives. Keep them as general CS / overlay evidence here. They show what overlay can do on email and chat without a rip-and-replace program. They are not a license to invent new percentages for other surfaces.

Native keep vs overlay shop (whiteboard)

Native suite AI getting deeper is good. Use it.

The live question is not native vs nothing. It is what stays in-suite vs what still needs a helpdesk overlay:

Usually keep native

• Routing and queues the team already trusts

• Seat workflows agents live in daily

• Knowledge and ticket UI they already open

Where teams still shop overlay

• Automation across gaps the suite does not close yet

• Assist that spans ticket + adjacent channels without a second swivel

• Speed when admin hours are the scarce resource

Whiteboard before the bake-off: handoff context, channel adjacency, admin hours, and what must stay in the helpdesk so you do not rip out the house. Many teams keep native routing, QA seats, and in-suite assist where it works, and add IrisAgent for grounded resolution depth, cross-gap automation, or channel adjacency the suite does not close yet. That checklist is operations, not a brand fight.

Bottom line

Keep Zendesk. Keep Salesforce. Keep Freshworks.

Add IrisAgent as a helpdesk overlay where you need grounded resolution, assist beside the ticket, and quality on every conversation, without migrating the house. That is the Zendesk AI overlay, Freshworks AI support, and Salesforce helpdesk AI path without rip-and-replace: same desk, better resolve-or-handoff. If you only remember one line, make it this: keep your helpdesk, then add a helpdesk overlay that pays for resolved work.

Ready to keep your helpdesk and add IrisAgent? Talk through overlay scope for Zendesk, Salesforce, Intercom, or Freshworks.

**Contact us**