Trellus for Google Sheets

Turn a Google Sheet into a controlled calling queue

Map the columns your team already uses, then power or parallel dial eligible rows while keeping the spreadsheet, tab, row, selected number, and follow-up context attached.

Google authorizes access at the spreadsheet-file level, not only the tab currently open. Test permissions and row updates on a synthetic copy before rollout.

Where Trellus works in Google Sheets

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

Watch Trellus dial from a Google Sheet

This short Trellus walkthrough shows the in-Sheet calling experience. Use it to understand the flow, then test your own column layout, filters, permissions, and result fields on a synthetic copy.

0:34 · Published on the Trellus YouTube channel September 28, 2025

Official Trellus product walkthrough. The video demonstrates the workflow; it does not replace a permission and row-update test for your Sheet.

Where it works

The Google Sheets surfaces Trellus uses

This is a calling workflow for a maintained Sheet—not a claim that the spreadsheet becomes a CRM.

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, eligible 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 exact 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.

Access boundary
Google Sheets permissions apply to the spreadsheet file, not a single tab. Trellus should show the exact access request before a team authorizes production data.
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 boundary.

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 an eligible Trellus parallel session without exporting the list to another tool.

05

Return to the same row

Send the supported result or callback marker to the designated Trellus columns, then verify the visible row before broad rollout.

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
Rollout check
Before reps use a real calling list, confirm that a result lands on the intended row, unrelated columns remain unchanged, and a callback resurfaces once on the correct tab.
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.
Not a native CRM task
A Google Sheet row does not gain CRM permissions, relationships, activity objects, or task completion semantics. Teams that need those controls should compare the CRM integrations in the directory.
FAQ

Google Sheets and Trellus

Where does Trellus work in Google Sheets?

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

Can Trellus power dial from Google Sheets?

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

Can Trellus parallel dial a Google Sheet?

Eligible 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 exact 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 exact row. Test the real column layout on a synthetic file before rollout and confirm unrelated values remain unchanged.

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.

Test the Sheet your team will actually call

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