Power dial an uploaded list through Nextiva
Bring the outbound list to Trellus, then work it one number at a time through the supported Nextiva browser softphone controls. Nextiva remains the phone system and uses the account's default number.
Where Trellus works in Nextiva
A list workflow around Nextiva—not a new Nextiva campaign
Use Trellus for an external list block
Choose this path when Nextiva is already the phone system, the audience arrives as a file, one-at-a-time pacing is appropriate, and Trellus-local progress covers the immediate job.
Use Nextiva Contact Center for native campaigns
Start there when Nextiva must own the campaign, Progressive or Predictive Dialing, ACD/routing, list policy, reporting, and downstream follow-up state.
If Nextiva's native campaign path already fits the list, pace, routing, and reporting requirements, Trellus does not remove a meaningful bottleneck.
The exact Nextiva browser workflow
Trellus works with a signed-in Nextiva browser softphone on supported *.nextos.com pages. The list itself starts in Trellus.
The file supplies the name, phone, company, and short call context. Nextiva Contacts, CRM views, and Contact Center campaigns are not imported.
Trellus uses the available softphone controls in the signed-in web session. This page does not promise support in Nextiva's desktop or mobile apps.
The workflow uses the account's Default Number. It does not offer a number pool, local presence, regional matching, or a separate caller-ID picker.
Start, end, mute/unmute, and keypad input are included. Hold, transfer, notes, and other Nextiva controls remain outside this Trellus workflow.
NextivaONE is the current user-app brand while NextOS still appears in some web addresses and account surfaces. Confirm that Trellus appears on the page your reps use before a call block.
One row finishes before the next begins
Upload the list into Trellus
Use fictional data first and review duplicates, malformed values, missing numbers, consent, and ownership.
Confirm the signed-in Nextiva surface
Record the host, product, plan, user role, region, browser, and extension build before production use.
Confirm Default Number
The displayed default identity must be the caller number the team intends to use. No alternate-number picker is promised.
Place one list call
Trellus fills the target and invokes the supported call control. The next row waits until the current attempt finishes.
Use supported in-call controls
End the call, mute or unmute, and use the keypad when required. Test missing-softphone and expired-session failures.
Record the result in Trellus
The disposition advances local list progress. Inspect Nextiva's own call history separately instead of calling it a Trellus sync.
The result stays in the Trellus list
Choosing a Trellus disposition advances the uploaded list. It does not create a matching disposition or note inside Nextiva.
Nextiva may create its own call-history record because it placed the call. That history is created by Nextiva, not by Trellus result sync.
A two-hour reactivation block from a research export
Sam's team uses Nextiva, but today's 42 fictional accounts came from a market-research project rather than a native campaign. Sam uploads “August reactivation — test” to Trellus and confirms the account's default number.
Jordan does not answer. The rep ends the call, selects “No answer” in Trellus, and only then advances to the second row. When the next person answers and asks for menu input, the rep uses the reviewed keypad control.
Trellus shows local progress and results. The report does not say Trellus synced a Nextiva disposition, summary, task, callback, DNC state, recording, or transcript.
Nextiva and Trellus
Can Trellus power dial through Nextiva?
Yes. Trellus works through an uploaded list one number at a time while the rep is signed in to the supported Nextiva browser softphone on a *.nextos.com page.
Does Trellus import Nextiva Contacts?
No. The queue comes from a list uploaded into Trellus, not a Nextiva Contacts view, CRM list, or Contact Center campaign.
Is this parallel or predictive dialing?
No. The Nextiva workflow described here is one number at a time. It does not add parallel, predictive, or progressive dialing.
Which Nextiva number does Trellus use?
It uses the signed-in account's Default Number. It does not offer a selectable number pool or local-presence behavior.
What does Trellus write back to Nextiva?
Nothing after the call. Trellus does not post its disposition, summary, task, callback, DNC state, recording, or transcript into Nextiva.
Does Nextiva offer automated dialing?
Yes. Nextiva Contact Center lists Progressive and Predictive Dialing. Teams that need Nextiva to own the campaign, routing, and reporting should evaluate that option.
Does Trellus use Nextiva SIP trunking?
No. This workflow uses the signed-in Nextiva browser softphone.
Is Trellus an official Nextiva marketplace partner?
This page does not claim a marketplace listing or certified partnership. It describes the supported in-browser Trellus workflow.
Bring the real list and Nextiva workflow
Show us the source file, the Nextiva page your reps use, the expected caller number, and the required post-call state. We will separate the supported Trellus workflow from Nextiva Contact Center campaign needs.
