The problem this solves
A calling block succeeds or fails in the first ten seconds of each call, and those seconds depend on preparation the rep rarely has time for. Thirty accounts at three minutes of research each is an hour and a half before the first dial, so most reps research the first five, wing the rest, and the quality of the conversations falls through the block. The information is available; the time to assemble it is what is missing.
Call notes are a specific format: short, scannable, ordered by the sequence of calls, and built around one question that opens the conversation. They differ from an account plan in length and from an email in purpose. The Personalization Agent writes them from the data on the list and the company's live signals, anticipates the objection each account is likely to raise, and puts everything in one Google Doc in the order the rep will dial, so the block can run without switching tabs.
How the mission runs
- Read the calling sheet in order. The Personalization Agent loads calling sheet <name> with its 30 accounts and the order they will be dialed, along with the contact, number and any fit score, and keeps that order for the Doc.
- Gather the facts per account. For each company it collects what the company does in one sentence, headcount and location, the detected stack in the categories that matter to your product, and the latest signal - a posting, a round, a technology change - with the date, from firmographics, technographics and funding data.
- Anticipate the objection. From the stack and the company's situation, the agent writes the objection this account is most likely to raise - an incumbent tool, a recent purchase, timing after a round - and a one-line response, so the rep is not hearing it for the first time on the call.
- Write the opening question. Each account gets one question to open with, built from its latest signal, that invites the contact to talk about their situation rather than to evaluate a pitch, written in the voice you describe.
- Assemble the Google Doc. A Google Doc is written with one section per account in call order - contact, number, the facts, the signal, the objection and response, the opening question - with a table of contents at the top and space for outcome notes under each account.
The prompt
This is the exact objective the agent receives. Swap the obvious placeholders for your own domain, segment or channel and run it as-is from the console, Slack, or the API.
What comes back
A Google Doc of call notes for the 30 accounts on calling sheet <name>, in dial order, each with the contact and number, a one-sentence description of the company, size and location, the relevant stack, the latest signal with its date, the likely objection with a response, an opening question and a space for notes. The notes are also saved on the list so a second block on the same accounts starts from them.
Make it yours
- Ask for 60 or 100 accounts and get the Doc split into morning and afternoon blocks.
- Add the company's named customers or partners as a talking point where the site lists them.
- Deliver the notes into HubSpot or Pipedrive as a note on each contact instead of a Doc.
- Refresh the signals section each morning for a standing calling list.
Frequently asked questions
How long is each account's section?
About a third of a page - enough to scan in the seconds before the call connects. Ask for a longer format if reps prefer to read before the block rather than during it.
Where does the likely objection come from?
From the account's own situation: an incumbent tool detected in the stack, a recent round that suggests a busy quarter, a posting that suggests they plan to hire rather than buy. The reasoning is stated so the rep can judge it.
Can the notes include the last CRM activity?
Yes. Connect the CRM and each section shows the last touch, the owner and any open deal, so the opening question reflects the history.