官方 Official 需审批 Needs approval 例行 Routine 多Agent Multi-agent Skill Skill

Grok Bot for SDRs(Cursor 写研究和初稿,Grok Bot 做后面的杂活) Grok Bot for SDRs (Cursor writes research and drafts, Grok Bot does the busywork)

Grok Bot for SDRs (Cursor writes research and drafts, Grok Bot does the busywork)

干净的名单往前走,有疑问的停下等你。 Clean contacts move ahead; questionable ones wait for you.

Grok Bot for SDRs(Cursor 写研究和初稿,Grok Bot 做后面的杂活) 预览
打开原文Open source

详细介绍Details

SpaceXAI 销售开发 Stefan Markarian 2026-09-24 官方指南:五步做外联——Cursor 云端 agent 查客户用量、丢单记录和过往通话写研究包;按这个故事找人;用写作技能起草第一封信;Grok Bot 检查每个人是否已在别的序列里或有进行中的商机,干净的标 CLEAR 进序列但不发,有问题的标 FLAG 等人看;最后他本人发。一只 Bot 一件事:总管负责每天早上的流程,一只管名单表格防止重复联系,一只发不带附言的 LinkedIn 邀请并先查每日上限。规矩:绝不自动发送,同一个问题出两次就写进技能。 Official guide by SpaceXAI SDR Stefan Markarian, Sep 24, 2026: five steps. Cursor cloud agents build a research packet from product usage, closed-lost deals, and past calls; prospects are matched to that story; first touches are drafted with writing skills; Grok Bot checks whether each person is already in another sequence or tied to an open opportunity, enrolls CLEAR contacts unsent and holds FLAGs for review; he sends himself. One job per bot: a chief of staff owns the morning run, one keeps the prospecting sheet so nobody is worked twice, one sends blank LinkedIn requests after checking caps. Rules: never auto-send, and any problem that happens twice becomes a skill update.

为什么推荐Why we recommend it 官方 Guides(2026-09-24)。收录理由:清楚示范 Cursor 和 Grok Bot 怎么分工,以及 CLEAR/FLAG 这种「干净的往前走、有疑问的停下」的分拣法,其他岗位也能用。边界:依赖 Salesforce、Gong、Nooks、Amplemarket 等付费销售工具;文中数字是作者某一天的情况。本库未实测。 Official Guides (Sep 24, 2026). Why listed: a clear split of work between Cursor and Grok Bot, and a CLEAR/FLAG triage (clean items move, questionable ones stop) that works for other roles too. Boundary: relies on paid sales tools (Salesforce, Gong, Nooks, Amplemarket); figures describe one day in the author’s work. Not tested here.

上手路径How to start

审批边界Approval boundary

研究、起草、建记录、排进序列(不发)可以自动;每一封信和每条触达都由人发。 Research, drafts, record creation, and unsent enrollment can run on their own; every email and touch is sent by a person.

  1. 先跑一次安全范围Run a safe first pass

    先在可撤回、不外发的范围内试跑。本条未批准前:研究、起草、建记录、排进序列(不发)可以自动;每一封信和每条触达都由人发。。 Try it first in a reversible, non-outbound scope. Until approved: Research, drafts, record creation, and unsent enrollment can run on their own; every email and touch is sent by a person..

  2. 存 SkillSave a Skill

    这条用法已包含可复用 Skill。跑通安全范围后,立刻把步骤固化下来。 This use already includes a reusable Skill. After the safe pass, lock the steps in.

  3. 再上 RoutineThen add a Routine

    输出稳定后再打开例行 / 定时。本条已有例行形态,不要一上来就无人值守外发。 Turn on the routine / schedule only after output is stable. This item already has a routine shape — do not start unattended outbound.

相关案例Related cases