CRM pipeline and quiet deals
Esta página aún no está disponible en tu idioma.
John can read a connected CRM and flag deals that stalled. Sending to a customer still waits for you.
Prerequisites
Section titled “Prerequisites”- CRM connected in Connections
- Slack or Telegram
- Optional: mail connected if you want him to draft follow-ups
Example ask
Section titled “Example ask”Pull this week’s pipeline. Flag deals that went quiet (no activity in 14 days). For each quiet deal: last activity, owner, and one suggested next step. Do not email anyone until I say so.
What John can read
Section titled “What John can read”Records the connected CRM allows for your login. Permission-aware: he should not see what you could not see in the CRM yourself.
What needs approval
Section titled “What needs approval”Creating or updating CRM records, and sending mail. The snapshot itself is a read.
Expected output
Section titled “Expected output”A list or table of quiet deals plus a recommended action you can accept.
Credits and limits
Section titled “Credits and limits”CRM reads and AI spend. Quality depends on how complete the CRM is. There is no dedicated “sales playbook” you must enable; a clear brief is enough. Skills.