Call plan from account signals

Use this workflow before a discovery or deal-progression call where the account history is scattered across CRM records, notes and recent news. You will leave with a one-page call plan: a focused agenda, useful questions, risks to test and one proposed next-step decision.

This is for account executives. It does not replace account judgement. Treat the CRM record and your direct conversation as the source of truth.

1. Set the call outcome before reading the account

Open a working note and fill in these fields first:

• Account: company name and business unit in scope.
• Call type: discovery, qualification, stakeholder alignment, technical validation, commercial progression or recovery.
• Attendees: customer names, roles and known influence.
• Deal stage: use the stage recorded in the CRM.
• Call outcome: one observable result you want by the end of the call.
• Proposed next step: the meeting, introduction, document review or decision you expect to request.

Write the outcome as a testable statement. For example: Confirm whether the operations lead will sponsor a scoped workflow review with IT and finance. Avoid outcomes such as build rapport or learn more. They may happen, but they do not tell you what to ask.

If the next step needs several people, state who must agree. A call with one participant rarely settles a decision owned by a wider buying group.

2. Assemble a bounded account pack

Collect only material that could change the call. Use records from the current opportunity, not the whole account archive.

1. Copy the CRM opportunity fields: stage, amount if recorded, close timing, stated problem, use case, competitors, next step and loss risk.
2. Copy the last two or three relevant activity records. Include call notes, emails and meeting outcomes.
3. Add stakeholder notes. For each person, include role, priorities, objections, influence, relationship strength and last interaction.
4. Add two or three recent account signals, such as a company announcement, leadership change, hiring pattern, product launch or stated strategic priority. Record the source date beside each signal.
5. Remove duplicate notes and label unverified claims as unconfirmed.

Do not paste a long CRM export without headings. A dated, labelled pack makes it possible to trace each recommendation back to evidence.

3. Ask for an evidence-led call plan

Give the model the account pack and a clear instruction. Keep the output short enough to use while you are on the call. If you use product features to attach or process material, check the current handling and feature details in the xAI documentation overview, as availability is version-dependent.

Use this prompt structure:

Create a call plan for a [call type] with [account] on [date].

Call outcome: [outcome]
Proposed next step: [next step]

Use only the evidence in the account pack. Mark anything unsupported as a question or assumption. Do not invent customer facts.

Return:
1. A three-item agenda, with minutes for each item.
2. A brief account position: confirmed facts, open questions and risks.
3. Six to eight questions, ordered from context to impact, process and commitment.
4. One tailored hypothesis, clearly labelled as a hypothesis.
5. A closing script that asks for the proposed next step.
6. A CRM update checklist for after the call.

Account pack:
[paste the labelled material]

Ask for questions that earn the next stage. For a discovery call, test problem, impact, ownership, urgency and process. For a progression call, test what has changed since the last conversation, which requirement remains unresolved, who else must participate and what decision date is credible.

4. Shape the agenda and questions

Read the draft as an account executive, not as an editor. Cut questions that merely repeat facts already confirmed in the CRM.

A useful agenda usually has three parts:

1. Confirm what has changed since the last interaction and what the customer wants from this call.
2. Test the problem, impact, stakeholders and constraints behind the current opportunity.
3. Agree the next action, owner and date.

Place your strongest evidence-based question early. If a stakeholder said the main issue is manual reporting, do not ask whether reporting is difficult. Ask what the manual work delays, who feels the impact and what changes if it continues for another quarter.

Keep a separate list of questions for each attendee. A senior sponsor can clarify priority and decision criteria. A practitioner can explain the current process. A technical contact can identify integration or security review needs. Do not ask one person to answer for the entire organisation.

5. Check the plan against the record

Before the call, compare every statement in the plan with the account pack. This is where call preparation often fails: polished wording can hide unsupported assumptions.

If you see this in the draft	Check it against	What to do
A claimed priority or initiative	Dated stakeholder note or account signal	Change it to a question if no source supports it
A named decision-maker	Stakeholder notes and opportunity history	Mark influence as unknown unless it is recorded
A promised timing or deadline	CRM close timing and last customer statement	Ask whether the date still holds
A suggested next step	Current stage and known buying process	Make the request smaller if required people are absent

The output is wrong when it sounds specific but cannot point to a dated note, CRM field or stated assumption. It is also wrong when the agenda does not leave time to agree the next step, or when the questions diagnose a problem but never test ownership and commitment.

Check for contradictions. A CRM field may say the deal is late stage while the latest note shows the problem is still unconfirmed. Follow the latest customer evidence, flag the mismatch and use the call to resolve it. Do not silently force the evidence into the preferred stage.

6. Run the call and hand over the record

Put the agenda, questions and closing request in the order you will use them. Keep the account position and risks below them as reference, rather than reading them aloud.

At the end of the call, summarise four items aloud:

• the problem or goal the customer confirmed;
• the unresolved issue;
• the next action;
• the owner and date for that action.

Then update the CRM on the same working day. Record the customer’s words separately from your interpretation. Update the next-step field, stakeholder roles, risks, timing, decision process and the reason for any stage change. Send the agreed follow-up only after those fields match what was said on the call.

When the plan does not work

If the output is generic, narrow the input. Add the last customer statement, the current opportunity stage and the specific decision you need next. If it invents facts, require a source label after each account claim and remove unsupported claims yourself. If the call produces no next step, lower the ask: request the missing stakeholder, a short validation session or confirmation of the decision process. Then record why the larger decision could not be made and rebuild the next call plan from that evidence.