Call Log Template: Free Google Sheet With Connect Rates by Hour and Weekday

Call log template cover: a free Google Sheet with outcome codes and connect rates by hour and weekday

Publish date: Nov 16, 2026

A call log is a dated record of every dial: who you called, when, what happened and what comes next. This call log template is a free Google Sheet that keeps that record and shows which hours connect. Make a copy of the Sheet.

Each dial gets one of seven outcome codes, so the sheet counts connects and conversations for you. Its Hour by weekday tab sets your connect rate against Spona data: 344,357 dials to US professional services firms, sorted by the prospect's local hour. In that data, dials inside working hours connected about twice as often as dials outside them.

The sheet has five tabs: Instructions, Call log, Outcomes, Hour by weekday and Summary. Nine grey example rows show every formula working before you clear them.

The Extractor
The Refiner
The Verifier
The Exporter

Get thousands of leads in 4 minutes.

Stop stitching tools together.
Start with verified sales data, delivered in minutes.

SCALE SALES NOW

No contracts · No setup · No onboarding

What should a call log template include?

A call log template should include one row per dial, a fixed outcome code and the prospect's time zone. Those three things turn a list of calls into numbers you can plan with. The Call log tab has 15 columns: you fill 13 and the sheet fills two.

ColumnWhat goes in
Date, Time (yours)When you dialed, on your own clock
RepWho dialed, from a dropdown
Company, Contact, PhoneWho you called, and on which number
Number typeDirect dial, Mobile, Switchboard or Unknown
Prospect time zoneET, CT, MT, PT, AKT, HT, UK, CET, TRT or BRT
OutcomeOne of seven codes
Talk time (min)Minutes on the line, for calls that connected
Next step, Next step dateCall again, Send email, Send invite, Nurture or Do not call
NotesThe one line you will want before the next call
Local hour (prospect), WeekdayFilled by the sheet

A 9am dial from New York reaches Seattle at 6am. So the sheet converts every call to the prospect's clock, which none of the four ranking pages we read does. Number type is there for filtering: a week of Switchboard rows reads differently from a week of Direct dial rows.

The Outcome column makes the log countable. Free-text notes such as "LM" or "no ans" do not add up. A dropdown of fixed codes does.

Jesse Chan at Spona confirmed the five codes reps log in the Spona data: no answer, gatekeeper, connect, conversation and meeting booked. The sheet adds Voicemail and Wrong number, two more no-connect codes that change no rate.

OutcomeWhat it meansCounts asHubSpot call outcome
No answerRang out, busy or dropped before anyone answeredDialNo answer or Busy
VoicemailReached voicemail, with or without a messageDialLeft voicemail
GatekeeperSomeone other than the prospect answeredDialLeft live message
Wrong numberThe number does not reach the prospectDialWrong number
ConnectThe prospect answered, with no real exchangeDial, connectConnected
ConversationThe prospect discussed a need or a next stepDial, connect, conversationConnected
Meeting bookedThe conversation ended with a booked meetingDial, connect, conversation, meetingConnected

The line that matters most runs between Gatekeeper and Connect. A gatekeeper answer alone is not a connect, in this sheet or in the Spona baseline. Our post on how to get past the gatekeeper covers that step.

HubSpot's default call outcomes fold the last three codes into one, Connected. The sheet keeps them apart. A prospect who says "not now" and one who books a meeting are different results, and our cold call scripts aim at the second.

Talk time (min) separates a brush-off from a real exchange. In Cognism's cold calling report, an average call lasted 82 seconds.

Two more fields come from the rulebooks. Where the FTC's Telemarketing Sales Rule applies, call records hold the "calling number, called number, date, time, and duration" of each call, plus its disposition. For calls a rep dials by hand, one number at a time, the rule does not require those items.

The FTC also says most calls to a business are exempt, so treat the list as a checklist. The Call log holds five of these six fields. Add a column for the calling number if your team dials from several lines.

The other field is the Do not call next step. In the UK, the ICO tells B2B callers to screen against both registers, the CTPS and the TPS. Their own do-not-call list comes on top, and a business that has objected is off limits.

The US National Do Not Call Registry is for personal numbers, and business phone numbers are not covered. Your own list is what stops a repeat call to a business line. Pick Do not call once, and the sheet turns the Phone cell red if anyone dials that number again.

Sales call log template in five steps

