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.
Where Trellus works in Quo (formerly OpenPhone)
Quo owns the phone number. Trellus owns the list.
Provides the signed-in business phone session, assigned numbers, inboxes, conversations, and its own calling controls and call history.
Chooses the list, removes malformed or inappropriate rows, selects an eligible caller number, and records the sales result in the Trellus workflow.
Maintains the uploaded queue, advances through the rows, manages the supported outbound session, and attaches the active answer to the correct list record.
The exact Quo surfaces and inputs
This is a browser workflow around Quo calling—not a claim that every Quo product surface becomes a sales queue.
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.
The rep supplies the rows. Quo Contacts, inbox filters, Calls filters, and contact exports are not automatic queue sources.
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 prospect's phone identity stays attached as calls ring, connect, or end, so the rep can tell which uploaded row produced the live answer.
An assigned Quo number is a caller-identity and permission choice. This page makes no area-code, answer-rate, spam-protection, or deliverability promise.
Six steps from upload to active answer
Sign into Quo in the browser
Use the supported web surface and confirm the correct workspace and member before loading any calling data.
Upload the Trellus list
Review duplicates, missing values, malformed numbers, international formats, list ownership, consent, and calling-hour rules.
Choose an assigned Quo number
Select from numbers the current member can use. An unassigned workspace number should not become an accidental fallback.
Start the supported call block
Trellus works separate outbound attempts from the upload. The released line limit and eligible plans remain current-account checks.
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.
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.
No fake bidirectional sync
Quo may create its own call-history entry because it placed the call. The reviewed Trellus path sends no additional sales-result update into Quo.
If every disposition and due-dated callback must live inside Quo, this is not a replacement workflow today.
Outbound list calls are not a conference call
Quo's documented group and conference calling puts multiple participants into one conversation. The verified Trellus job here is different: work separate sequential outbound attempts and keep the active call attached to the matching uploaded row.
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.
The job is a client conference, a group customer call, one-at-a-time Quick dial, or a Contact/inbox workflow that must remain entirely inside Quo.
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 verified boundary is separate sequential outbound attempts from an uploaded Trellus list using an assigned Quo number. Any broader calling mode, released line limit, and eligible 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 verified Trellus boundary 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 supported Quo and legacy OpenPhone web apps, not the mobile or desktop apps.
Test the number and list your reps will actually use
Bring a synthetic upload, the assigned Quo numbers, and the exact reporting requirement. We will show you where this workflow fits and where it stops.
