LearnGrok
Prompts
PromptBeginnerGrok Bot basics

Call prep sheet for discovery meetings

Build a focused discovery call sheet from CRM notes and emails, for salespeople working new or expanding accounts.

5 min read

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:

  1. Copy the current opportunity stage and the fields that explain it. Include the next activity and any stated reason for the opportunity.
  2. Copy the last relevant emails, messages and meeting notes. Keep dates and speaker names where possible.
  3. Add the planned attendees, including internal colleagues. Mark a name as unknown rather than guessing their role.
  4. Remove material that is unrelated to this opportunity. A long thread about a closed support issue can distract from a current discovery call.
  5. Use the prompt's placeholders exactly once for each source. If you have no correspondence, write None rather 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 week is vague. If the operations lead confirms the workflow and approval path, send a scoped outline, owned by the account executive, by Friday is 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.

Copy-ready prompts

5 prompts. Open one to read it, or take the whole pack.

1Build the complete call sheetUse this when you have the account record, recent correspondence and a defined opportunity stage.
Create a discovery meeting call sheet for the account below. Use only the supplied material. Do not assume facts that are not stated.

Account record:
[paste account record or CRM fields]

Prior correspondence:
[paste emails, meeting notes and messages]

Opportunity stage: [paste current stage]

Meeting details:
- Date and time: [paste]
- Planned attendees: [paste names and roles, if known]
- Meeting type: [discovery / expansion discovery]

Return the call sheet in this exact Markdown format:

## Account snapshot
- Company and segment:
- Known business context:
- Current products, relationship or activity:
- Opportunity stage and evidence for that stage:
- Information that is missing:

## Meeting objective
Write one measurable objective for this meeting. It must be achievable in one call and based on the opportunity stage.

## What we need to learn
List 5 to 7 tailored discovery questions. For each question, include:
- Question
- Why it matters
- What answer would indicate a strong fit

## Likely objections or risks
List up to 5 likely objections, concerns or deal risks. For each, include the evidence from the supplied material and one neutral follow-up question. Do not invent objections.

## Attendees to involve
List relevant customer and internal roles. For each, state why they matter. Mark each as Confirmed, Suggested or Unknown.

## Proposed next step
State one proposed next step, the owner, the target timing and the condition that must be met before it happens.

## Rep briefing
Give three concise points to remember during the call.

Where the material is ambiguous, write `Unknown` and add the exact question to ask. Separate facts from inferences clearly.
2Prepare from a thin account recordUse this when the CRM record is incomplete or the opportunity has only just been created.
Prepare a discovery call sheet from the limited account information below. Treat every missing detail as unknown. Do not fill gaps with generic company claims, assumed pain points or guessed stakeholder names.

Account record:
[paste available CRM fields]

Prior correspondence:
[paste any emails, forms, notes or write "None"]

Opportunity stage: [paste current stage]

Known meeting attendees: [paste names and roles, or write "Unknown"]

Return a Markdown call sheet with these sections:

## Confirmed facts
List only facts directly supported by the supplied material.

## Unknowns to resolve first
List the 5 most important unknowns for this opportunity stage. For each, provide one precise question to ask.

## Meeting objective
Write one objective that is realistic given the thin record. Do not make the objective a product demonstration or proposal commitment unless the supplied stage supports it.

## Discovery questions
Provide 6 questions in this order: business trigger, current process, problem impact, stakeholders, decision process, next step. Tailor wording to the known facts. If no tailoring is possible, say so in a note before the list.

## Stakeholders to identify
Provide a table with columns: Role to identify, Why this role matters, Question to find them.

## Risks
List up to 3 risks created by missing information, with a question that reduces each risk.

## Proposed next step
Give one conditional next step using this format: `If [evidence gained], then [action], owned by [person], by [timing].`

End with `Do not assume:` followed by every important fact that cannot yet be supported.
3Focus an expansion discovery callUse this for an existing customer where the discussion concerns a new team, use case or wider deployment.
Create a call sheet for an expansion discovery meeting. Distinguish clearly between what is known about the existing customer relationship and what still needs to be validated for the expansion opportunity.

Customer account record:
[paste CRM account fields]

Existing relationship and product usage:
[paste renewal notes, usage summaries, support themes or account notes]