To create a call log your team will keep, make logging faster than skipping it. Start here: Make a copy of the Sheet. Leave the grey example rows in place while you read.

  1. Set it up. On the Instructions tab, fill the yellow cells: Your time zone, Week starting (a Monday), Weekly conversation target and Fewest dials before a gap shows. Type your reps in the Reps list in column D.
  2. Log every dial. The Call log takes one row per dial, not per contact, so a second attempt is a second row. Enter Date and Time (yours), then pick Rep, Number type, Prospect time zone and Outcome. Google Sheets rejects a value that is not on a dropdown's list, which keeps the codes clean. A dated row with no rep, time zone or outcome stays yellow until you fill it.
  3. Code the result. Pick the highest code the call reached: a call that books a meeting is Meeting booked, not Conversation. Add Talk time (min) for connects, then a Next step and a Next step date.
  4. Read Hour by weekday. This tab counts your dials for each local hour and weekday. It prints your connect rate under Spona's, cell for cell. A cell turns green at or above the baseline and red below it, once it holds 50 dials. You can change that floor in Fewest dials before a gap shows.
  5. Plan on Summary. Every Friday, read the week against the baseline, by hour block and by weekday. Pick one name in the Rep cell to see that rep's week alone. Then type next week's call blocks in the last row.

The example rows cover two days and all seven codes. One dials a Pacific prospect early in the New York morning. The sheet files that call under 05:00, the prospect's local hour.

The last example row dials a number that an earlier row marked Do not call, so its Phone cell is red. Every phone number uses the fictional 555 range. With those rows, Summary shows nine dials, four connects, two conversations and one meeting.

Formulas and dropdowns run to row 200. A full-time caller fills that within a week, so copy row 200 down as far as you need. The other tabs read whole columns, and new rows count at once.

Summary's weekly counts are the same dials, connects and conversations a sales KPI dashboard tracks, so one log feeds both.

Connect rates by hour and weekday: 344,357 Spona dials

The baseline on the Hour by weekday tab is Spona data from a recent quarter. It covers 344,357 dials to US professional services firms, with all number types together.

Three definitions keep it honest. A connect means the rep reached the intended prospect, so a gatekeeper answer alone does not count. A conversation is a substantive exchange about a need or a next step. Both rates divide by every dial, and a repeat attempt is another dial.

Of those dials, 61,275 reached the prospect, a connect rate of 17.8%. Conversations followed on 34,851 dials, or 10.1%. That is 5.6 dials per connect and 9.9 per conversation.

Hours are the prospect's local time, with daylight saving applied.

Local timeDialsShare of dialsConnectsConversationsConnects per dialConversations per dial
00:00 to 07:5924,0217.0%2,2241,2369.3%5.1%
08:00 to 09:5957,30816.6%10,7396,23118.7%10.9%
10:00 to 11:5961,73417.9%11,8186,86319.1%11.1%
12:00 to 13:5967,76819.7%13,5567,47020.0%11.0%
14:00 to 15:5953,87815.6%9,8905,67318.4%10.5%
16:00 to 17:5960,92117.7%11,3366,38618.6%10.5%
18:00 to 23:5918,7275.4%1,7129929.1%5.3%
All344,357100%61,27534,85117.8%10.1%

Read the first and last rows against the five between them. Working hours here means 8am to 6pm on the prospect's clock. Inside them, 19.0% of dials connected. Outside them, 9.2% did.

That is about 2.1 times the rate. The gap holds with the mix of number types held equal. It is not a side effect of which numbers get dialed at night.

Dials inside and outside the prospect working day compared by share of dials, connect rate and dials per connect
Calling inside the working day roughly halves the dials that each connect and each conversation costs.

Inside the working day, the hours differ far less. Hourly connect rates ran from 17.6% to 20.5%, a spread of under three points. So this data names no best hour. It names a window.

Single cells move more. Inside working hours, the hour-by-weekday cells range from 14.7% to 23.9%. Each of those cells holds between 3,534 and 8,505 dials.

Heat map of connect rates for each working hour and weekday, with summed rows for the hours before 08:00 and from 18:00
No hour or weekday stands apart inside the working day, so the window matters more than the slot.

Thirteen of the 120 cells hold fewer than 500 dials, all of them outside working hours. The sheet prints those in grey italics.

Weekdays sit within 0.6 points

