Start here
Supported Five9 Agent and integrations browser routes under five9.com/clients
Five9 keeps the campaign, routing, agent controls, and disposition workflow. Trellus can recognize the supported live browser call and retain useful contact and campaign context for coaching.
Browser compatibility—not a Trellus queue or dialer replacement. Current UI, account, permissions, region, and plan must be verified before rollout.
Available name or phone context stays with the supported live call. Five9 remains the calling system.
A platform logo is not enough. This page names the screen, what Trellus can see there, and where the workflow stops.
Supported Five9 Agent and integrations browser routes under five9.com/clients
Five9 owns the campaign, contact-center queue, routing, call controls, wrap-up, disposition, callback policy, and system record.
Trellus adds supported coaching and session context to the active Five9 browser call.
Join the assigned campaign or queue in the supported browser client.
Five9 controls the dial, connection, mute, hold, transfer, and end-call state.
Trellus attaches the available contact, phone, campaign, and session context to the supported live call.
Choose the required Five9 disposition, notes, and callback behavior in the native agent workflow.
Trellus uses the contact clues available on the supported live-call view. It does not invent missing CRM context.
Use Five9 alone when Five9 AI Agent Assist, real-time guidance, transcription, summaries, contact-center controls, and quality workflow already cover the team's requirements.
Review Trellus when Five9 remains the contact-center system but the team wants the Trellus coaching experience on supported browser calls.
The reviewed support covers specific Five9 Agent and integrations browser routes under five9.com/clients. Five9 interface variants require rollout testing.
No. Five9 continues to own the campaign, queue, routing, and call controls.
The supported path can retain the displayed name and phone, campaign context when available, and the selected disposition or visible interaction notes for the Trellus session.
No public write-back claim is made. Agents should complete required wrap-up in Five9.
Not through this compatibility path. Keep callback scheduling in the team's Five9 workflow.
Bring the browser route, account role, phone setup, and after-call requirements your reps use. We will show where Trellus fits and where the native platform stays in control.