Call the Common Room Contacts your team already prioritized
Start from the current Contacts view or a Contact Segment pinned to Home. Trellus keeps the Contact, company, title, Segment, and returned phone number attached, then adds the call result to the Contact timeline.
Where Trellus works in Common Room
Common Room finds the reason. Trellus works the phone numbers.
Common Room owns the cohort
Signals, Contact data, filters, Segment criteria, sort order, and the decision that someone belongs in today's call block remain Common Room and operator choices.
Trellus works the supported call
The rep starts from the visible cohort. Trellus keeps the Contact context attached and sends a labeled answered or no-answer activity back to that exact timeline.
Trellus does not claim it interpreted the signal, scored the Contact, created the Segment, or independently chose the audience.
Three Common Room starting points
A Contacts request, a Contact Segment, and an individual profile share Contact identity—but not identical task behavior.
Trellus reuses the active Contacts request, including room, filters, sort, returned rows, cursor, and pagination boundary. It does not substitute a generic audience.
The control belongs on Segment cards labeled “Contacts,” not Organization cards. The first reviewed batch contains up to 50 Contacts sorted by oldest activity first.
Trellus can expose a one-off call for the current Contact and use the same acknowledged timeline-activity path afterward.
Mobile, work, home, and other labels can be retained. A Contact with no returned phone has no callable number in this workflow.
A returned phone value is not proof of ownership, freshness, reachability, consent, primary status, premium status, or source. Trellus does not enrich a missing number here.
From visible cohort to Contact timeline
Choose the current Contacts view or Segment
Apply the signal, tag, title, activity, phone, and ownership filters the rep can explain.
Review the exact sort and pagination
A Segment's oldest-first order may fit a follow-up queue but not a recent-intent list. Show the operator what will be called.
Inspect returned phone values
Remove duplicates and unusable values without relabeling Common Room's phone data as independently verified.
Work the supported call block
The active answer keeps Contact, company, title, Segment, room, and phone context attached.
Write the acknowledged Contact activity
The exact timeline receives an AnsweredCall or ReceivedCallNoAnswer activity with only the call fields that actually exist.
A Contact activity with explicit fields
Trellus confirms that Common Room accepted the activity before showing it as saved. If Common Room rate-limits the update, the activity can be retried.
This workflow confirms the Contact activity, but it does not reliably confirm that a Segment task was completed. Trellus does not present task completion as a supported result.
Trellus or Common Room's official Nooks path?
Use Common Room + Nooks
Choose the documented Salesforce/HubSpot-to-Nooks handoff when Nooks sequences are already the system of action and the official integration posture matters.
Review the Trellus path
Choose Trellus when the rep should start from the Common Room cohort on screen and the required in-product result is a labeled call activity on the Contact timeline.
Common Room currently documents Nooks sequence enrollment returning to Common Room, while call participation and recordings do not. The Trellus path returns the bounded Contact activity described above.
A pricing signal stays attached to the Contact
Maya pins “Pricing revisit — economic buyers” to Home. Its criteria include a recent pricing visit, the economic-buyer tag, North America, and “Has phone number.” The first fictional Contact keeps company, title, Segment, and a mobile value returned by Common Room.
The rep chooses “Interested” and adds “Send the security overview before Friday.” The Contact receives an acknowledged AnsweredCall activity with the Trellus marker, disposition, summary, available numbers, duration, and transcript link.
The release report does not say the Segment task was completed. It also does not promise a callback, DNC update, custom Segment Status, or Salesforce/HubSpot activity.
Common Room and Trellus
Can I call Common Room Contacts with Trellus?
Yes. Start from the current Contacts view, a selected Contact Segment pinned to Home, or an individual Contact profile in the supported Common Room web app.
Does Trellus use my current filters?
Yes. Trellus uses the current Contacts request as it loads more rows. If the rep changes views or filters, confirm the visible queue before calling.
What does Trellus write back?
A confirmed AnsweredCall or ReceivedCallNoAnswer activity on the exact Contact, with available disposition, summary, numbers, duration, and transcript context.
Does Trellus complete the Segment task?
No. This workflow confirms the Contact activity but does not promise Segment-task completion.
Are Common Room phone numbers verified by Trellus?
No. Trellus uses values returned by Common Room and preserves their labels; it does not independently prove ownership, freshness, reachability, consent, or primary status.
Does Trellus create callbacks or update DNC?
No. This workflow does not create a Common Room callback or update Contact-level DNC state.
Is Trellus listed in Common Room's integration directory?
No. This page describes supported in-browser Trellus behavior and does not claim a Common Room marketplace listing or partnership.
How is this different from Nooks?
Common Room's documented Nooks path sends Contacts through Salesforce or HubSpot into Nooks sequences. Trellus starts from Common Room Contact context and returns the labeled Contact activity described here.
Bring one real Contact view to the review
Show us the filters, Segment, phone fields, required Activity, and any task or CRM state. We will separate what is acknowledged today from what still needs a sandbox call.
