Bot de seguimiento de ventas
Un Grok Bot que revisa tu pipeline a las 8:00 y redacta cada seguimiento y cada empujón.
por GetKits
Mira la diferencia
8:00: el Bot encuentra las oportunidades que se enfriaron
Antes
Jue 15 oct, 8:00 ET. Gmail: propuesta de Acme enviada el mar 6 oct, sin respuesta. Plan piloto de Orbit enviado el vie 9 oct, sin respuesta. Correcciones del contrato de Fernway con su equipo legal desde el 29 sep, la fecha de cierre era el 30 sep. Más 26 hilos de proveedores, boletines e internos.
Después
1. Fernway, Negociación: legal lleva 12 días hábiles con las correcciones y la fecha de cierre del 30 sep ya pasó. Decisión para ti: ¿pedir a Elena que fije una fecha con legal, o mover la fecha de cierre? 2. Acme, Propuesta, Lena Ortiz: último correo tuyo el mar 6 oct (7 días hábiles). Siguiente: Empujón 1, valor nuevo: Respuesta, el informe SOC 2 para Raj. 3. Orbit, Demo, Sam Patel: último correo tuyo el vie 9 oct (4 días hábiles). Siguiente: Empujón 1, valor nuevo: Recurso, una hoja con su cierre de 9 días y 4 personas.
Champion quiet after three nudges, so the Bot writes to IT, not the CFO
Antes
You, Tue Nov 3, 8:40 AM ET: /Stalled-deal nudge Northwind. Or should I just email Mark? On the Oct 5 call Priya asked how SCIM works with Okta. It does, about 20 minutes to set up. Gmail, the Northwind proposal thread: Tue Oct 13, proposal to Dana Ruiz (VP Operations), Cc Mark Chen (CFO): 20 seats, $16,800/yr or $15,120/yr on a 3-year term. Your nudges to Dana: Fri Oct 16 (3-year cost comparison for Mark), Wed Oct 21 (sign by Wed Dec 9 to be live before Jan 4), Thu Oct 29 ("Is the Jan 4 start still the plan?"). No reply, no out-of-office. Google Calendar: Mon Oct 5, discovery call with Dana and Priya Shah (IT Systems Manager, per her signature), both in Chicago.
Después
DECISION Deal: Northwind, Proposal, $16,800/yr They asked: nothing. Dana has not answered the Oct 13 proposal or three nudges, and you asked about writing to Mark. Options: (a) Second-contact email to Priya, Dana on Cc (drafted below) (b) Ask Dana in the thread whether Mark should join a call (c) Email Mark directly: he is the CFO and senior to Dana, so it goes around her Trade: none needed; no concession is on the table Recommendation: (a). Priya was on the Oct 5 call and is not senior to Dana, so Dana stays in charge. Needed by: today, so the email goes out by 10:00 AM CT EMAIL Subject: Northwind: SCIM with Okta, 20-minute setup To: Priya Shah <[email protected]> Cc: Dana Ruiz Attach: SCIM setup sheet for Okta [confirm attachment] Send: today, Tue Nov 3, by 10:00 AM CT Hi Priya, On our Oct 5 call you asked how SCIM would work with Okta. It is supported, and setup takes about 20 minutes. The attached sheet walks through your side of it, step by step. Would it help to go through it together for 20 minutes, Thu Nov 5 at 10:00 AM CT or Fri Nov 6 at 9:00 AM CT? Jordan CRM NOTE Contacts: Dana Ruiz, VP Operations, Champion; Mark Chen, CFO, Economic buyer; Priya Shah, IT Systems Manager, Technical buyer (second contact from today) Next step: Thu Nov 5 or Fri Nov 6, 20-min SCIM setup walkthrough with Priya, owner Jordan Risk: champion silent through three nudges; nothing from Mark since the proposal Summary: No reply from Dana to the Oct 13 proposal or the nudges on Oct 16, 21 and 29. Second-contact email to Priya Shah (IT) with the SCIM setup sheet, Dana on Cc. Writing to Mark stays your decision. REMINDER Check: Wed Nov 4, 12:00 PM ET (one business day before the first proposed slot) If no reply: release the holds and send nothing extra. The break-up (T5) to Dana is due Tue Nov 10, 5 business days after this email If they reply: send the invite for the slot Priya picks, with Dana added, once you approve Hold: Thu Nov 5, 11:00 to 11:20 AM ET and Fri Nov 6, 10:00 to 10:20 AM ET (tentative; create only after you approve) CONFIRM 1. Is the SCIM setup sheet for Okta ready to attach?
5:30 PM sweep: a demo you forgot to follow up on
Antes
Tue Oct 6, 5:30 PM ET, End-of-day post-call sweep. Google Calendar: "Orbit demo", 2:00 to 2:45 PM ET, with Sam Patel (Head of Finance Ops) and Jo Rivera (Controller), orbit.example. Gmail: no email to orbit.example since the demo. Sam's Oct 5 email: "we close the books in 9 days with 4 people. I want 6." Your message to the Bot at 2:50 PM: "orbit: loved approvals from email. jo worried about netsuite sync. want pilot w/ 2 entities. I owe pilot plan by fri"
Después
EMAIL Subject: Orbit demo: approvals, NetSuite and a 2-entity pilot To: Sam Patel <[email protected]> Cc: Jo Rivera <[email protected]> Attach: none Send: today, Tue Oct 6, by 6:00 PM ET Hi Sam, Your goal of closing the books in 6 days instead of 9 framed today's demo, so here is where we landed: - Approvals from email: the part you liked most - NetSuite sync: Jo's open question [confirm answer before sending] - Pilot: 2 entities, as you suggested Open items: - Me: the pilot plan with dates, by Fri Oct 9 Would Tue Oct 13 at 10:00 AM ET or Wed Oct 14 at 2:00 PM ET work to walk you and Jo through the plan? Jordan CRM NOTE Deal: Orbit, 2-entity pilot Stage: Demo (unchanged; moves to Proposal when they ask for pilot pricing) Amount: [confirm] Close date: [confirm] (no date discussed) Contacts: Sam Patel, Head of Finance Ops, Champion; Jo Rivera, Controller, Technical buyer (new today) Pain: Close takes 9 days with 4 people; Sam wants 6 Their words: "We close the books in 9 days with 4 people. I want 6." (Sam, Oct 5) Decision: Gap Objections: NetSuite sync (Jo; answer before the pilot plan) Competition: none mentioned Next step: Tue Oct 13 or Wed Oct 14, pilot plan review with Sam and Jo, owner Jordan Risk: Jo's NetSuite concern could block the pilot Gaps: who signs; budget; pilot success criteria; which 2 entities Summary: Demo with Sam Patel and Jo Rivera. Approvals from email landed; Jo raised NetSuite sync. They want a 2-entity pilot; pilot plan due Fri Oct 9. REMINDER Check: Fri Oct 9, 9:00 AM ET (the pilot plan you promised is due) If no reply: send the pilot plan as promised, with the NetSuite answer for Jo, and repeat the two times If they reply: book the time they pick once you approve; the plan still goes out by Fri Oct 9 Hold: Tue Oct 13, 10:00 to 10:30 AM ET and Wed Oct 14, 2:00 to 2:30 PM ET (tentative; create only after you approve) CONFIRM 1. Do NetSuite journal entries sync both ways? Jo will ask again. 2. Did pricing or timing come up? Amount and Close date are empty.
Prep brief for a call with two new attendees
Antes
You: /Meeting prep brief my 11:00 with Lumen tomorrow. Google Calendar: "Lumen demo", Tue Oct 20, 11:00 to 11:30 AM CT, with Ava Kim plus two new attendees, Marco Diaz and Grace Liu (lumenhealth.example). Gmail: Oct 6 recap to Ava (6 clinics, 18% new-patient no-shows, goal under 10% before 2 spring openings, BAA required). Ava on the call: "My front desks spend every morning on the phone." Case study sent Oct 6. Ava, Oct 14: "Send something I can share with my clinic managers." One-pager sent Oct 15. No pricing discussed.
Después
PREP BRIEF Meeting: Lumen Health, demo for clinic managers, Tue Oct 20, 11:00 to 11:30 AM CT (12:00 PM ET) Attendees: Ava Kim, Director of Patient Ops, Champion, met Oct 6; Marco Diaz, role unknown [confirm], new; Grace Liu, role unknown [confirm], new Where it stands: Discovery. Last two touches: case study (Oct 6), one-page summary for clinic managers (Oct 15). You owe: an answer on the BAA. They owe: nothing yet. Their words: "My front desks spend every morning on the phone." (Ava, Oct 6) Goal: a pilot at 1 or 2 clinics with a start date, agreed before you hang up Ask: 1. Marco and Grace: how do reminders work at your clinics today, and who makes the calls? 2. Besides Ava, who decides, and is there budget this year or next? 3. What would make a pilot a success: the no-show rate, front-desk hours, or something else? Expect: the BAA question. Answer: confirm before the call whether you sign BAAs; if yes, say so and offer the document; if not, give the date you will know by Bring: the 18% rate and the under-10% goal; page 2 of the case study (reminder timing); a 1 or 2 clinic pilot outline [confirm] Risk: two new attendees with unknown roles; no budget or decision process known yet
Qué incluye
- sales-followup-bot-setup.md
Sobre este Kit
A Grok Bot teammate that owns your sales follow-up. Every sales meeting gets a drafted recap, CRM note and dated next step by 5:30 PM. Every quiet deal gets a nudge with something new at 8:00 AM. Nothing is sent until you send it. Setup takes about 12 minutes, from a template link or by hand.
What you get
- A setup file that builds the Bot step by step, or shows exactly what the template link installs.
- A profile with the durable rules: what the Bot owns, what needs your approval, and the tone it writes in.
- Four skills, each with when to use it, inputs, steps, validation, output and approvals:
- Post-call follow-up: notes, transcript or a two-line message in, then EMAIL, CRM NOTE and REMINDER out. With no notes, it asks four questions instead of guessing.
- Pipeline check: deals where you sent last and got no reply for 3+ business days, deals with no next step, and deals at risk, with up to 5 nudge drafts.
- Stalled-deal nudge: reads the whole thread, picks a new value you have not used yet, and knows when to write to a second contact or send the break-up.
- Meeting prep brief: attendees, where the deal stands, their words, one goal, three questions, the likely objection.
- Three routines, all in your time zone, and all report a failure instead of reusing old data:
- Weekday morning pipeline check, 8:00 AM, with prep briefs for today's meetings.
- End-of-day post-call sweep, 5:30 PM, which catches every meeting without a follow-up.
- Friday pipeline review, 2:00 PM, with the week's numbers: recap speed, reply rate, deals with no next step.
- The playbook inside the skills: stage cadence, the value ladder, word limits, banned phrases and the same output blocks as the Sales Follow-up Skill and Dot.
- A test run with expected results, 10 everyday prompts and a troubleshooting list.
What a morning looks like
You open Grok Bot at 8:05. One message is waiting: Fernway is at risk and needs your decision, Acme and Orbit each have a nudge drafted with a different new value, Lumen has no next step and a draft that proposes one, and your 11:00 has a prep brief. You read, edit, and send three emails from Gmail. That is the follow-up done for the day.
Who it is for
- Account executives and founders who work from Gmail and Google Calendar and run more deals than they can track in their head.
- Sellers with no sales ops support, who need the pipeline check to happen without remembering to do it.
- Teams: share it as a Team-only template so every rep runs the same follow-up rules.
What it will not do
- Send, reply, forward, archive or delete email, or book, move or decline meetings without your approval in the chat.
- Update your CRM. It writes the CRM NOTE with your CRM's field names; you paste it.
- Offer discounts, change terms, or answer legal and security questions. Those come to you as a DECISION.
- React the second a meeting ends. The 5:30 PM sweep catches the day's meetings; for an instant draft, message the Bot right after the call.
- Work without the Grok Bot desktop app. If you live in ChatGPT, the Sales Follow-up Dot does the same job there.
Reseñas
Aún no hay reseñas.
Más Kits de Ventas
Kit de seguimiento de ventas
Cada llamada de ventas acaba con un seguimiento enviado, un próximo paso con fecha y una nota de CRM limpia.
Dot de seguimiento de ventas
Tu ChatGPT dot redacta el seguimiento y la nota de CRM después de cada reunión de ventas.
Skill de seguimiento de ventas
Pasa de notas de llamada desordenadas a un correo de seguimiento, nota de CRM y próximo paso con fecha.