Trellus for Quo

Call an uploaded list through Quo

Open Trellus inside the Quo web app, load the list your team intends to call, and place separate sequential outbound attempts using a Quo number assigned to the signed-in rep.

The queue comes from a Trellus upload. It does not come from Quo Contacts, and Trellus does not post its disposition, summary, or callback into Quo.

Where Trellus works in Quo (formerly OpenPhone)

Starts in: the Quo web app
Queue: a list uploaded to Trellus
Caller number: the assigned Quo number
Calling: separate outbound list calls
Current limit: results do not write back to Quo
Division of responsibility

Quo owns the phone number. Trellus owns the list.

Quo

Provides the signed-in business phone session, assigned numbers, inboxes, conversations, and its own calling controls and call history.

The rep

Chooses the list, removes malformed or inappropriate rows, selects an caller number, and records the sales result in the Trellus workflow.

Trellus

Maintains the uploaded queue, advances through the rows, manages the outbound session, and attaches the active answer to the correct list record.

Where it works

The Quo surfaces and inputs

Quo remains the phone system; Trellus turns an uploaded list into a focused outbound calling session.

The Quo web app

Trellus works on the current my.quo.com web app and the legacy my.openphone.com web app. The Quo desktop and mobile apps are not part of this workflow.

A list uploaded into Trellus

The rep supplies the rows. Quo Contacts, inbox filters, Calls filters, and contact exports are not automatic queue sources.

Numbers assigned to the current member

Trellus presents Quo numbers owned by or assigned to the signed-in rep and removes duplicate number IDs. It stops when the rep's identity or number permission is unclear.

The active Quo call

The prospect's phone identity stays attached as calls ring, connect, or end, so the rep can tell which uploaded row produced the live answer.

Rep workflow

Six steps from upload to active answer

01

Sign into Quo in the browser

Use the web surface and confirm the correct workspace and member before loading any calling data.

02

Upload the Trellus list

Review duplicates, missing values, malformed numbers, international formats, list ownership, consent, and calling-hour rules.

03

Choose an assigned Quo number

Select from numbers the current member can use. An unassigned workspace number should not become an accidental fallback.

04

Start the call block

Trellus works separate outbound attempts from the upload. The released line limit and plans remain current-account checks.

05

Take the live answer

The active Quo call is attached to the matching Trellus row so the rep retains the list context for the conversation.

06

Keep the Trellus result separate

Record the sales outcome in Trellus. Inspect Quo's own call history separately; do not call it Trellus write-back.

What does not return

No fake bidirectional sync

Quo may create its own call-history entry because it placed the call. the Trellus path sends no additional sales-result update into Quo.

Trellus disposition
Summary or transcript link
Callback or reminder
Quo task completion
Contact enrichment
Structured sales outcome
A useful distinction

Outbound list calls are not a conference call

Quo's documented group and conference calling puts multiple participants into one conversation. The Trellus job here is different: work separate sequential outbound attempts and keep the active call attached to the matching uploaded row.

sample example
Maya signs into a sandbox Quo workspace, uploads 40 event-follow-up rows, removes unusable numbers, chooses her assigned sales number, and works the list one separate attempt at a time. One person answers. Afterward, Maya records the result in Trellus; no Trellus disposition or callback appears in Quo.
FAQ

Quo, OpenPhone, and Trellus

Is OpenPhone now Quo?

Yes. OpenPhone became Quo in September 2025. Current public pages use Quo, while some web addresses and product labels still use OpenPhone, so this page includes both names.

Does Trellus dial my Quo Contacts list?

No. The queue comes from a list uploaded into Trellus. Quo Contacts, inbox filters, and call-history filters are not queue sources in this workflow.

Can Trellus parallel dial through Quo?

Not as a current public promise. The scope is separate sequential outbound attempts from an uploaded Trellus list using an assigned Quo number. Any broader calling mode, released line limit, and plans must pass the current-account smoke test before this page claims them.

Which Quo number does Trellus use?

The rep chooses from Quo numbers owned by or assigned to the current member. Quo workspace permissions still control access.

Does Trellus write dispositions or summaries to Quo?

No. This workflow does not post a Trellus disposition, summary, transcript link, callback, or task into Quo.

Is Quo conference calling the same as parallel dialing?

No. Conference calling joins several participants in one conversation. The Trellus scope here is separate sequential outbound attempts from an uploaded list.

Does this work in the Quo mobile app?

No. This Trellus workflow works in the Quo and legacy OpenPhone web apps, not the mobile or desktop apps.

Test the number and list your reps will actually use

Bring a sample upload, the assigned Quo numbers, and the reporting requirement. We will show you where this workflow fits and where it stops.