Build today's call list
Ranks today's calls from the CRM by promises, fresh signals, stage and last touch, each with a dated reason and an opening line.
daily-call-list/SKILL.mdDownload- name
daily-call-list- description
- Use this skill when a seller asks who to call today. It reads the CRM and returns a ranked list of calls, each with a dated reason, the first line to say and the deal behind it. Ranking uses promised follow-ups, signal freshness, deal stage and days since the last touch, with weights you can change.
- license
- CC-BY-4.0
Build today's call list
This skill turns the CRM into today's calls, in order, each with its reason and the date behind it. Use it before the first call block. It changes nothing in the CRM unless you approve the tasks it proposes.
Inputs
Ask for what is missing, in one message:
- CRM access (read) to open deals, contacts, activities and notes. Without it, ask for a CSV export or a paste of open deals (company, contact, phone, stage, amount, close date, last and next activity dates) and the last 30 days of activities.
- Whose list: the person asking, unless they name another owner.
- Capacity: how many calls fit today. Default 10.
- Today's date and time zone, and the seller's calling hours. Default 9:00 to 17:00 local.
- New signals (optional): job posts, funding rounds, new leaders, contract awards or events at their accounts, each with a date. If the agent has web access, it can check the top 20 accounts for news from the last 30 days.
- Weights (optional): the defaults are in step 4.
Steps
State the date and time zone at the top of the answer, so "overdue" and "today" mean the same thing to both of you.
Build the candidate set. Open deals owned by the user, contacts with a task due today or overdue, and accounts with a dated signal in the last 30 days. Drop anyone flagged do not call, unsubscribed or opted out, and deals where the next step belongs to the buyer and is dated in the future.
Find promises and open replies. Search notes, tasks and (if connected) sent email from the last 30 days for commitments such as "I'll call you Tuesday" or "let's talk next week", and for buyer messages nobody answered. Resolve relative dates against the date the message was written. Without email access, ask: "Did you promise anyone a call this week, or is anyone waiting on you?"
Score the rest. Pin promises due today or overdue and open replies to the top, in that order. Score everyone else:
Factor Points Signal freshness 3 if dated in the last 7 days, 2 if 8 to 30 days, 0 if older or none Stage 3 for late stages (proposal, negotiation), 2 for middle (qualified, demo held), 1 for early Days since the last two-way touch 2 if 15 or more, 1 if 4 to 14, 0 if 0 to 3 Map the CRM's own stage names to early, middle and late once, and ask the user if a stage is unclear. Break ties by the nearest close date, then by amount. The user can change any weight; restate the weights in the output when they do.
Write the reason and the opener. The reason cites one dated fact: the signal and its date, the promise and the day it was made, or the last touch. The opener is one sentence that refers to that fact. "Just checking in" is never an opener.
Check that the call can happen. A phone number on file, and the contact's local time inside business hours if their time zone is known. No phone: suggest email or LinkedIn instead and move the contact to "Other channel".
Cut to capacity. Everything past the limit goes under "If you have time", in rank order.
Offer, then stop. Offer to create call tasks for today's list in the CRM. Create them only after a yes.
Output
Calls for Tuesday 2026-11-24 (America/Chicago) · 10 calls · weights: default
Pinned
1. Dana Ruiz, VP Operations, Pinecrest Engineering · +1 512 555 0142 · 9:30 her time
Why: you promised a call "early next week" in your email of 2026-11-19.
Open with: "I said I'd call this week about the pilot dates. Is now still a good time?"
Deal: Field pilot · Proposal · $18,000 · close 2026-12-15
Ranked
2. Luis Prado, Director of Logistics, Summit Ag Supply · +1 559 555 0187 · score 7
Why: announced a second distribution center on 2026-11-18 (signal 6 days old);
last two-way touch 2026-10-30.
Open with: "I saw the new Fresno site went public last week. Who is setting up
receiving there?"
Deal: Warehouse rollout · Qualified · $40,000 · close 2027-01-31
3. ...
If you have time: 11. ... 12. ...
Other channel (no phone on file): Vale Alto Construction, Ana Costa: email instead.
Left out: 1 contact flagged do not call.Guardrails
- Reads: open deals, contacts, activities and notes in the CRM; sent email from the last 30 days when connected; public news for the top accounts when web access is on.
- Writes: nothing by default. With approval, call tasks dated today.
- Asks before: creating or moving tasks, logging a call, changing any field.
- MUST give every call a reason with a date, or write "no date found".
- MUST put open replies and promised follow-ups above any score.
- MUST respect do not call, unsubscribe and opt-out flags on every list, including "If you have time".
- NEVER invent a signal, a promise, a phone number or a time zone. A missing field is shown as missing.
- NEVER mark a call as done or change a deal stage from this skill.
Sources
- Hiring signals, ALTARA Insights: which job posts count as a buying signal.
- Funding and leadership changes, ALTARA Insights: why a new round or a new leader opens a conversation.
Made by ALTARA, the AI sales agent your team texts. More skills: https://www.altaratech.com/store
Use it with
-
Runs in ALTARAPlaybook Plan the dayRun the Monday pipeline review in ALTARAText ALTARA for the week's plan, count the activities, find deals with no next step and fix them by chat. The review uses no credits. 20 minutes every MondayRun it →
-
Runs in ALTARAPlaybook Run the cadenceFounder-led outbound in 30 minutes a day, with ALTARAThirty minutes a day with ALTARA: a weekly list with dated reasons, contacts and sequences you approve, replies logged in the CRM. 30 minutes a dayRun it →
-
Connection Keep the CRM currentHubSpotALTARA reads one HubSpot pipeline, read-only, and sends each change with a link to the deal. Your own AI reads the same records through HubSpot's MCP. Reads (rolling out)See how →
-
Connection Keep the CRM currentSalesforceThe ALTARA team connects Salesforce on request, read access first. Your own AI reads the same records through Salesforce's hosted MCP servers. Connected on requestSee how →
-
Connection Keep the CRM currentPipedriveALTARA keeps your Pipedrive pipeline current from the chat, after your yes. Your own AI reads the same deals through Pipedrive's MCP server. Reads and writesSee how →
-
Connection Keep the CRM currentZoho CRMThe ALTARA team connects Zoho CRM on request, read access first. Your own AI reads the same records through Zoho's pre-built MCP servers. Connected on requestSee how →
-
Connection Run the cadenceGmail, Google Calendar and DriveALTARA sends the sequences your team approved from a separate, warmed inbox. Your own AI reads your Gmail, Calendar and Drive to prepare the calls. Sending inbox for sequencesSee how →
-
Connection Run the cadenceOutlook, Teams and SharePointYour team texts ALTARA in Microsoft Teams, and it sends approved sequences from a warmed inbox. Your own AI reads your Outlook, Teams and files. Sending inbox for sequencesSee how →