LearnGrokUse these prompts to turn a contact list into a buying-group view of one complex opportunity. They suit account executives building deal coverage and sales managers testing whether a forecast rests on real customer access.
A contact map is only useful when it distinguishes what you know from what you assume. Run the prompts in order for a new opportunity. For an established deal, start with the prompt that matches the weak point, such as duplicate CRM records or an unfilled economic-buyer role.
Key point
Keep evidence visible
A named stakeholder without a source, date or documented interaction is a lead to validate, not confirmed deal coverage.
1. Gather the account material first
Create one working folder or document for the opportunity. Copy the source material into the placeholders without changing the prompt instructions. Include the information that can show both contact identity and deal relevance:
- CRM contact records, including record IDs, title, employer, owner and recent activity.
- Opportunity fields, particularly the stated customer problem, current status, next step and expected decision process.
- Meeting notes with dates and attendees.
- Email summaries or call notes that record a stakeholder's position, concern or commitment.
- Public account information that your organisation has approved for this work.
Do not paste a general account summary and expect a reliable stakeholder map. The model needs the names, the evidence and the date of each interaction. If your CRM shows only activity counts, add the relevant notes. An activity count cannot show whether the contact challenged the proposal, introduced a colleague or merely accepted a calendar invitation.
Watch out
Do not fill gaps with job titles
A senior title may suggest where to investigate. It does not prove decision authority, support or internal influence.
2. Extract before you interpret
Run Extract contacts and evidence first. Its job is not to decide who matters. It creates an auditable register of every person found in the material and flags records that may refer to the same person.
This matters when a CRM contains an old title, while a meeting note uses a newer one. It also matters when two people share a surname or when an external contact moved between business units. Keep former employees in the evidence register. Their history may explain why a route has gone quiet, but they are not current buying-group coverage.
Then use Resolve duplicate contact records. Review its Do not merge section before changing CRM data. A mistaken merge can remove a valid stakeholder, assign activity to the wrong person and give your manager a false picture of account access.
Check
Check the working contact list
Every current contact should have one canonical row, a source, and a confidence level. Uncertain matches should remain separate.
3. Map roles from deal evidence
Run Assign buying roles once the contact list is stable enough to use. Give it the customer problem and proposed scope, not only names and titles. A person can be influential in one initiative and irrelevant to another.
Read the Role status column closely:
| If the role is | Treat it as | What to do next |
|---|---|---|
| Confirmed | Supported by explicit notes or customer statements | Maintain access and test whether the role remains current |
| Probable | A reasonable reading of incomplete evidence | Ask a targeted question to confirm it |
| Unfilled | No named person is supported by evidence | Find the route to identify that person |
The critical output is often the blank space. A missing procurement contact may not matter early in every opportunity. It does matter if the notes show a commercial review is approaching. Likewise, an unfilled business owner is a more serious risk than a missing technical evaluator when the customer has already validated the technical approach.
4. Test relationship and influence claims
Run Map relationships and influence after roles are assigned. This prompt makes you separate a documented interaction from an interpretation of that interaction.
For example, a meeting with an executive is a fact. Calling that executive supportive is an assumption unless the notes show support. A colleague saying that someone "has influence" is useful evidence, but it still needs a validation action. Ask who else they involve, what decision they own, or whether they would introduce the relevant owner.
Use the relationship table in manager reviews. It shows whether deal progress depends on one contact, whether the account owner has recent access, and whether a supposed champion is actually active.
5. Select one next move
Run Choose the next contact last. It turns the map into an action, without pretending that every uncertain role is a reason to send another email.
The recommended person should close the most important gap in the current opportunity. That might mean validating who owns the business problem, testing an assumed decision route, or creating a route into an unrepresented review function. It is not automatically the most senior name.
Check
Check the final recommendation
You should be able to point to the evidence for the chosen contact, name the unknown you will test, and explain why the alternative route is genuinely different.
6. Know when the output is wrong
Treat these outputs as wrong or incomplete when they show any of the following:
- A contact is described as supportive, influential or a champion without a quoted note, dated activity or stated source.
- A role is marked confirmed because of title alone.
- A former employee appears as an active decision-maker.
- The same person appears twice with no explanation of the difference.
- The next contact recommendation does not link to a specific coverage gap.
- The result names a decision process, budget owner or reporting line that was not in your source material.
Correct the source record or add the missing meeting evidence, then rerun only the affected prompt. Keep the prior output until you can see what changed.
If a prompt gives shallow or conflicting results, reduce the input to one account and one opportunity. Add dated notes and the exact CRM fields rather than more general background. If you need to confirm what inputs or capabilities are available in the environment you are using, check the xAI documentation.
