[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"blog-post-zh-\u002Fsales-follow-up-email":3},{"page":4,"surround":714},{"id":5,"title":6,"authors":7,"badge":10,"body":11,"date":697,"demo-cta":698,"description":699,"extension":700,"genre":701,"heroOrder":702,"icp":703,"image":706,"meta":707,"navigation":708,"no-translate":698,"path":709,"rank-country":702,"rank-keywords":702,"rank-tag":702,"seo":710,"stem":711,"updated":702,"video":712,"__hash__":713},"blog_zh\u002Fblog\u002Fsales-follow-up-email.md","销售跟进邮件：通话后的模板，以及如何让总结报告自动发送 (2026)",[8],{"name":9},"The Mind.com Team","Guide",{"type":12,"value":13,"toc":676},"minimark",[14,19,27,30,33,37,40,56,59,61,64,69,171,175,259,263,303,307,350,354,433,435,438,441,444,447,450,452,456,464,467,470,472,476,479,499,510,514,517,540,543,545,548,551,558,565,567,570,576,582,588,594,600,606,608,611,650,652],[15,16,18],"h1",{"id":17},"销售跟进邮件通话后模板以及如何让通话纪要自动发送-2026","销售跟进邮件：通话后模板，以及如何让通话纪要自动发送 (2026)",[20,21,22,26],"p",{},[23,24,25],"strong",{},"销售跟进邮件","是销售人员在通话或会议后发送的消息，用于重述讨论的内容、确认决定的事项，并在对话冷却之前——附上日期——敲定下一步。这是销售中以书面形式完成的部分，而在大多数销售管道中，交易往往在这里悄然停滞：通话很顺利，邮件却是在两天后凭记忆写出的，而下一步则是“我会再联系您”。",[20,28,29],{},"本指南分为三个部分。邮件需要包含的内容以及针对常见情况的五个模板。何时发送以及发送频率。以及最耗时的部分——通话纪要——它可以使用会议链接和密件抄送地址自动为您生成并存入您的 CRM 中。",[31,32],"hr",{},[34,35,36],"h2",{"id":36},"销售跟进邮件需要包含什么",[20,38,39],{},"按顺序包含四件事。其他都是可选的。",[41,42,43,47,50,53],"ol",{},[44,45,46],"li",{},"**您听到了什么。**用两三行文字以对方的措辞重述潜在客户的现状和问题。这句话证明您倾听了，也是潜在客户会向内部转发的那一句。",[44,48,49],{},"**决定了什么。**通话中达成的任何共识，每项一句话。“已达成共识”和“仍有待解决”要分开写。",[44,51,52],{},"**下一步，附上日期。**周四进行演示，周五前提供提案，下周与其运营主管通话。没有日期的下一步只是一厢情愿。",[44,54,55],{},"**一个请求。**确认日期、发送文件、介绍同事。仅限一个——包含三个请求的跟进邮件往往一个也得不到回复。",[20,57,58],{},"保持篇幅简短，无需滑动即可在手机上阅读。录音、演示文稿和完整笔记应以链接形式提供，而不是作为附件。",[31,60],{},[34,62,63],{"id":63},"五个销售跟进邮件模板",[65,66,68],"h3",{"id":67},"_1-发现通话后","1. 发现通话后",[70,71,72,86,93,96,146,152,166],"blockquote",{},[20,73,74,77,78,82,83],{},[23,75,76],{},"主题："," 回顾与下一步 — ",[79,80,81],"span",{},"公司名称"," \u002F ",[79,84,85],{},"贵公司名称",[20,87,88,89,92],{},"您好 ",[79,90,91],{},"姓名","，",[20,94,95],{},"感谢您今天的时间。我的体会如下：",[97,98,99,122,132],"ul",{},[44,100,101,102,105,106,109,110,113,114,117,118,121],{},"您在 ",[79,103,104],{},"团队"," 中推行 ",[79,107,108],{},"流程","，当出现 ",[79,111,112],{},"问题"," 时就会中断——大约 ",[79,115,116],{},"频率","，代价是 ",[79,119,120],{},"影响","。",[44,123,124,125,128,129,121],{},"您尝试过 ",[79,126,127],{},"他们尝试的方法","；但未能奏效，因为 ",[79,130,131],{},"原因",[44,133,134,135,138,139,142,143,121],{},"决策需要 ",[79,136,137],{},"姓名\u002F职务"," 参与，您希望它在 ",[79,140,141],{},"时间表"," 前落实，因为 ",[79,144,145],{},"驱动因素",[20,147,148,149,121],{},"基于此，我认为这正是我们擅长解决的问题——具体而言 ",[79,150,151],{},"一句话说明",[20,153,154,155,158,159,161,162,165],{},"下一步：在 ",[79,156,157],{},"日期，时间"," 安排一场演示，",[79,160,91],{}," 参与，重点关注 ",[79,163,164],{},"该问题","。我现在就发送邀请；如果时间不合适请回复。",[20,167,168],{},[79,169,170],{},"您的姓名",[65,172,174],{"id":173},"_2-演示后","2. 演示后",[70,176,177,189,193,202,223,237,255],{},[20,178,179,181,182,184,185,188],{},[23,180,76],{}," 针对您 ",[79,183,112],{}," 的 ",[79,186,187],{},"产品"," —— 我们展示了什么以及下一步",[20,190,88,191,92],{},[79,192,91],{},[20,194,195,196,198,199,201],{},"感谢 ",[79,197,91],{}," 的加入。对 ",[79,200,112],{}," 而言重要的部分：",[97,203,204,213],{},[44,205,206,209,210,121],{},[79,207,208],{},"功能\u002F流程 1"," —— 它如何处理 ",[79,211,212],{},"他们的场景",[44,214,215,218,219,222],{},[79,216,217],{},"功能\u002F流程 2"," —— ",[79,220,221],{},"他们的问题","，已解答。",[20,224,225,226,229,230,233,234,236],{},"仍有待解决：",[79,227,228],{},"他们提出的问题"," —— 我将在 ",[79,231,232],{},"日期"," 前与 ",[79,235,104],{}," 确认。",[20,238,239,240,243,244,246,247,250,251,254],{},"您提到了 ",[79,241,242],{},"决策流程","。在 ",[79,245,232],{}," 前提供一份涵盖 ",[79,248,249],{},"范围"," 的提案是有用的下一步，还是您希望先与 ",[79,252,253],{},"职务"," 进行第二次会谈？",[20,256,257],{},[79,258,170],{},[65,260,262],{"id":261},"_3-当他们沉默时","3. 当他们沉默时",[70,264,265,273,277,296,299],{},[20,266,267,269,270],{},[23,268,76],{}," 回复：",[79,271,272],{},"之前的主题",[20,274,88,275,92],{},[79,276,91],{},[20,278,279,280,282,283,285,286,288,289,291,292,295],{},"当我们在 ",[79,281,232],{}," 交谈时，",[79,284,112],{}," 让您付出了 ",[79,287,120],{}," 的代价，而您希望在 ",[79,290,141],{}," 前解决它。自 ",[79,293,294],{},"演示\u002F提案"," 以来我一直没有收到您的回复——这通常意味着优先级发生了变化，或者我发送的内容中有不合适的地方。",[20,297,298],{},"两种情况都没问题。如果是第二种，请告诉我哪里不合适，我会进行调整；如果是第一种，请告诉我何时再次跟进，在此之前我不会打扰您。",[20,300,301],{},[79,302,170],{},[65,304,306],{"id":305},"_4-在发给我一些资料之后","4. 在“发给我一些资料”之后",[70,308,309,314,318,328,346],{},[20,310,311,313],{},[23,312,76],{}," 您要的资料 —— 以及它无法回答的一个问题",[20,315,88,316,92],{},[79,317,91],{},[20,319,320,321,324,325,121],{},"如约附上：",[79,322,323],{},"回答他们问题的那份文件的链接","。它涵盖了 ",[79,326,327],{},"内容",[20,329,330,331,334,335,337,338,341,342,345],{},"它无法回答的一点是，这如何应用于 ",[79,332,333],{},"通话中提到的他们的具体情况","。这大约需要与 ",[79,336,253],{}," 交流二十分钟——",[79,339,340],{},"日期选项 1"," 或 ",[79,343,344],{},"日期选项 2"," 方便吗？",[20,347,348],{},[79,349,170],{},[65,351,353],{"id":352},"_5-缺席决策者的会议后","5. 缺席决策者的会议后",[70,355,356,369,373,380,415,429],{},[20,357,358,360,361,364,365,82,367],{},[23,359,76],{}," 给 ",[79,362,363],{},"缺席者姓名"," 的摘要 —— ",[79,366,81],{},[79,368,85],{},[20,370,88,371,92],{},[79,372,91],{},[20,374,375,376,379],{},"以下是您可以转发给 ",[79,377,378],{},"缺席者"," 的简短版本：",[97,381,382,391,399,407],{},[44,383,384,387,388,121],{},[23,385,386],{},"问题："," ",[79,389,390],{},"用他们的措辞概括的一句话",[44,392,393,387,396,121],{},[23,394,395],{},"我们将改变什么：",[79,397,398],{},"一句话",[44,400,401,387,404,121],{},[23,402,403],{},"成本\u002F节约：",[79,405,406],{},"数字，如果有",[44,408,409,387,412,121],{},[23,410,411],{},"目前已达成的共识：",[79,413,414],{},"下一步和日期",[20,416,417,418,420,421,424,425,428],{},"如果更方便的话，我可以直接向 ",[79,419,378],{}," 详解 —— ",[79,422,423],{},"日期选项","。否则我将在 ",[79,426,427],{},"商定的下一步"," 之后跟进。",[20,430,431],{},[79,432,170],{},[31,434],{},[34,436,437],{"id":437},"何时发送销售跟进邮件以及发送频率",[20,439,440],{},"**当天。**第一封跟进邮件应在双方对通话记忆犹新时发出——最理想的是在一小时内。每推迟一天，摘要就会变得更模糊，潜在客户对通话的记忆也会更淡。",[20,442,443],{},"**然后按计划行事，而非凭感觉。**在销售团队中流传的一个经验法则是“2-2-2 法则”：两天后跟进，然后是两周，再然后是两个月。数字不如原则重要——每次跟进都是在发送上一次跟进时计划好的，而不是碰巧想起来时才做的。",[20,445,446],{},"**每次跟进都要增加内容。**一个重申的问题、一份相关的文件、一个新的日期选项。“只是跟进一下”没有增加任何内容，只会让潜在客户习惯于忽略这个邮件线程。",[20,448,449],{},"**干净利落地结束。**在计划的序列之后，发送最后一封敞开大门的邮件（“告诉我何时再次跟进”）——然后停止。六个月后回来的潜在客户，回到的正是那个礼貌结束的邮件线程。",[31,451],{},[34,453,455],{"id":454},"最耗时的部分通话纪要","最耗时的部分：通话纪要",[20,457,458,459,463],{},"上面的每个模板都以同一个模块开始——",[460,461,462],"em",{},"您听到了什么","。把它写好所花的时间比邮件其余部分加起来还要长，因为这意味着要在一边主持通话一边记笔记的情况下，重构通话内容。被跳过的通话纪要正是跟进邮件迟发两天且言之无物的原因。",[20,465,466],{},"如果通话在 InterMIND 中进行，通话纪要在会话结束时生成：一份带有标题、概述、关键要点、带时间戳的分段要点、行动项、待解决问题和主题的回顾，会通过电子邮件发送给注册参与者。如果对话没有产生可总结的内容，则根本不会发送电子邮件。摘要可以在回顾页面上进行更正——每次编辑都是一个修订版，与 AI 原始版本有逐词差异——而更正后的文本就是回顾邮件随后显示的内容。",[20,468,469],{},"然后，跟进邮件从回顾的要点和行动项开始，而不是从记忆开始。“您听到了什么”模块只需粘贴和修剪。有一个边界值得了解：对于临时会议，仅保留最近一次会话的回顾，这与每次通话后删除其聊天记录的方式相对应；而频道会保留过去每次会话的回顾。",[31,471],{},[34,473,475],{"id":474},"无需手动记录即可将跟进内容存入-crm","无需手动记录即可将跟进内容存入 CRM",[20,477,478],{},"大多数 CRM 都接受发送至特定入站地址的电子邮件。将其放入密件抄送（BCC）字段，邮件就会记录在 CRM 与其他收件人匹配到的记录上。供应商记录了其机制和条件：",[97,480,481,487,493],{},[44,482,483,486],{},[23,484,485],{},"HubSpot"," —— 记录地址从 Settings → Objects → Activities → Email Log & Track 复制。被记录的邮件“将自动关联到收件人的联系人记录、其主要关联的公司记录，以及与该联系人关联的五个最近的未完成交易记录”；如果没有联系人与收件人匹配，则会创建一个联系人。发件人必须是 HubSpot 用户、已连接的工作电子邮件或已配置的别名。文档记录的两个限制：“当收件人被密件抄送时，该邮件不会创建新记录，且如果该收件人作为联系人存在，邮件不会被记录在其现有记录上”——匹配是基于“收件人\u002F抄送”收件人，而不是密件抄送的收件人——并且包含页眉和附件的电子邮件不能超过 40 MB。",[44,488,489,492],{},[23,490,491],{},"Pipedrive"," —— Smart Bcc 为账户提供一个通用地址，并且“您公司 Pipedrive 账户中的每个线索和交易都有其自己唯一的密件抄送地址。”“如果用于转发电子邮件的地址在 Pipedrive 中关联到了某个联系人，则被转发的电子邮件将链接到该联系人，”如果没有匹配的联系人，则“将自动创建一个新的个人联系人。”文档记录的一项要求：“必须在您的域名设置中正确配置 DKIM 或 SPF，”同步才能正常工作。在所有 Pipedrive 计划上均可用。",[44,494,495,498],{},[23,496,497],{},"Zoho CRM"," —— BCC Dropbox“为您 Zoho CRM 账户中的每个用户提供唯一的电子邮件地址。”收件人通过可配置的搜索模式进行匹配（仅联系人、仅线索，或先联系人后线索，并带有在无匹配时创建记录的选项）。文档记录的一个条件：“只有添加到已验证电子邮件地址列表中的电子邮件地址才会关联到 Zoho CRM 中的线索\u002F联系人”——发件人必须预先经过验证。关联可能需要长达 3 分钟；附件上限为 10 MB。",[20,500,501,502,505,506,509],{},"综合来看，这三者描述了相同的契约：CRM 将电子邮件存档在",[23,503,504],{},"它识别出的 To\u002FCC 收件人","的记录上，并且它只接受来自",[23,507,508],{},"它信任的发件人","的电子邮件——已验证的地址、已认证的域名或已连接的用户。",[65,511,513],{"id":512},"intermind-回顾如何满足该契约","InterMIND 回顾如何满足该契约",[20,515,516],{},"回顾邮件旨在通过这两项检查：",[97,518,519,522,528],{},[44,520,521],{},"**参与者保留在“收件人”字段中。**他们的地址是 CRM 进行匹配的依据，因此通话纪要会存入潜在客户的记录中，而不是落入未归档的收件箱。",[44,523,524,527],{},[23,525,526],{},"CRM 地址放入“回顾副本”字段中","，位于 Meetings 页面上的会议行中或频道的显示设置中。最多 10 个已确认的地址可保存在您的个人通讯录中，并可在不同会议和频道中重复使用。在每个计划上均可用。",[44,529,530,531,534,535,539],{},"**每个新地址均通过送达测试进行确认。**InterMIND 会发送一封类似于真实回顾的测试邮件；有人需要",[460,532,533],{},"在接收工具内","打开它，并在 1 小时内点击其中的确认链接。在此之前，该地址处于待定状态，不会发送任何副本。测试的存在是因为上述发件人信任条件：否则，一个通过 SMTP 接收邮件然后悄悄丢弃未经验证发件人的 CRM，看起来就像是在正常工作一样。如果测试邮件一直未到达，解决办法是在接收工具中允许 ",[536,537,538],"code",{},"noreply@intermind.com"," 作为发件人，然后再次选择该地址。",[20,541,542],{},"CRM 接收到的副本与参与者收到的电子邮件相同：摘要文本以及指向完整回顾和记录的链接。这些链接仍然需要以会议成员的身份登录——CRM 保存的是摘要，而不是进入会议的门径。",[31,544],{},[34,546,547],{"id":547},"当通话使用两种语言时",[20,549,550],{},"国际通话后的跟进邮件有一项额外的工作：它通常是潜在客户拥有的唯一书面记录。关于回顾的两个事实决定了如何处理这种情况。",[20,552,553,554,557],{},"通过电子邮件发送的回顾是",[23,555,556],{},"会议源语言的单一快照","。它链接到的回顾页面以读者自己的语言提供摘要——但该页面需要登录并具有会议成员资格，因此它是为您的团队准备的路径，而不是为仅通过链接加入一次的潜在客户准备的。没有账户的潜在客户在通话后根本收不到任何内容；他们没有接收渠道。",[20,559,560,561,564],{},"因此，您写的跟进邮件",[460,562,563],{},"就是","潜在客户的记录。用您的语言打开回顾，从其要点中编写“您听到了什么”模块，并在当天发送——潜在客户一方的通话使用的是他们的语言，而电子邮件正是双方理解以书面形式达成一致的地方。",[31,566],{},[34,568,569],{"id":569},"常见问题",[20,571,572,575],{},[23,573,574],{},"如何在销售通话后进行跟进？","\n当天，以书面形式，包含四件事：您听到了什么（用潜在客户的措辞）、决定了什么、带日期的下一步以及一个请求。然后按照计划的日程——每次跟进都增加新内容，序列以干净利落的退出结束，而不是逐渐淡出。",[20,577,578,581],{},[23,579,580],{},"如何写一封通话后的跟进邮件？","\n从通话纪要开始，而不是凭记忆：用两三行文字重述潜在客户的现状和问题，每项决定一行，下一步及其日期，以及一个请求。保持其在手机上的可读性；链接演示文稿和录音，而不是将它们作为附件。上面的五个模板涵盖了发现通话、演示、沉默、“发给我一些资料”以及缺席决策者的情况。",[20,583,584,587],{},[23,585,586],{},"销售中的 2-2-2 法则是什么？","\n在销售团队中流传的关于跟进节奏的经验法则：在最后一次联系后两天跟进，然后是两周后，再然后是两个月后。它是一项安排原则，而非测量出的定律——有用的部分在于每次跟进都是在发送上一次跟进时计划好的。",[20,589,590,593],{},[23,591,592],{},"销售跟进邮件应该多长？","\n足够短，无需滑动即可在手机上阅读：问候语、三四个要点、一个下一步、一个请求。细节存在于链接的文档中。篇幅过长是缺少通话纪要的症状——当您确切知道说了什么时，邮件自然就短了。",[20,595,596,599],{},[23,597,598],{},"通话摘要可以自动发送吗？","\n如果通话在 InterMIND 中进行，是的：当会话结束时，包含概述、关键要点、行动项和待解决问题的回顾会通过电子邮件发送给注册参与者，并且之后可以在回顾页面上进行更正。没有账户的参与者不会收到它——您发送的跟进邮件就是他们的记录。",[20,601,602,605],{},[23,603,604],{},"如何在不手动记录的情况下将跟进内容存入 CRM？","\n通过密件抄送到 CRM 的入站地址。HubSpot、Pipedrive 和 Zoho 各自记录了一个地址：只要发件人是它信任的对象，邮件就会存档在 CRM 识别出的 To\u002FCC 收件人的记录上。在 InterMIND 中，CRM 地址放在会议的“回顾副本”字段中；该地址通过在 CRM 内部打开的测试邮件确认一次，从那时起，该会议的每次回顾都会自动存档在潜在客户的记录上。",[31,607],{},[34,609,610],{"id":610},"试试看",[97,612,613,623,632,641],{},[44,614,615,622],{},[23,616,617],{},[618,619,621],"a",{"href":620},"\u002Fmeetings","发起会议并复制其链接"," —— 回顾和“回顾副本”字段位于会议行中。",[44,624,625,631],{},[23,626,627],{},[618,628,630],{"href":629},"\u002Ffeatures\u002Frecap","查看回顾包含的内容"," —— 摘要、记录和历史的实例演示。",[44,633,634,640],{},[23,635,636],{},[618,637,639],{"href":638},"\u002Fblog\u002Fdiscovery-call","阅读发现通话指南"," —— 这些模板所跟进的通话。",[44,642,643,649],{},[23,644,645],{},[618,646,648],{"href":647},"\u002Fblog\u002Fbook-a-demo","查看预约演示流程"," —— 第二个模板所跟进的演示，以及通话纪要如何到达 CRM。",[31,651],{},[20,653,654],{},[460,655,656,657,663,664,669,670,675],{},"来源：供应商文档 —— HubSpot，",[618,658,662],{"href":659,"rel":660},"https:\u002F\u002Fknowledge.hubspot.com\u002Fconnected-email\u002Flog-email-in-your-crm-with-the-bcc-or-forwarding-address",[661],"nofollow","使用 BCC 或转发地址在您的 CRM 中记录电子邮件","；Pipedrive，",[618,665,668],{"href":666,"rel":667},"https:\u002F\u002Fsupport.pipedrive.com\u002Fen\u002Farticle\u002Fsmart-email-bcc",[661],"Smart Bcc 电子邮件指南","；Zoho CRM，",[618,671,674],{"href":672,"rel":673},"https:\u002F\u002Fhelp.zoho.com\u002Fportal\u002Fen\u002Fkb\u002Fcrm\u002Fconnect-with-customers\u002Femail\u002Farticles\u002Fbcc-dropbox",[661],"BCC Dropbox","。引用的条件和限制均如那些页面上所述。已于 2026 年 9 月核查。",{"title":677,"searchDepth":678,"depth":679,"links":680},"",2,3,[681,682,689,690,691,694,695,696],{"id":36,"depth":678,"text":36},{"id":63,"depth":678,"text":63,"children":683},[684,685,686,687,688],{"id":67,"depth":679,"text":68},{"id":173,"depth":679,"text":174},{"id":261,"depth":679,"text":262},{"id":305,"depth":679,"text":306},{"id":352,"depth":679,"text":353},{"id":437,"depth":678,"text":437},{"id":454,"depth":678,"text":455},{"id":474,"depth":678,"text":475,"children":692},[693],{"id":512,"depth":679,"text":513},{"id":547,"depth":678,"text":547},{"id":569,"depth":678,"text":569},{"id":610,"depth":678,"text":610},"2026-09-02",false,"销售跟进邮件会重述通话内容、所作决定以及带有日期的下一步行动，并在当天发出。本文提供针对实际场景的五个模板、发送时机规则、如何通过 BCC 在 HubSpot、Pipedrive 和 Zoho 中将邮件同步至 CRM（附相关文档化条件），以及一种可为您自动生成通话总结并存入潜在客户记录中而无需任何人手动复制的设置方案。","md","seo",null,{"role":704,"spend":705},"sales-lead","incumbent-subscription","\u002Fblog\u002Fsales-follow-up-email.svg",{},true,"\u002Fblog\u002Fsales-follow-up-email",{"title":6,"description":699},"blog\u002Fsales-follow-up-email","howto-recap","YMT1-qYxtoZDm6kYuO0daDO5Pt59Fb0X7OE-IlyE0uw",[715,720],{"title":716,"path":717,"stem":718,"description":719,"children":-1},"如何撰写会议记录：格式、模板、示例——以及现在由谁来撰写（2026）","\u002Fblog\u002Fhow-to-write-meeting-minutes","blog\u002Fhow-to-write-meeting-minutes","会议记录是会议的正式书面记录：决定了什么、谁投票、谁在何时之前完成什么。格式、您可以复制的模板、填写完整的示例、董事会会议的附加内容——以及该格式从未提出的问题：记录以谁的语言送达？",{"title":721,"path":722,"stem":723,"description":724,"children":-1},"土耳其语语音翻译器：动词最后出现，这决定了您需要哪一款","\u002Fblog\u002Fsesli-cevirmen","blog\u002Fsesli-cevirmen","土耳其语将动词——以及否定和时态——放在句子末尾。单凭这一事实，即可区分作为“语音翻译器”出售的三类产品：手机应用、翻译耳机和实时会议翻译。它们各自能对土耳其语句子做些什么、不能做什么，以及为什么供应商支持的语言数量对此毫无参考价值。"]