Expansion opportunity:
[paste opportunity fields, requested use case and stage]

Prior correspondence about the expansion:
[paste emails and meeting notes]

Meeting attendees:
[paste names, roles and teams, if known]

Return the answer in Markdown using this exact structure:

## Existing relationship
- Confirmed outcomes or value already seen:
- Current limitations, risks or unresolved issues:
- Evidence source for each point:

## Expansion hypothesis
State the proposed new use case in one sentence. Label it `Confirmed`, `Partly supported` or `Unconfirmed`, and explain why.

## Meeting objective
Write one objective that validates the expansion case without assuming that existing success transfers to the new team or use case.

## Tailored questions
Provide 7 questions. Group them under: New team's workflow, problem and impact, adoption and ownership, commercial or approval process. For each, state what the answer will help decide.

## Likely objections
List only objections supported by account history, correspondence or a stated gap. Include a follow-up question for each. If none are supported, write `No evidence-based objections identified`.

## People to involve
Create a table with columns: Person or role, Relationship to current account, Role in expansion, Status, Reason to involve.

## Proposed next step
Give one next step with owner, required input and timing.

## Boundaries
List any claims about outcomes, adoption or stakeholder support that must not be made on the call because the supplied material does not support them.
4Test questions against likely objectionsUse this after you have a draft call sheet and want to remove weak questions before the meeting.
Review the draft discovery call sheet below against the account material. Improve it for a sales discovery meeting, but do not add unsupported account facts.

Account record and opportunity stage:
[paste account and opportunity fields]

Prior correspondence:
[paste emails and notes]

Draft call sheet:
[paste draft]

Return four sections in Markdown:

## Questions to keep
List questions that are specific, open enough to produce useful evidence and appropriate for the stated opportunity stage. Give one sentence explaining why each should remain.

## Questions to replace
For each weak, leading, generic or repetitive question, provide:
- Original question
- Problem
- Replacement question
- Decision the answer will inform

## Objection coverage
Create a table with columns: Evidence-based concern, Where it appears in the source material, Question that surfaces it, What not to assume. Do not create a concern if the source material provides no evidence.

## Revised call plan
Provide:
- One meeting objective
- The best 5 to 7 questions in call order
- Attendees or roles to involve, labelled Confirmed, Suggested or Unknown
- One conditional next step

If the draft contains unsupported claims, quote them under `Remove or verify` and state what evidence would be needed. If information is ambiguous, retain the ambiguity rather than resolving it.
5Refresh prep after new correspondenceUse this when an email, message or updated CRM field arrives shortly before the call.
Update a discovery meeting call sheet using the new information below. Preserve useful parts of the previous sheet, but change anything contradicted by the update. Do not silently treat a prospect's opinion, intention or estimate as a confirmed fact.

Previous call sheet:
[paste previous sheet]

New correspondence or CRM update:
[paste new email, message, note or field change]

Opportunity stage:
[paste current stage]

Return a Markdown update in this exact format:

## What changed
Create a table with columns: New information, Impact on call preparation, Confidence. Use `Confirmed`, `Reported` or `Unclear` for confidence.

## Revised meeting objective
Write one objective. State `Unchanged` if the update does not materially affect it.

## Revised questions
List only questions that should be added, removed or rewritten. For each, explain the reason in one short sentence.

## Revised objections or risks
List changed, new or removed risks. Cite the relevant supplied wording or field value for each.

## Attendee changes
State who should now attend or be identified, and why. Label each item Confirmed, Suggested or Unknown.

## Proposed next step
Provide the revised next step with owner, timing and condition.

## Open ambiguities
List every ambiguity introduced by the new information and the question to resolve it.

Do not repeat unchanged sections from the old call sheet unless they are needed to explain a change.

Last checked against xAI’s own pages on 2026-08-21. Grok changes quickly; anything version-specific should be confirmed upstream before you rely on it.

More in Grok Bot basics

Found something out of date?

Grok changes quickly and this page is a snapshot. If something here is wrong, or you know a better resource, send it over.

Suggest a link →

Advertise on LearnGrok

$420.69one-time, for a 30-day run

Square works best. PNG, JPEG or WebP, up to 2 MB.

Stripe on the next step. Live once approved.