Use these prompts to turn the account record into a call plan you can use while speaking. They are for discovery calls with a new prospect or an existing customer considering a wider use case.
Start with the account record, not a company website or a generic research summary. The useful call sheet connects the stated opportunity stage, prior conversations and the people in the meeting. It should tell you what to learn next, not pretend you already know the answer.
Key point
Build around evidence
A good call sheet separates confirmed facts from assumptions, then turns the gaps into questions.
Choose the right prompt
Use the prompt that matches the state of the opportunity.
| If you have | Use | What you get |
|---|---|---|
| A populated CRM record and recent emails | Build the complete call sheet | A full briefing with questions, risks and a next step |
| Only a few CRM fields or an inbound request | Prepare from a thin account record | A fact list and questions that qualify the opportunity without guessing |
| A current customer and a possible new use case | Focus an expansion discovery call | A plan that tests whether existing success applies to the expansion |
| A rough sheet that feels generic | Test questions against likely objections | A tighter question set and unsupported claims to remove |
| A late email or changed opportunity field | Refresh prep after new correspondence | A change-only update, so you see what matters before the call |
For a normal discovery meeting, start with the complete call sheet. Paste the account record, the opportunity fields and the actual correspondence. Include fields such as account owner, segment, opportunity amount if your team records it, close period, stated use case, stage, named contacts and last activity. If a field is blank in the CRM, leave it blank in the prompt. Do not replace it with your own estimate.
For an expansion, include material about the existing relationship. This may include adoption notes, renewal discussion, support themes and success measures already agreed with the customer. The expansion prompt deliberately asks where the evidence stops. A satisfied existing team does not prove that another team has the same workflow, sponsor or budget.
Watch out
Do not paste a generic account summary alone
The meeting objective and objections will be weak if you omit the opportunity stage and the customer's actual words from prior correspondence.
Prepare the source material
Before pasting anything, make a short collection in this order:
- Copy the current opportunity stage and the fields that explain it. Include the next activity and any stated reason for the opportunity.
- Copy the last relevant emails, messages and meeting notes. Keep dates and speaker names where possible.
- Add the planned attendees, including internal colleagues. Mark a name as unknown rather than guessing their role.
- Remove material that is unrelated to this opportunity. A long thread about a closed support issue can distract from a current discovery call.
- Use the prompt's placeholders exactly once for each source. If you have no correspondence, write
Nonerather than leaving the section unclear.
The model you are using can handle inputs differently depending on the version and service configuration. Check the current guidance in the xAI documentation overview if you need to work with a large record or adjust how you provide source material.
Read the sheet in call order
Do not treat the returned sheet as a script. Read the meeting objective first. It should describe what evidence you need by the end of this particular call. For an early-stage opportunity, that may be confirming the business trigger, problem owner and agreed follow-up. It is not usually a commitment to send a proposal.
Then scan the questions. Keep five to seven on your notes. Put them in an order that sounds natural: context, current process, impact, stakeholders, decision process, then a next step. If one question has no link to the account record, remove it or make it a conditional question.
Use likely objections as preparation, not as a list to introduce. The strongest output will identify a concern tied to a previous email, an unresolved account issue or a missing stakeholder. If it says there is no evidence for an objection, accept that result. Do not ask the model to manufacture resistance so you can rehearse it.
Check
Check the objective before the call
You should be able to say what you need to learn, who can answer it and what next step follows if you learn it.
Check the output for errors
Check every factual statement against the pasted material. This is especially important for role, authority, timeline and business problem. A polished sentence can still turn an inference into a fact.
Use this quick review:
- Check that every named person appears in the account record or correspondence. If not, change them to a role suggestion or remove them.
- Check the stated opportunity stage against your CRM. The questions should fit that stage.
- Check that the meeting objective is achievable in one conversation. Split it if it requires validation from several teams.
- Check that each proposed next step has an owner and a condition.
Send proposal next weekis vague.If the operations lead confirms the workflow and approval path, send a scoped outline, owned by the account executive, by Fridayis usable. - Check objections for evidence. A concern based only on a common sales pattern belongs in your private preparation, not in the account sheet.
Stop
Do not present inferred details as customer statements
Label uncertain points as unknown and ask the question on the call. A false assumption damages trust faster than an incomplete sheet.
When the result does not work
If the output is generic, add the missing source material first. Usually this means the latest customer email, the exact opportunity stage or the names and roles of meeting attendees. Then run the complete call sheet prompt again.
If the output conflicts with the CRM, treat the CRM field and dated customer correspondence as the source to verify. Use the refresh prompt to show the changes rather than editing a long sheet by hand. If key details remain unclear, take the Open ambiguities questions into the call. Your aim is a better conversation, not a complete story before the customer has told it.