Trellus for ClayPower and parallel dial the contacts in your Clay table
Open the Clay view your team has already enriched and filtered. Trellus turns its callable rows into a power or parallel dialing queue, keeps the research beside every conversation, and writes the call result back to the same row.
Your Clay-to-call flow
Watch a Clay table become a calling queue
This four-minute walkthrough starts in Clay Tables and shows where Trellus enters the rep’s day. You’ll see the table context stay close while the call block runs.
Trellus dialing walkthrough for Clay · 4 minutes
The table stays the source of truth
The current view decides which rows enter the call block. The research your team assembled in Clay stays with the person instead of disappearing into an exported list.
The visible view supplies the source record IDs and their order. Change the view, and the audience changes with it.
At least one phone column is required. Name, title, company, industry, URLs, and other useful row fields can stay beside the active call.
Each queue row keeps its Clay record ID, table, row position, source URL, original fields, and mapped values attached to the active call.
Rows with a Trellus callback title and due date can return as follow-up work. The current callback scan covers up to 250 records.
Map the column your reps actually trust—whether it is called Mobile, Direct dial, or the result of a provider waterfall. Trellus can use more than one mapped phone field.
One view. Five steps. No list handoff.
Qualify the audience in Clay
Enrich, score, and filter the records into the view your reps should call today.
Map phone and research columns
Choose the phone fields plus the company, title, signal, and research columns that make an answer useful.
Start a power or parallel session
Trellus builds the queue from callable rows. Rows marked Do not call again (Trellus) stay in Clay without entering the call block.
Talk with the row in view
The person, phone choice, company context, and Clay research stay attached while the conversation is happening.
Let the result land on the same row
Trellus records the outcome and attempt, then adds the available summary, history, wrong-number state, or callback date.
Every completed call leaves useful context behind
Trellus updates named fields on the source row, so the next rep can see what happened without hunting through a second system.
Seventeen rows, two phone fields, one source of truth
Maya filters a fictional event table to 17 US accounts with verified mobile numbers and an ICP score above 80. She maps Mobile, Direct dial, and the research columns. One do-not-call row stays out of the queue; one known-wrong mobile leaves the direct line available.
Trellus writes Interested, the attempted and reached-human times, a history line, and the available summary to that same row. A Tuesday 10:00 follow-up is saved with the row and can return as callback work.
Set up the Clay call block in four clear steps
Choose where callbacks live
Save the callback title and due date on the Clay row, or connect the assigned CRM task workflow your team already uses.
Keep downstream automations explicit
Trellus writes named result fields to Clay. Your Clay-to-CRM automation can keep using those fields as its trigger.
Confirm the result columns once
Run one sample call through the required result columns, then scale the same mapping across the full view.
Keep calling controls current
Wrong-number and do-not-call fields stay visible on the source row and continue to follow the team’s process.
Clay power and parallel dialing with Trellus
Can I call directly from a Clay table?
Yes. Trellus uses the current Clay table view as the source list, provided at least one phone column is mapped.
Do I need to export the table first?
No. Trellus reads the current view and returns result fields to those source rows, so the calling block can stay connected to the table.
Which Clay columns should I map?
Start with one or more phone columns. Add the name, title, company, industry, signal, and research fields your reps want beside the call.
What does Trellus write back to Clay?
The core fields are outcome, attempted time, and call history. Reached-human time, summary, wrong-number state, do-not-call state, and callback fields are added when the corresponding event occurs.
How do callbacks work?
Trellus stores a callback title and due date on the source row, then can surface that row again as follow-up work. It does not create a native Clay Sequencer task.
Can my existing Clay automation send the result to a CRM?
Potentially, but that is a separate Clay automation. Test its trigger, field mapping, permissions, and failure behavior with the Trellus result columns your team plans to use.
Does Trellus remember wrong numbers and do-not-call rows?
Yes. Trellus can store wrong-number and Do not call again (Trellus) state in dedicated Clay columns and use that state when rebuilding the queue.
Try Trellus on a Clay view you already trust
Bring the phone fields, research columns, and result fields your team uses now. We’ll show you the call block on that setup.
