How this helps you
Your CRM stays current without the end of week data entry, and nothing changes until you've approved it.
Read my notes for my call with [account] in [call notes app], plus any related email and Slack threads from the last [days]. Propose updates to [CRM] for: stage, next steps with dates, key people and their roles, pain points and risks. Show me the changes as a before and after list. Don't write anything to [CRM] until I say yes, and never delete a field.
Fill in: [account] is the customer. [call notes app] is Granola, Gong or wherever your notes live. [days] is how far back to look for related threads. [CRM] is your CRM, such as Salesforce.
What they did
In the official Grok Bot for Sales webinar, Christa from SpaceXAI's enterprise sales team shows how she stopped spending her week updating Salesforce. Her Bot reads her Granola call notes, Gong recordings, email and Slack channels for each account and keeps the account notes current. For a demo customer it picked up a proposed 30 day pilot, the executive sponsors and timeline, the pain points raised on the call, and pushed the next steps into the CRM. On 27 Oct the official @bot account described the same pattern from its own sales operations team: an Account Intel Bot that updates the CRM after calls, next to a Quote Bot for proposals and a Deal Bot that sends non-standard terms for approval.
Who it's for: Account executives, founders who sell, and customer success managers who are behind on CRM updates.
Before you start
- Your CRM connected from Connect apps (Salesforce is shown in the webinar).
- A source of call notes connected, such as Granola or Gong.
- Email and Slack connected if account talk happens there.
How to try it
- Connect your CRM and call notes app from Connect apps.
- Pick the Bot that does your account work, or create one for it.
- Tell it which CRM fields it may update and which it must never touch.
- Run the prompt below by hand on one recent call.
- Check every proposed change against what was actually said. Correct it in chat.
- Repeat on two or three more calls until the changes need no edits.
- Then ask it to do this at the end of each day for that day's calls (we haven't verified this step).
What to expect
From the webinar demo: a proposed 30 day pilot, who the sponsors are and the timeline, the pain points from the call, and dated next steps pushed to the account.
Common mistakes
- Letting it write straight to the CRM before you've checked a few runs.
- Giving it every field at once. Start with next steps and key people.
- No notes source connected, so it fills gaps from memory or guesses.
Related tips
- Two Bots that research leads and draft first emails while you sleep: One Bot finds the right person at each target company, a second writes a personal first email as a draft, and you review the pile each morning.
- Get a prep doc a few minutes before each meeting: A morning routine reads your calendar, pulls context from email and connected apps, and sends a prep doc just before each meeting starts.
- Keep an attention list instead of a priority list: An hourly routine reads your email, Slack, meetings and calendar and keeps a short list of what you are actually working on. Other Bots use it as a filter.
- Route every meeting transcript to the right Bot with a webhook: When your note taker finishes a call, a webhook wakes your Chief of Staff Bot, which reads the transcript and hands it to the Bot that owns that work.
- A people Bot that remembers everyone you meet: Tell one Bot about people as you meet them, with exact spellings, and ask it later who someone was in one line.
Worth knowingCarved from a segment of this video starting at 5:00. Paraphrased by us; watch the original for the full walkthrough.
Learn more: Grok Bot Use Cases: Real Workflows From Real Users · All Grok Bot workflows tips