Turn sales notes into a useful team handoff
Create a compact account summary that preserves unanswered questions and records the next owner.
Start with these inputs
- Anonymized sales-call notes
- Your handoff fields
- Confirmed next owner and next action
Follow the workflow
- Select the relevant notes and replace personal details that are unnecessary for this draft.
- Run the prompt in a new Gemini chat.
- Check the handoff against the notes, especially requirements and timeline.
- Paste only verified fields into your team’s agreed handoff system.
Your starting prompt
Format these notes as a handoff to [team]. Use these fields: stated need, current process, confirmed requirements, timeline, decision process, open questions, next action, owner. For every material detail, retain a source-note reference. Use "Not confirmed" where the notes do not establish an answer. Do not infer deal value, probability, budget, approval, or contract status. Do not update a CRM. Handoff fields or rules: [paste] Notes: [paste]
What the output could look like
Illustrative example, not a recorded test result.
Illustrative example using invented sample inputs:
Stated need: a repeatable way to summarize weekly requests.
Budget: Not confirmed.
Next action: share a sample output for review.
Owner: Jordan, as named in the notes.
Review before you use it.
A polished summary can hide uncertainty. Keep unconfirmed fields explicit and follow your organization’s rules for customer data. Time is an approximate planning estimate, not a measured result. Free access has usage limits; features can vary by account.
A polished summary can hide uncertainty. Keep unconfirmed fields explicit and follow your organization’s rules for customer data. Time is an approximate planning estimate, not a measured result. Free access has usage limits; features can vary by account.
Sources & review notes
- Google: use Gemini Apps and refine responses ↗
- Google: Gemini Apps limits and free feature availability ↗
By AI Flow Finder · Reviewed October 14, 2026. Documented means this guide is based on the sources above. It has not yet passed a recorded end-to-end workflow test. Tool access and limits can change.