Trellus for Common RoomCall the Common Room Contacts your team already prioritized
Start with the Contacts view or Segment your team already trusts. Trellus turns those phone-ready Contacts into a power or parallel dialing session, keeps the company and buyer context beside the conversation, and saves the result to the right Contact timeline.
Your Common Room-to-call flow
Common Room finds the reason. Trellus works the phone numbers.
Build the audience in Common Room
Use signals, Contact data, filters, Segment criteria, and sort order to decide who belongs in today’s call block.
Run the call block with Trellus
Start from that visible cohort, keep the Contact context attached, and return a labeled answered or no-answer activity to the right timeline.
Three ways to start a Common Room call
Use the surface that already matches the rep’s job: a live Contacts view, a saved Contact Segment, or one Contact profile.
Trellus carries the active room, filters, sort, returned rows, and pagination forward as more Contacts enter the call block.
Start from Segment cards labeled Contacts. Trellus loads up to 50 Contacts in the first batch, ordered by oldest activity first.
Make a one-off call from a Contact profile and use the same timeline-activity write-back afterward.
Mobile, work, home, and other labels can stay attached. Contacts with at least one phone value can enter the calling queue.
Trellus uses the phone values Common Room returns, preserves their labels, and keeps that source clear during the call.
From visible cohort to Contact timeline
Open the right Contacts view or Segment
Use the signal, tag, title, activity, phone, and ownership filters your team already relies on.
See the queue before dialing
Trellus carries the current sort and paging context into the session, so reps can see which Contacts are coming next.
Choose the best available phone
Keep Common Room’s mobile, work, home, and other labels close while removing duplicate or unusable values.
Work the power or parallel call block
Contact, company, title, Segment, room, and phone context stay attached when someone answers.
Save the result to the Contact
The right timeline receives an AnsweredCall or ReceivedCallNoAnswer activity with the call fields that exist.
The call history lands on the right Contact
Trellus waits for Common Room to accept the activity before showing it as saved. Rate-limited updates can be retried instead of disappearing from the rep’s flow.
A pricing signal stays attached to the Contact
Maya pins a fictional Pricing revisit — economic buyers Segment to Home. Its criteria include a recent pricing visit, the economic-buyer tag, North America, and Has phone number. The first Contact enters the call block with company, title, Segment, and mobile context attached.
The rep chooses Interested and adds Send the security overview before Friday. The Contact receives an saved AnsweredCall activity with the Trellus marker, disposition, summary, available numbers, duration, and transcript link.
Common Room power and parallel dialing with Trellus
Can I call Common Room Contacts with Trellus?
Yes. Start from the current Contacts view, a Contact Segment pinned to Home, or an individual Contact profile in the Common Room web app.
Does Trellus keep my current filters?
Yes. Trellus carries the current Contacts request forward as it loads more rows. If the rep changes filters or views, the visible cohort becomes the new source.
Which phone fields can I use?
Trellus can retain mobile, work, home, and other labels returned by Common Room. A Contact needs at least one returned phone value to enter the callable queue.
What does Trellus write back?
An saved AnsweredCall or ReceivedCallNoAnswer activity on the right Contact, with the available disposition, summary, numbers, duration, and transcript context.
Turn one Common Room cohort into a live call block
Bring the Contacts view, Segment, and timeline fields your reps use now. We’ll show you how Trellus works on that current flow.
