Trellus for Dialpad

Keep Dialpad calling. Add Trellus coaching in the browser.

Place the call from the Dialpad web app as usual. Trellus can recognize a supported active call and keep the visible contact name or preferred phone number with the coaching session.

Browser compatibility—not a Trellus queue or dialer replacement. Current UI, account, permissions, region, and plan must be verified before rollout.

Supported surfaceDialpad web app in Google Chrome, including supported main call-bar and embedded call views
Call placementDialpad or its connected phone provider
Trellus roleSupported coaching and session context
After-call recordComplete required work in Dialpad
Where it works

The exact Dialpad 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

Dialpad web app in Google Chrome, including supported main call-bar and embedded call views

Dialpad stays in control

Dialpad owns the inbox, contacts, dialer, messages, phone numbers, call controls, and Dialpad call records.

What Trellus adds

Trellus adds supported live-call coaching and session context without moving the rep into a separate calling queue.

Rep workflow

One native call, one clear role for Trellus

01

Open Dialpad in Chrome

Use the Dialpad web app and navigate to the contact, conversation, or number you want to call.

02

Start the call in Dialpad

Dialpad remains the system that places and controls the call.

03

Use Trellus on the active call

On a supported call view, Trellus retains the displayed name or phone number for coaching context.

04

Finish in Dialpad

Use Dialpad for messages, native call history, and any required follow-up.

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.

  • Contact name shown in the active Dialpad call bar
  • Preferred phone number when it is present
  • The supported embedded-call participant label
Current boundary
  • Trellus does not build a Dialpad call queue on this path.
  • Trellus does not claim Dialpad contact, message, disposition, note, or callback write-back.
  • Desktop and mobile Dialpad apps are outside this browser-page claim.
Concrete example

What a rep actually does

Avery opens a Dialpad contact, chooses the preferred work number, and calls from the web app. The active call bar shows the contact and number. Trellus uses that visible context for the supported coaching session while Dialpad continues to own the call and its record.
Fit check

Keep the native setup when it already works

Dialpad alone is a strong fit when

Use Dialpad alone when Dialpad Sell and its AI Sales Coach, real-time assist cards, calling, messaging, and contact workflow already match the team's process.

Review Trellus when

Review Trellus when reps place calls in the Dialpad web app and want the Trellus coaching experience without rebuilding their Dialpad workflow.

FAQ

Dialpad and Trellus

Where does Trellus work in Dialpad?

The reviewed support is in the Dialpad web app in Chrome, on supported main call-bar and embedded call views.

Does Trellus dial the number for Dialpad?

No. Dialpad places and controls the call. Trellus recognizes the supported active browser call for coaching.

What contact context can Trellus keep?

The current browser path can retain the displayed contact name and preferred phone number when Dialpad exposes them on the active call view.

Does Trellus update Dialpad after the call?

No Dialpad record write-back is promised on this compatibility path.

Does this cover the Dialpad desktop or mobile app?

No. This page is scoped to the Dialpad web app in Chrome.

Test one real Dialpad 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.