Use this workflow to turn scattered account records into a one-page brief before a customer or prospect call. It is for account executives preparing the conversation and sales managers checking that the account plan is grounded in evidence.
The finished brief gives you likely priorities, questions worth asking, risks to manage and one proposed next step. It does not replace account knowledge. It makes the evidence, gaps and assumptions visible before the call.
Key point
Build from evidence, not guesses
Separate what the account record says from what you infer. A useful call brief shows both.
1. Gather the account record
Collect the material before asking the model to draft anything. Use records that relate to the current opportunity, not every historical interaction.
Create a working document with these sections:
- Account: company name, sector, territory, current stage and opportunity name.
- Call: date, purpose, meeting type and attendees.
- CRM notes: the latest notes, open tasks, stated needs, objections, timeline and decision process.
- Contacts: each person's role, level of influence, stated priorities and relationship status.
- Prior emails: the most recent thread, promised actions, unanswered questions and language the customer used.
- Company news: dated items from the company or reliable account research, with the source and date recorded.
- Commercial context: current proposal status, agreed scope, dependencies and the next dated event.
Remove duplicates and mark the date on each item. If two CRM notes disagree, retain both rather than choosing one silently.
Do not include data you are not permitted to use in your approved AI workspace. Keep personal contact details, internal pricing discussions and confidential attachments out unless your organisation has approved that use.
Watch out
Do not treat old notes as current intent
A contact's priority from a previous quarter is a lead to test, not a fact for the next call.
2. Define the outcome for this call
Write one sentence before you create the brief. It should name the decision or information you need by the end of the conversation.
Examples:
- Confirm whether the operations lead is sponsoring the project and agree the evaluation steps.
- Test whether the stated implementation date still holds after the company's recent change.
- Agree who must review the proposal and book the review meeting.
Then list the result you want and the minimum result you will accept. This stops the brief becoming a generic account summary.
| Call type | Main outcome | Evidence to bring |
|---|---|---|
| Discovery | Confirm problem, impact and owner | Current notes, contact roles, relevant company change |
| Proposal review | Confirm scope, concerns and approval path | Proposal version, email feedback, open assumptions |
| Follow-up | Secure a dated action | Last commitment, unanswered question, next internal milestone |
3. Ask for a structured draft
Paste the collected material and the call outcome into your approved workspace. Ask for a brief in a fixed format, so you can inspect each part quickly.
Use this prompt:
Create a sales call brief using only the material below.
Call outcome required: [write one sentence]
Account material:
[paste your dated CRM notes, contact details, emails and news]
Return these sections:
1. Call objective, in one sentence.
2. Known facts, with the source and date for each fact.
3. Likely priorities, labelled as inferences and tied to supporting evidence.
4. Contacts and roles, including missing stakeholders or unclear influence.
5. Five tailored questions, ordered from confirmation to decision process.
6. Risks, contradictions and information gaps.
7. Recommended next step, with owner, action and target date if supported by the material.
8. A 60-second opening summary for the call.
Do not invent customer facts, dates, stakeholders, budget, approval steps or commitments. State "not evidenced" where the material does not support a conclusion.
Keep source labels in the input, such as CRM note, 14 May or Email from procurement, 3 June. The model can then connect a claim to a record instead of presenting a plausible but untraceable summary.
Input handling and available features can vary by version and workspace. Check the xAI documentation before using account material in a new process.
4. Check the brief against the source material
Read the draft with the CRM record and email thread open. Do this before sharing it with your manager or using it on the call.
Check each section in this order:
- Facts: verify names, roles, dates, opportunity stage and commitments word for word where they matter.
- Inferences: check that each likely priority has evidence. Change unsupported claims to questions.
- Questions: remove questions already answered in the email thread. Add a question for every material uncertainty.
- Risks: look for silence around stalled actions, missing stakeholders, unclear timing and conflicting notes.
- Next step: make sure it is realistic for this meeting. It should name an owner and a specific action, not
follow up.
Check
The brief is ready when you can trace it
You should be able to point to a dated CRM note, email or research item for every claimed fact. Everything else must be labelled as an inference, question or gap.
A common error is a smooth narrative that combines separate clues into a false certainty. For example, an email asking about implementation and a news item about expansion may suggest urgency. They do not prove an approved project or a fixed deadline. Ask: “Has the expansion changed the timing or scope of this work?”
5. Put the brief into call order
Reduce the checked draft to the notes you can use live. Aim for one page or a clearly scannable screen.
Use this order:
- Opening: your purpose for the meeting and the agreed context.
- What changed: one or two recent facts that justify the conversation.
- Questions: ask the highest-value confirmation question first, then move to impact, stakeholders and process.
- Risks to test: keep these as prompts, not statements.
- Close: propose the next action, owner and date.
Send the brief to your sales manager only after you have checked it. If they review it, ask them to challenge one point: the missing person, assumption or commitment most likely to block progress.
Note
Keep the next step conditional when needed
If a decision depends on information you do not yet have, write the condition. For example: If the technical lead confirms scope, book a proposal review with procurement.
6. Update the CRM after the call
Within your normal sales process, record what changed. Add the customer's exact wording for priorities or objections where useful. Update contact roles, timeline, decision process, risks and the agreed next action.
Keep the previous brief with the call record if your team uses account files. It gives the next account owner a clear distinction between what was expected and what the customer actually said.
When the draft does not work
If the brief is vague, do not ask for a more persuasive version. Add the missing material: the latest email, a dated CRM note, the actual proposal status or the call outcome you need.
If it invents details, shorten the input to relevant records and repeat the instruction to label unsupported points as not evidenced. If the records conflict, keep the conflict in the brief and make resolving it a call question. If there is too little evidence to prepare a useful brief, use the call to qualify the account rather than pretending you have an account plan.