WeekdayDialsConnectsConversationsConnects per dialConversations per dial
Monday72,75712,7097,29417.5%10.0%
Tuesday70,14812,6277,24018.0%10.3%
Wednesday71,24412,7906,94918.0%9.8%
Thursday63,56611,1056,50317.5%10.2%
Friday66,64212,0446,86518.1%10.3%

The lowest weekday connected on 17.5% of dials and the highest on 18.1%. Conversation rates are as flat, between 9.8% and 10.3%. If your own log shows a strong Tuesday, check its dial count before you move the week around.

The baseline covers one vertical in one country. Use it as a reference line for your own log, not as a target for every market.

What is a good connect rate for B2B cold calls?

Across the studies below, 10% to 18% of dials connected when a connect means a person answered. When it means a real conversation, the range is about 6% to 10%. The gap between studies comes mostly from the definition, so read that column first.

StudyDialsWhat counts as a connectConnects per dialConversations per dial
Spona, US professional services344,357The intended prospect was reached; gatekeepers excluded17.8%10.1%
Cognism, State of Cold Calling55,701"A seller got through to a prospect"16.6% (9,247 connected)9.5% (5,265 conversations)
Belkins175,000+A live human picked up, gatekeepers included9.9%About 5.7%, our calculation (58% of connects)
Abstrakt6,220,737A dial that ends in "an actual conversation with a prospect"Not reported6.5%

Cognism publishes counts, so the percentages in its row are our division. Belkins reports a 9.9% connect rate and says 58% of connects became conversations. The 5.7% is our multiplication of the two.

Abstrakt calls its 6.5% a connect rate, but it counts only dials that end in a conversation. That puts it nearer Spona's 10.1% than Spona's 17.8%. No two rows are like for like.

What happens after the answer is steadier. In Spona's data, 56.9% of connects became conversations. Cognism's counts give 57%, and Belkins reports 58%.

So judge your own log in two steps. Dials to connects measures your list and your timing. Connects to conversations measures what your reps say next.

For daily volume, the Bridge Group's SDR survey has phone-centric teams averaging 56 dials a day and 4.6 quality conversations. Our B2B telemarketing post has the same hourly cut for switchboard dials to US manufacturers.

How do you use a call log to plan calling hours?

Sort a week of dials by the prospect's local hour and compare each block with a baseline. Then move the dials that fall outside working hours before you touch anything else. Our best time to cold call post collects the general timing studies; this section reads your own log.

Those studies disagree on the hour. Cognism's cold calling report names 10am to 11am as the most effective window. Belkins found more positive outcomes at 3 to 4 PM than in the morning. In Spona's data, the five two-hour blocks of the working day ran from 18.4% to 20.0%.

Three data sets, three answers. Your own log is the only one about your buyers.

Worked example: four SDRs, one week

This example is invented. Four SDRs in New York each make 56 dials a day, the Bridge Group average. Over five days that is 1,120 dials.

Local time (prospect)DialsConnectsConnect rateSpona connect rateGap (points)
Before 08:009088.9%9.3%-0.4
08:00 to 09:593005418.0%18.7%-0.7
10:00 to 11:591803016.7%19.1%-2.5
12:00 to 13:591202621.7%20.0%+1.7
14:00 to 15:591602716.9%18.4%-1.5
16:00 to 17:592003618.0%18.6%-0.6
18:00 and later7068.6%9.1%-0.6
All hours1,12018716.7%17.8%-1.1

Overall the team connected on 16.7% of dials, against 17.8% in the baseline. On 1,120 dials, the Summary tab prints a margin of error of 2.2 points. A gap of 1.1 points sits inside it.

The blocks tell the same story. Each holds 70 to 300 dials. On samples that size, chance alone moves a connect rate by 4 to 7 points. The widest gap in the table is 2.5 points, so one week gives no reason to reshuffle the working day.

Range bars showing how far chance moves a 17.8% connect rate at 100, 250, 500, 1,000 and 5,000 dials
A week of 250 dials cannot tell a 14% connect rate apart from a 22% one.

What the week does show is misplaced dials. The first and last rows hold 160 of them, 14% of the total. Here they are West Coast numbers dialed in the New York morning, and East Coast numbers dialed after 6pm.

Summary prices that mistake. It multiplies those dials by the gap between Spona's inside and outside rates, 9.8 points. Here that comes to about 16 more connects a week for the same effort.

