Trellus for VICIdial

Coach VICIdial calls without replacing the agent workflow

Keep the campaign, lead order, phone controls, and dispositions in VICIdial. Trellus can recognize a supported live browser call and retain the displayed lead name and 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.

Supported surfaceSupported VICIdial agent pages and ViciPhone or phone.php browser frames
Call placementVICIdial or its connected phone provider
Trellus roleSupported coaching and session context
After-call recordComplete required work in VICIdial
Where it works

The exact VICIdial browser surface

A platform logo is not enough. This page names the screen, what Trellus can see there, and where the workflow stops.

Start here

Supported VICIdial agent pages and ViciPhone or phone.php browser frames

VICIdial stays in control

VICIdial owns the campaign, lead queue, dialing mode, agent controls, statuses, callbacks, and reporting.

What Trellus adds

Trellus adds supported coaching and session context to the active VICIdial browser call.

Rep workflow

One native call, one clear role for Trellus

01

Enter the VICIdial campaign

Use the team's normal agent login, list, and campaign settings.

02

Let VICIdial place or connect the call

VICIdial controls the dialing mode, line, and live call state.

03

Use Trellus coaching

Trellus keeps the displayed lead name and phone number with the supported coaching session.

04

Disposition in VICIdial

Complete the required status, notes, and callback action in the native agent workflow.

Context

What stays with the coaching session

Trellus uses the contact clues available on the supported live-call view. It does not invent missing CRM context.

  • Lead first and last name from the active agent page
  • The active lead phone number
  • The supported live-call state in VICIdial or ViciPhone
Current boundary
  • Trellus does not replace VICIdial's campaign or queue.
  • Trellus does not claim to set the VICIdial status, update the lead, schedule a callback, or change list membership.
  • Self-hosted VICIdial installations vary; the exact agent and phone pages must be tested.
Concrete example

What a rep actually does

Elena receives the next lead from a VICIdial campaign. The agent screen shows the lead's first name, last name, and phone number. Trellus uses that context for the supported coaching session while VICIdial continues to control the line. Elena selects the required VICIdial status after the call.
Fit check

Keep the native setup when it already works

VICIdial alone is a strong fit when

Use VICIdial alone when its campaign controls, agent scripts, live monitoring, dispositions, callbacks, and reporting already cover the team's operating model.

Review Trellus when

Review Trellus when the organization will keep its VICIdial campaign and wants Trellus coaching on the supported browser agent experience.

FAQ

VICIdial and Trellus

Where does Trellus work in VICIdial?

The reviewed support covers supported VICIdial agent pages and embedded ViciPhone or phone.php call frames.

Does Trellus replace the VICIdial campaign dialer?

No. VICIdial keeps the campaign, lead queue, dialing mode, and call controls.

What lead context can Trellus keep?

The supported path can retain the first name, last name, and phone number displayed on the active agent page.

Does Trellus set the VICIdial disposition?

No public write-back claim is made. Agents complete statuses and notes in VICIdial.

Will this work on every self-hosted VICIdial setup?

Not without testing. Customized domains, themes, phone frames, and agent pages must pass a current smoke test.

Test one real VICIdial call view

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.