LearnGrokUse these prompts after a customer call, while the transcript or notes are still the source of record. They give you two outputs: an email the customer can correct, and a CRM entry your manager can inspect. They are for sales representatives who need a clean follow-up without turning assumptions into commitments.
Choose the source that matches the call
Pick the prompt based on the material in front of you, not the type of account.
| If you have | Use this prompt | What it protects against |
|---|---|---|
| A complete call transcript | Transcript to email and CRM update | Missing a stated qualification detail |
| Short or messy notes | Rough notes to safe follow-up | Presenting shorthand as fact |
| A task-heavy call | Action and owner confirmation email | Assigning an owner or date without agreement |
| A stage, timing or stakeholder change | Deal movement CRM note | Moving the deal based on weak signals |
| A request for commercial material | Proposal follow-up and CRM record | Promising scope, pricing or documents not agreed |
Key point
Keep the source visible
The email and CRM record should be traceable to the call notes. If a point cannot be traced, mark it as unconfirmed or leave it out.
Prepare the source before pasting it
- Paste the whole transcript where possible. Do not paste only the final five minutes if the buying process or timing was discussed earlier.
- Fill in the account name, opportunity name and call date. These fields stop the output becoming a generic note that you cannot find later.
- Add your current CRM stage and stage definitions when you need a stage recommendation. Without the definitions, the output can assess evidence but should not choose a stage.
- Remove material unrelated to the opportunity, such as another customer's details or a private internal discussion accidentally included in the record.
- Keep the customer's actual wording where it matters. This is especially useful for timing, budget, approval, security review and a request for a proposal.
Watch out
Notes are not a meeting record
Phrases such as "likely next month" or "send pricing" may be your shorthand. Treat them as unclear unless the source names who said it, what they agreed and when.
Send the email only after comparing actions
Read the action table before you send anything. Check each row against the source text, then make three decisions:
- Is the action explicit, rather than merely suggested?
- Is the owner named, rather than assumed from job title or past practice?
- Is the date a stated calendar date, rather than your interpretation of a relative phrase?
A follow-up email can safely ask the customer to confirm an incomplete item. It should not quietly fill in the gap. For example, use Please confirm the owner and target date for the security questionnaire instead of saying that a named person will complete it on Friday.
Keep internal pipeline judgement out of the email. A customer should see the agreed discussion, actions and open questions. They should not see your forecast confidence, concerns about executive support or a missing budget field.
Check
The email is ready when
Every factual sentence is supported by the call source, and every action has either a confirmed owner and date or an explicit request to confirm them.
Put the right detail in the CRM update
The CRM record has a different job. It should make the next person in the account able to answer four questions quickly:
- What changed on this call?
- Who matters to the decision, and what is their position?
- What could stop or delay the deal?
- What will the sales team do next?
Use evidence beside important conclusions. Customer said procurement review starts after technical validation is useful. Procurement is a blocker is less useful unless the notes support it. If the customer did not discuss budget, do not write No budget. Write Budget not discussed or Budget unconfirmed.
For a stage change, look for evidence such as a confirmed evaluation step, an identified decision process, a scheduled decision meeting or a stated commercial review. Interest in a demo, a request for slides or a polite response does not by itself show progress.
If your CRM fields or workflow differ from the labels in these prompts, map the output into your local fields. Product behaviour and available features can vary, so check the current guidance in the xAI documentation overview.
Stop
Do not copy internal judgement into the customer email
Risks, forecast calls and stakeholder assessments belong in the CRM update. Sending them externally can damage trust and create confusion.
Check for wrong output
The most common error is false certainty. Search the output for words such as agreed, will, confirmed, approved, by, and next. For each one, find the supporting line in the notes or transcript. Remove it or change it to a confirmation question if you cannot find support.
Also check names. A contact may attend a call without owning an action or influencing a decision. Check that the output has not converted attendance into responsibility. Finally, compare the email action table with the CRM action list. The confirmed external actions should match. The CRM may contain extra internal follow-up, but it must not contradict the email.
When the result does not work
If the email is too vague, add the missing call date, attendee names and the exact notes on actions. If it invents detail, use the rough-notes prompt and keep ambiguous wording in the source rather than rewriting it first. If the CRM stage recommendation is unreliable, paste your team's stage definitions or record No stage change recommended until you have evidence. If a commitment matters, return to the call recording or ask the customer to confirm it in writing.
