Google Sheets leads to CRM: how Telodial turns new rows into calls

Ad platforms, website forms, property portals and agencies can nearly all write to a Google Sheet, even when they cannot connect to anything else. That makes the sheet a very good place for leads to arrive and a poor place for them to be worked.

How to move Google Sheets leads to a CRM

Connect the Google Sheet once as a live lead source, map its columns to lead fields, and let the CRM pick up every new row.

Telodial does the picking up in the background and deals each new row to one caller, ready to dial from that caller’s own SIM.

• The sheet stays where leads land; nothing changes for the form tool.
• Each row gets a source tag and exactly one owner.
• Repeated numbers are dropped on the way in.

Telodial treats a sheet as a lead source rather than a file to download. On the web you add the sheet, point Telodial at the name and phone columns, map any extra columns you care about such as city or budget into built-in or custom fields, set the country for that source so numbers are read correctly, and pick which callers should receive it. From then on the sheet is checked in the background on a schedule. Each new row becomes a lead tagged with its source, so months later you can still tell which campaign produced it. Rows that cannot be imported are listed with the exact reason instead of vanishing. Each lead goes to one caller by round robin, a notification opens it in one tap, and the call goes out on that caller’s own SIM. The sheet stays exactly as it is, which keeps your agency or form tool working without any change on their side.

Setup in five steps

Step	Where	Time
Add the sheet as a live source	Telodial web dashboard, lead sources	2 minutes
Map name, number and extra columns	Column mapping screen	3 minutes
Set the country for the source	Source settings	1 minute
Choose the callers for this source	Assignment settings	2 minutes
Add a test row, check it, remove test data	The sheet, then the source’s row view	A few minutes

Times assume a clean sheet; the Telodial source settings were read on 14 October 2026.

Why a sheet beats a list of native integrations

Almost every tool can write to a sheet, while no vendor’s list of integrations covers everything a business uses. The portal your property agency set up last year, the form plug-in on your website, a marketplace export: all of them can land in a sheet, which is why scattered channels are the first problem any lead management software for small firms has to solve.

The sheet route also survives change. Switch ad platforms or add a new portal and the sheet stays put, so the CRM side needs no reconfiguring, which is one reason live sources sit at the centre of most complete telecalling software solutions.

Google Sheets layout that keeps the import clean

A few habits keep the import clean:

• One sheet, or one tab, per source. It keeps the source tag honest and lets each source go to different callers.
• Never delete rows after import. Treat the sheet as an append-only log; the working list lives in the CRM.
• Keep the phone column plain. Digits only, with or without the country code, and no extra text in the cell.
• Leave the headers alone. Renaming a mapped column is the most common reason an import quietly stops.

Google Sheets or an API endpoint: which to connect

Use an endpoint when your website or system can post each lead straight to a URL. A webhook source removes even the schedule, so a lead is in the CRM as it is created, and a REST API source can be read the same way a sheet is. The sheet route exists because many businesses cannot get developer time for that, and the difference between a scheduled check and instant is small next to the difference between a scheduled check and somebody opening a file at four in the afternoon.

Example: a Manila travel desk

Take Paolo, who runs a four-caller holiday desk in Manila. Leads arrive from a website form, a lead ad and a partner agency, about 90 a day in total, each landing in its own tab of one Google Sheet. Paolo’s agency is hypothetical.

He connects each tab as a separate source. The website form rotates across all four callers, the lead ad goes to two callers who handle package pricing, and the partner agency’s leads go to the one caller who manages that relationship.

In this illustration, each caller starts the day with a queue already filled as rows arrived, and at month end Paolo can filter leads by source tag to see which tab produced the bookings. The numbers are round figures for the example.

When a sheet connection is not worth it

If you receive five leads a week and one person calls them all, open the sheet twice a day and call; nothing here earns its setup time. The same applies if nobody on the team calls by phone. A sales process run entirely by email does not need its leads on a handset.

More detail sits on the Google Sheets lead import page, one-off files are covered on the Excel lead upload page, and why minutes matter is argued in how fast to call Facebook leads.