Trellus for Google Sheets

Power and parallel dial a Google Sheet

Trellus is a Chrome extension that adds power and parallel dialing to Google Sheets: map the phone columns once, then dial rows while results and callbacks write back to the same row. The spreadsheet, tab, row and selected number stay attached to every call.

Google authorizes access at the spreadsheet-file level, not only the tab currently open. Start with a sample copy to confirm spreadsheet permissions and row updates.

Where Trellus works in Google Sheets

Starts in: the current spreadsheet and tab
Queue: mapped rows
Phone choice: an explicitly mapped column
After the call: Trellus result columns on the row
Follow-up: callback state stays with that row

Interactive demo

Play one call inside Google Sheets.

Trellus queues your sheet rows with likely pickups first, dials four lines, coaches the live conversation (live coaching is on Business plans) and logs the notes back to your sheet. Pick a chapter or pause at any point.

Product walkthrough

Watch Trellus dial from a Google Sheet

Map your name and phone columns, review the calling list and choose power or parallel dialing. See how Trellus records call attempts and notes in the sheet.

8:08 · Setup, column mapping and call logging

Open the Google Sheets guide and chapters

Where it works

The Google Sheets surfaces Trellus uses

Use the Sheet as a focused calling list while your CRM continues to own customer records.

The spreadsheet file your team opens

Trellus identifies the current Google spreadsheet so the queue stays attached to the file the rep is actually working.

The current sheet tab

Each tab keeps its own list identity and resume point. Moving from “US prospects” to “EMEA prospects” does not treat both tabs as one queue.

Mapped rows

Choose the columns for name, company, phone types, email, and useful call context. Rows without a usable number—or rows your Trellus controls exclude—stay out of the call block.

The row behind the call

The row number and direct row link remain attached, so a rep can return to the source instead of searching for the person again.

Rep workflow

From visible row to focused call block

01

Open the right tab

Start in the spreadsheet and sheet tab that owns the list. Trellus keeps that location as the queue scope.

02

Map the columns once

Map mobile, work, home, or other phone columns alongside the identity and context your reps need during the call.

03

Review the callable rows

Confirm filters, missing numbers, wrong-number markers, and any “do not call again” state before starting.

04

Choose power or parallel

Work one number at a time or use a Trellus parallel session without exporting the list to another tool.

05

Return to the same row

Send the result or callback marker to the designated Trellus columns and keep the visible row current.

What stays attached

The row remains the unit of work

A research note, owner, source URL, or campaign label can stay visible with the phone choice. Trellus does not force every useful column into a formal CRM object first.

Spreadsheet and tab
Row number and link
Original phone value
Mapped phone label
Other row context
Separate resume point
Visible result

Use designated Trellus columns for call state

The value is not a vague “sync.” It is a small, inspectable set of fields on the same row.

Last call attempt
Last outcome
Last human reached
Total attempts
Call notes and history
Wrong-number state
Callback marker
Callback due time
Good fit

When a Sheet is the real operating surface

This workflow fits teams with a maintained call list, stable columns, clear row ownership, and a reason to keep research and results in the same file. It is less useful when the spreadsheet is an ungoverned export full of duplicates, unclear consent, and shifting columns.

Example
Dana opens “September webinar — US follow-up,” maps Mobile and Work once, and keeps an event question visible during each call. Her EMEA tab keeps a separate queue and resume point.
FAQ

Google Sheets and Trellus

Can you make calls from Google Sheets?

Google Sheets has no built-in calling. With the Trellus Chrome extension you can map a sheet's phone columns and power or parallel dial its rows, with results and callbacks written to designated Trellus columns on the same row.

Where does Trellus work in Google Sheets?

Trellus works from the current Google spreadsheet and sheet tab, using mapped rows as the calling queue. The columns, filters, permissions, and result fields should be on a sample copy.

Can Trellus power dial from Google Sheets?

Yes. Map the phone columns, review eligibility, and use the Trellus power-dialing workflow while the source row remains attached.

Can Trellus parallel dial a Google Sheet?

Yes. Trellus teams can parallel dial mapped rows. Available lines depend on the Trellus plan and calling setup, not on Google Sheets.

Can I authorize only one sheet tab?

No. Google applies Sheets access to the spreadsheet file rather than one tab inside it. Review the permission request before authorizing a real file.

What happens when I switch tabs?

The queue and resume state are tied to both the spreadsheet and the sheet tab, so work from one tab is not reused as though it came from another.

Does Trellus overwrite other columns?

The intended workflow targets designated Trellus result and callback columns on the row. Use a sample file with the real column layout to confirm result fields and unrelated values.

Does Trellus turn Google Sheets into a CRM?

No. Trellus adds a controlled calling workflow around mapped rows. It does not create CRM object permissions, activity relationships, or native task behavior.

How much does a Google Sheets dialer cost?

With Trellus, Power is $99.99 per seat per month and covers power dialing, one number at a time. Parallel dialing needs Power + Parallel at $149.99 per seat per month, which dials several numbers at once, up to five lines on eligible plans. Business pricing is custom, and you can buy a single seat online with no seat minimum. See current pricing.

Test the Sheet your team will actually call

Use a sample copy with the same columns, filters, tabs, and list shape. Check the queue, result row, and callback before reps use production data.