Next week's call blocks

The Next week block at the foot of Summary turns the log into a plan.

Summary rowWhat it tells you
Dials outside 08:00 to 17:59 this weekHow many dials reached prospects outside working hours
Share of your dials outside 08:00 to 17:59The same count as a share of the week
Connects gained if they move into 08:00 to 17:59 (estimate at the Spona gap)Those dials times the gap between Spona's inside and outside rates
Callbacks due next weekRows with Call again as the next step and a date in the coming week
Dials for the weekly conversation targetYour target times your own dials per conversation
Call blocks for next week (type them)The plan, in your own words

Fill the last row in three moves:

  1. Move the outside dials. Sort the list by Prospect time zone and start each rep on a zone that is already at work. A New York rep opens with Eastern numbers and reaches Pacific ones after 11am.
  2. Book the callbacks. Callbacks due next week counts the rows you promised to call again. Those dials go into the blocks before any new number does.
  3. Size the week. Under 50 dials, the target row falls back on Spona's 9.9 dials per conversation. With the example rows, a target of 20 conversations needs 198 dials.

Leave changes inside the working day for later. At this team's pace, an average two-hour block reaches 1,000 dials in about five weeks. At that size chance moves a rate by 2.4 points, and a real pattern can show.

What Spona adds to a call log, and what it cannot

A call log measures the calls. It cannot fix the list behind them, and that is where Spona fits:

  • Numbers that reach the prospect. A switchboard line often puts a gatekeeper in front of the prospect. Spona's Data Enrichment adds a direct dial to a contact you already hold for 47 credits, and a mobile for 88. Spona charges only when a result returns.
  • A price you can check. One credit costs $0.008 to $0.01, depending on the plan. A direct dial then costs $0.38 to $0.47. A mobile costs $0.70 to $0.88.
  • A measured baseline. The 120 cells in the sheet come from logged dials, not from a survey of what reps remember.

And three places where something else does the job better:

  • Spona does not place or log calls. Its dialer is coming soon. Until then, a dialer or phone system that logs each dial by itself beats a sheet filled by hand. Its lead grows with volume.
  • A CRM holds the history. HubSpot logs a call on the contact's record with its outcome. A sheet keeps calls in one long list, apart from emails and deals.
  • The baseline is one vertical in one country. If you sell to UK manufacturers, the line to beat is your own log after a month of dials.
The Extractor
The Refiner
The Verifier
The Exporter

Get thousands of leads in 4 minutes.

Stop stitching tools together.
Start with verified sales data, delivered in minutes.

SCALE SALES NOW

No contracts · No setup · No onboarding

Call log template FAQ

Is there a free call log template for Google Sheets?

Yes. The call log template linked at the top of this post is free: open it and choose File, then Make a copy. It has five tabs, a dropdown for every code and formulas down to row 200. There is no form to fill in first.

How do I make a call log in Excel?

For an Excel call log template, open the Google Sheet and choose File, Download, Microsoft Excel. The sheet uses only functions Excel has, so the formulas and dropdowns survive the move. To build one from scratch, type your outcome codes in a column and select the cells that will hold outcomes. Then go to Data, then Data Validation and set Allow to List.

What is the best way to track sales calls?

Start with a shared call log spreadsheet and fixed outcome codes. Move to a CRM or a dialer when typing the rows costs more time than you can spare. A CRM keeps each call beside the contact's emails and deals, and a dialer logs the dial for you. Our CRM template keeps contacts, deals and activities in one sheet.

How long should I keep call records?

Where the Telemarketing Sales Rule applies, sellers and telemarketers keep call records for a period of 5 years. The UK GDPR sets no specific time limits: you cannot keep personal data for longer than you need it. Keep people who objected on a suppression list. If you delete them, the number comes back with the next list you load.

How does a call log differ from a call report?

A call log holds one row per dial. A call report sums up a period for a manager, and many employers require field reps to send one every week or two. Build the report from the log, not from memory. Our sales report template does that for a weekly report.

How does a call log differ from a call list?

A call list says who to call next. A call log says what happened when you did. In this sheet the two meet in the Next step column: every row marked Call again, with its date, belongs on tomorrow's call list.

Share this article

GET FREE LEADSSparkle

Similar Topics For You

see all texts