The Call Sheet
Feature Guide
The single-lead workspace where the call happens — everything the rep needs on one screen, and every outcome logged in place.
Edgebrook Software · Sales Workspace
Work in progress — a live example is shown (anonymized)

The Call Sheet — what it is

The Call Sheet is where a prospect stops being a row on a list and becomes a conversation. It is the single screen a rep opens to make the call — and everything they need to make it well is already there, gathered from official public records before they dial: who owns the place, who to ask for by name, whether the kitchen is even open right now, the phone that rings, the website, the Google rating, the beverage privileges, and the health-inspection standing. No hunting across five different websites mid-dial; no calling a stranger. The rep opens the sheet already knowing the business — which is exactly what turns a cold dial into a warm conversation.

And the moment the call ends, its outcome is captured right here — a Note, a status, a booked Appointment, or a Callback with a date — so the pipeline updates itself as the work happens. There is no separate CRM to keep in sync and no end-of-day data entry: the record is written where the call was made, and it is instantly visible to the whole team and rolled into the manager’s reports.

That is the difference between a spreadsheet of leads and a system that actually gets worked. A rep spends the day talking to owners instead of hunting for their names; a manager sees every touch and every booking without asking; and nothing — not a promising lead, not a “try me Thursday,” not the reason a deal stalled — quietly slips through the cracks. For a small team with no admin behind them, the Call Sheet is the entire follow-up operation, on one screen.

Below the header sit the working cards: a status bar that records where the lead stands, full Details, running Notes, and the Appointment and Callback cards that turn a good call into a scheduled next step — each covered one by one below.

The full Call Sheet for a single lead — details, status bar, and the Notes, Appointment and Callback cards.

Across the top of the sheet sit four quick actions. Pre-call and Appt briefing open this lead’s two on-demand research briefings — the first for the cold call, the second for a booked meeting — each with its own guide. Home and Back to list return the rep to the Lead Builder or the Restaurant Call List.

Why this matters — everything the call needs, on one screen

The difference between a cold call and a warm one is usually just information — and the information is exactly what a rep has no time to look up mid-dial. Who actually owns this place? Are they open right now, or am I calling into a lunch rush? Who do I ask for by name? Have we talked to them before? Hunting those answers across a map, a search engine and the public record while the phone rings is how good calls get skipped.

The Call Sheet puts all of it on one screen. The owning company and its officers are right there, so the rep opens with “Hi, is Marcus in?” instead of “Hi, who owns this?” Hours are on the page, so no one calls a closed kitchen. Phone and website are one tap. The call is warmer, shorter, and far more likely to reach a decision-maker — because the rep walked in already knowing the business.

And the moment the call ends, the outcome is captured in place: a note, a status, an appointment, or a callback with a date — no separate CRM, no end-of-day data entry. For a two-person shop with no admin behind them, this is the follow-up system: the pipeline updates itself as calls happen, and nothing depends on someone remembering to write it down later.

The time it saves

A rep never leaves this screen to work a lead — the research is already here, and the result is logged where the call happened. No alt-tabbing to look up an owner or open hours, and no re-keying outcomes into another tool at the end of the day.

The cards, one by one

Status & assignment

The status bar turns the Call Sheet into living pipeline. Each of the six stages — New, Attempted, Contacted, Interested, Not interested, Appt set — is a single tap, and that tap does more than colour a pill: it updates the lead’s row on the shared Restaurant Call List and rolls into the manager’s Activity and Status reports in real time. There is no separate CRM to keep in sync and no “where did this one land?” — the current state of every prospect is visible to the whole team at once. The Assign call sheet to control sits beside it: hand a lead to a specific rep or keep it yourself, so ownership is explicit and two people never work the same bar by accident. In a two-person shop it is the entire coordination layer; on a larger team it is how a manager divides and tracks the work without a spreadsheet.

Details

This is the research a rep would otherwise spend 20–30 minutes assembling by hand across four or five separate government websites and a search engine — already gathered and laid out for the call. The trade name, address and today’s hours say who they’re calling and whether the kitchen is even open; the owning company and its officers give the exact person to ask for by name (the difference between reaching a decision-maker and being screened at the host stand); phone and website are one tap; the Google rating is a ready-made compliment to open with. Because every field is drawn from official public records it is accurate and defensible — not a scraped guess — so the rep opens each call already knowing the business, which is what turns a cold dial into a warm conversation.

📝 Notes

Every call leaves a mark. Notes is a running, timestamped history of each touch on the lead — what was said, who to ask for next time, the objection still to handle. Whoever picks the lead up next, days or weeks later, sees the whole thread and continues the relationship instead of starting cold. Nothing lives in a rep’s memory, a notebook, or a sticky note that walks out the door when they do — for an owner, that is institutional memory that stays with the business, so the pipeline’s value compounds rather than evaporating with turnover.

📅 Appointment

Booking the meeting is the whole point of the call, so it happens right here — no switching to a separate calendar. Set the date and time from the pickers, choose in-person or phone, add a location or note, and assign the rep who will take it. Saving does three things at once: it moves the lead’s status to “Appt set,” it schedules the meeting against that rep, and it unlocks the printable Appointment Briefing the rep walks in with (its own guide). One action turns a good call into a tracked, prepared meeting — and it appears instantly in the manager’s Status Report, so the team’s booked pipeline is always visible without anyone compiling it.

📲 Callback

Most calls don’t end in a meeting — they end in “try me Thursday,” a voicemail, or a not-yet. Callback captures that in one tap (No answer, Left VM, Reached, Not interested) plus a dated next step and a reason, so the follow-up is scheduled on the spot instead of riding on a rep’s memory. That is the difference between a lead that quietly goes cold and one that resurfaces at exactly the right moment. Logged outcomes also feed the team’s activity reporting, so effort is visible even when a call doesn’t book — a manager can see who is dialing and where conversations stall, not just who closed.

Setting a date or time

The date and time pickers that open from the calendar and clock icons.

Dates and times use the browser’s built-in pickers, so there is no typing, no format guessing, and no invalid entries to clean up later. Clicking the calendar icon on a date field opens a month picker; the clock icon opens a time list — a couple of clicks and the exact slot is set. It is a small thing that removes a real source of friction and error when a rep is booking mid-call, and it works identically on the Appointment and Callback cards.

Work-in-progress feature guide. Screens reflect a live build; the example prospect shown is anonymized. How the underlying data is gathered, matched, and kept current is Edgebrook’s proprietary process and is intentionally not detailed here.