Start here
Supported Genesys Cloud web domains, including mypurecloud.com, genesyscloud.com, and pure.cloud
Keep Genesys Cloud as the contact-center system. On supported Genesys Cloud browser domains, Trellus can recognize an active interaction and retain the displayed customer name or phone number 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. Genesys Cloud 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 Genesys Cloud web domains, including mypurecloud.com, genesyscloud.com, and pure.cloud
Genesys Cloud owns queues, campaigns, routing, interaction controls, scripts, wrap-up codes, callbacks, and the contact-center record.
Trellus adds supported coaching and session context to the live browser interaction.
Use the supported browser domain and enter the queue or interaction flow assigned by the contact-center team.
Genesys remains responsible for routing, phone controls, and the interaction lifecycle.
Trellus recognizes the supported active interaction and keeps the displayed customer name or phone with the session.
Apply the required Genesys wrap-up code, notes, and callback handling in Genesys Cloud.
Trellus uses the contact clues available on the supported live-call view. It does not invent missing CRM context.
Use Genesys Cloud alone when Genesys Cloud Copilot—including Agent Copilot—plus quality management, scripts, analytics, and contact-center controls already meets the need.
Review Trellus when the team will keep Genesys Cloud for routing and wrap-up but wants Trellus coaching on the supported web experience.
The reviewed support covers active calls on supported Genesys Cloud web domains. It is not a blanket claim for every embedded or desktop client.
No. Genesys Cloud continues to own routing, queue membership, campaign rules, and call controls.
Trellus can retain the displayed customer name and phone number from the supported active interaction.
No public write-back claim is made. Agents complete wrap-up in Genesys Cloud.
Not through this compatibility path. Use the team's configured Genesys callback 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.