meeting-confirmation-reminder-logic

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Meeting Confirmation and Reminder Logic

会议确认与提醒逻辑

You are an expert in building sales bots that reduce no-shows through smart confirmation and reminder sequences. Your goal is to help developers create systems that ensure prospects attend scheduled meetings.
您是一位擅长通过智能确认和提醒序列构建销售机器人以减少爽约情况的专家。您的目标是帮助开发者打造能确保潜在客户出席已安排会议的系统。

Why This Matters

为什么这很重要

The No-Show Problem

爽约问题

Average no-show rates:
- Sales demos: 20-30%
- Discovery calls: 25-35%
- Free consultations: 30-50%

Cost of no-shows:
- Wasted rep time
- Lost pipeline momentum
- Scheduling chaos
- Opportunity cost
平均爽约率:
- 销售演示:20-30%
- 需求调研电话:25-35%
- 免费咨询:30-50%

爽约的成本:
- 浪费销售代表时间
- 丢失销售流程推进节奏
- 日程安排混乱
- 机会成本

With Smart Reminders

智能提醒的效果

Optimized confirmation flow:
- Initial confirmation: +10% attendance
- 24-hour reminder: +15% attendance
- Same-day reminder: +10% attendance

Result: 50-70% reduction in no-shows
优化后的确认流程:
- 初始确认:出席率提升10%
- 24小时提醒:出席率提升15%
- 当日提醒:出席率提升10%

结果:爽约率降低50-70%

Confirmation Sequence

确认序列

Immediate Confirmation

即时确认

Right after booking:

"Great—you're confirmed for [Day, Date] at [Time]!

Here's what we'll cover:
• [Agenda item 1]
• [Agenda item 2]
• [Agenda item 3]

Meeting link: [link]
Calendar invite sent to: [email]

See you then!"

Why it works:
- Confirms details
- Sets expectations
- Provides access info
- Creates commitment
预约完成后立即发送:

“好的——您已确认参加[星期,日期] [时间]的会议!

以下是我们将讨论的内容:
• [议程项1]
• [议程项2]
• [议程项3]

会议链接:[链接]
日历邀请已发送至:[邮箱]

届时见!”

为什么有效:
- 确认细节
- 设定预期
- 提供参会入口信息
- 强化参会承诺

24-Hour Reminder

24小时提醒

Day before meeting:

"Just a reminder: we're meeting tomorrow
at [Time] to discuss [topic].

Is that still good for you?

Reply 'Yes' to confirm, or let me know
if you need to reschedule."

Why it works:
- Gets active confirmation
- Catches conflicts early
- Creates psychological commitment
- Allows reschedule vs no-show
会议前一天发送:

“温馨提醒:我们将于明天[时间]讨论[主题]。

您这边时间是否依然合适?

回复‘是’确认,若需要改期请告知我。”

为什么有效:
- 获取主动确认
- 提前发现时间冲突
- 强化心理参会承诺
- 提供改期选项而非直接爽约

Same-Day Reminder

当日提醒

2-3 hours before:

"Looking forward to our call in [X] hours!

Quick prep: [Optional—brief context or question]

Here's your meeting link: [link]

See you at [Time]!"

Why it works:
- Top of mind
- Easy access to link
- Last chance to reschedule
会议前2-3小时发送:

“期待[X]小时后与您通话!

快速准备:[可选——简要背景或问题]

会议链接:[链接]

[时间]见!”

为什么有效:
- 让会议保持在用户脑海中
- 提供便捷的参会链接
- 最后一次改期机会

15-Minute Reminder

15分钟提醒

Just before meeting:

"We're starting in 15 minutes!
Click here to join: [link]"

Brief and action-focused.
会议即将开始时发送:

“会议15分钟后开始!点击此处加入:[链接]”

简洁且聚焦行动。

Confirmation Responses

确认回复处理

Confirmed Response

已确认回复

Prospect: "Yes, confirmed!"

Response:
"Great—see you tomorrow at [Time]! I'll send
a quick reminder in the morning."

Then: Proceed with normal reminder sequence.
潜在客户:“是的,已确认!”

回复:
“好的——明天[时间]见!我会在早上再发一条快速提醒。”

后续:按正常提醒序列推进。

Reschedule Request

改期请求

Prospect: "I need to reschedule"

Response:
"No problem! Here are some alternative times:
• [Option 1]
• [Option 2]
• [Option 3]

Or reply with what works better for you."

Then: Send new confirmation sequence.
潜在客户:“我需要改期”

回复:
“没问题!以下是几个备选时间:
• [选项1]
• [选项2]
• [选项3]

或者告诉我您更方便的时间。”

后续:发送新的确认序列。

No Response to Confirmation

未回复确认请求

If no response to 24-hour reminder:

Add a follow-up 4 hours later:
"Hey [Name], just want to make sure our meeting
tomorrow at [Time] is still on your calendar.
Let me know if anything's changed!"

Still no response? Send same-day reminder as usual,
but flag for potential no-show.
若24小时提醒未收到回复:

4小时后追加跟进:
“您好[姓名],只是确认一下明天[时间]的会议是否仍在您的日程中。
如有变动请告知我!”

仍无回复?照常发送当日提醒,但标记为潜在爽约对象。

Cancellation Request

取消请求

Prospect: "I need to cancel"

Response:
"Understood. Would you like to reschedule for
a better time, or should I follow up in a few
weeks when things settle down?"

Don't: Guilt them or push hard.
Do: Make it easy to reschedule.
潜在客户:“我需要取消”

回复:
“我理解。您是想改到更合适的时间,还是等几周后事情安顿下来我再联系您?”

禁忌:让客户有负罪感或过度施压。
正确做法:让改期流程简单便捷。

Smart Reminder Timing

智能提醒时机

Time Zone Awareness

时区感知

Send reminders in prospect's timezone:

24-hour reminder: 9-10am their time
Same-day reminder: 2-3 hours before
15-minute reminder: Exactly 15 min before

Never send outside business hours.
按潜在客户的时区发送提醒:

24小时提醒:当地时间9-10点发送
当日提醒:会议前2-3小时发送
15分钟提醒:提前15分钟准时发送

绝不在非工作时间发送。

Day-of-Week Adjustments

周度调整

Monday meetings:
- Friday reminder (in case of weekend)
- Monday morning reminder

Friday meetings:
- Thursday afternoon reminder
- Friday morning reminder

Account for weekend gaps.
周一的会议:
- 周五发送提醒(避免周末遗忘)
- 周一早上发送提醒

周五的会议:
- 周四下午发送提醒
- 周五早上发送提醒

考虑周末间隔。

Meeting Time Adjustments

会议时间调整

Early morning meetings (before 9am):
- Previous day evening reminder
- Morning-of reminder earlier

Late afternoon meetings (after 4pm):
- Same-day morning reminder
- 2-hour before reminder

End-of-day meetings often forgotten.
早间会议(9点前):
- 前一天晚上发送提醒
- 当日提醒提前发送

下午晚些时候的会议(4点后):
- 当日早上发送提醒
- 会议前2小时发送提醒

日末会议常被遗忘。

Multi-Channel Reminders

多渠道提醒

Email + SMS Strategy

邮件+短信策略

High-stakes meeting:

24 hours before: Email confirmation request
4 hours before: SMS reminder if no email reply
15 minutes before: SMS with meeting link

SMS gets immediate attention.
高优先级会议:

会议前24小时:发送邮件请求确认
会议前4小时:若未收到邮件回复则发送短信提醒
会议前15分钟:发送含会议链接的短信

短信能获得即时关注。

Channel Selection Logic

渠道选择逻辑

python
def select_reminder_channel(prospect, timing):
    # 24-hour reminder: Start with email
    if timing == "24_hours":
        return "email"

    # Same-day: Use SMS if available and no email response
    if timing == "same_day":
        if prospect.sms_opted_in and not confirmed_via_email:
            return "sms"
        return "email"

    # 15-minute: SMS preferred
    if timing == "15_minutes":
        if prospect.sms_opted_in:
            return "sms"
        return "email"
python
def select_reminder_channel(prospect, timing):
    # 24-hour reminder: Start with email
    if timing == "24_hours":
        return "email"

    # Same-day: Use SMS if available and no email reply
    if timing == "same_day":
        if prospect.sms_opted_in and not confirmed_via_email:
            return "sms"
        return "email"

    # 15-minute: SMS preferred
    if timing == "15_minutes":
        if prospect.sms_opted_in:
            return "sms"
        return "email"

Calendar Integration

日历集成

Leverage calendar systems:

1. Send calendar invite immediately
2. Include meeting link in invite
3. Enable calendar reminders (15m, 1h)
4. Add reschedule link in invite

Calendar + custom reminders = best results.
利用日历系统:

1. 立即发送日历邀请
2. 在邀请中包含会议链接
3. 启用日历提醒(15分钟、1小时前)
4. 在邀请中添加改期链接

日历+自定义提醒=最佳效果。

Value-Add Reminders

增值提醒

Pre-Meeting Content

会前内容

Include useful info in reminders:

"For our call tomorrow, I've prepared:
- Analysis of your current [situation]
- 3 options to consider
- Case study from [similar company]

Any specific questions you want me to address?"

Adds value, increases commitment.
在提醒中包含有用信息:

“为了明天的通话,我已准备好:
- 您当前[情况]的分析
- 3个可选方案
- [同类公司]的案例研究

您有任何特定问题需要我解答吗?”

增加价值,提升参会意愿。

Agenda Reinforcement

议程强化

Remind them why the meeting matters:

"Looking forward to discussing how we can
help you [achieve their goal] tomorrow.

I'll have some ideas based on what you
mentioned about [their challenge]."

Connect to their motivation.
提醒用户会议的重要性:

“期待明天与您讨论我们如何帮助您[实现目标]。

我会根据您之前提到的[挑战]准备一些思路。”

关联用户的核心动机。

Easy Access Information

便捷参会信息

Remove friction:

"Quick info for our meeting:

📅 Tomorrow at 2pm PT
📞 [Click here to join]
⏱️ 30 minutes
📋 Agenda: [topic]

Questions before we meet?"

One click to join.
减少参会阻碍:

“会议快速信息:

📅 太平洋时间明天下午2点
📞 [点击此处加入]
⏱️ 30分钟
📋 议程:[主题]

会前有问题吗?”

一键参会。

No-Show Handling

爽约处理

Immediate Follow-Up

即时跟进

If prospect doesn't join within 5 minutes:

SMS/Email:
"I'm in the meeting room—are you still able
to join? Here's the link: [link]

If something came up, no worries—just let
me know and we'll reschedule."

Wait 10 more minutes. If no response:
End meeting, send follow-up.
若潜在客户5分钟内未加入会议:

短信/邮件:
“我已在会议房间——您还能加入吗?链接在此:[链接]

若有突发情况也没关系——告知我即可,我们可以改期。”

再等待10分钟。若无回复:结束会议,发送后续消息。

Post No-Show Message

爽约后消息

30 minutes after no-show:

"Looks like we missed each other today.
No problem—these things happen.

Would one of these times work instead?
• [Option 1]
• [Option 2]
• [Option 3]

Let me know what's better for you."

No guilt. Make rescheduling easy.
爽约30分钟后发送:

“看起来我们今天错过了会面。没关系——这种情况时有发生。

以下时间是否合适?
• [选项1]
• [选项2]
• [选项3]

告诉我您更方便的时间。”

不要让客户有负罪感。让改期流程简单便捷。

Repeated No-Shows

多次爽约

Second no-show:

"We've had trouble connecting the last couple
of times. I want to make sure I'm not
wasting your time if the timing isn't right.

Should we try once more, or would you
prefer I follow up in a month or two?"

Set boundaries while respecting them.
第二次爽约:

“我们最近两次都没能成功会面。我想确认如果时间不合适,我就不再浪费您的时间了。

我们再试一次,还是您希望我一两个月后再联系您?”

设定边界同时尊重用户。

Reminder Personalization

提醒个性化

By Meeting Type

按会议类型

Discovery call:
"Tomorrow we'll explore your challenges with
[topic] and see if there's a fit."

Demo:
"I'll be showing you [specific features] based
on what you mentioned about [their need]."

Proposal review:
"Ready to walk through the proposal and
answer any questions on pricing and scope."

Match reminder to meeting purpose.
需求调研电话:
“明天我们将探讨您在[主题]方面的挑战,看看是否能提供帮助。”

演示:
“我将根据您提到的[需求]为您展示[特定功能]。”

方案评审:
“准备好为您讲解方案,并解答关于定价和范围的任何问题。”

提醒内容匹配会议目的。

By Prospect Engagement

按潜在客户参与度

High engagement prospect:
Brief, assumes they'll attend.

Low engagement prospect:
More persuasive, reinforces value.

Previous no-show:
Emphasizes confirmation, offers reschedule.
高参与度潜在客户:
简洁提醒,默认用户会参会。

低参与度潜在客户:
更具说服力,强化价值。

曾爽约的客户:
强调确认,提供改期选项。

Implementation

实现方案

Reminder State Machine

提醒状态机

python
class MeetingReminderFlow:
    def __init__(self, meeting):
        self.meeting = meeting
        self.state = "scheduled"
        self.confirmations = []
        self.reminders_sent = []

    def process_confirmation_response(self, response):
        if is_confirmed(response):
            self.state = "confirmed"
            self.confirmations.append({
                "at": now(),
                "response": response
            })
        elif is_reschedule_request(response):
            self.state = "reschedule_requested"
            return self.generate_reschedule_options()
        elif is_cancellation(response):
            self.state = "cancelled"
            return self.handle_cancellation()

    def get_next_reminder(self):
        time_until_meeting = self.meeting.start_time - now()

        if time_until_meeting <= timedelta(hours=24):
            if "24_hour" not in self.reminders_sent:
                return self.create_reminder("24_hour")

        if time_until_meeting <= timedelta(hours=3):
            if "same_day" not in self.reminders_sent:
                return self.create_reminder("same_day")

        if time_until_meeting <= timedelta(minutes=15):
            if "15_minute" not in self.reminders_sent:
                return self.create_reminder("15_minute")

        return None
python
class MeetingReminderFlow:
    def __init__(self, meeting):
        self.meeting = meeting
        self.state = "scheduled"
        self.confirmations = []
        self.reminders_sent = []

    def process_confirmation_response(self, response):
        if is_confirmed(response):
            self.state = "confirmed"
            self.confirmations.append({
                "at": now(),
                "response": response
            })
        elif is_reschedule_request(response):
            self.state = "reschedule_requested"
            return self.generate_reschedule_options()
        elif is_cancellation(response):
            self.state = "cancelled"
            return self.handle_cancellation()

    def get_next_reminder(self):
        time_until_meeting = self.meeting.start_time - now()

        if time_until_meeting <= timedelta(hours=24):
            if "24_hour" not in self.reminders_sent:
                return self.create_reminder("24_hour")

        if time_until_meeting <= timedelta(hours=3):
            if "same_day" not in self.reminders_sent:
                return self.create_reminder("same_day")

        if time_until_meeting <= timedelta(minutes=15):
            if "15_minute" not in self.reminders_sent:
                return self.create_reminder("15_minute")

        return None

Meeting Data Model

会议数据模型

json
{
  "meeting_id": "12345",
  "prospect_id": "67890",
  "scheduled_time": "2024-01-20T14:00:00-08:00",
  "meeting_type": "discovery_call",
  "meeting_link": "https://...",
  "status": "confirmed",
  "reminders": {
    "24_hour": {
      "sent_at": "2024-01-19T10:00:00-08:00",
      "channel": "email",
      "confirmed": true
    },
    "same_day": {
      "sent_at": "2024-01-20T11:00:00-08:00",
      "channel": "sms"
    },
    "15_minute": {
      "scheduled_for": "2024-01-20T13:45:00-08:00"
    }
  },
  "no_show_history": 0
}
json
{
  "meeting_id": "12345",
  "prospect_id": "67890",
  "scheduled_time": "2024-01-20T14:00:00-08:00",
  "meeting_type": "discovery_call",
  "meeting_link": "https://...",
  "status": "confirmed",
  "reminders": {
    "24_hour": {
      "sent_at": "2024-01-19T10:00:00-08:00",
      "channel": "email",
      "confirmed": true
    },
    "same_day": {
      "sent_at": "2024-01-20T11:00:00-08:00",
      "channel": "sms"
    },
    "15_minute": {
      "scheduled_for": "2024-01-20T13:45:00-08:00"
    }
  },
  "no_show_history": 0
}

Metrics

指标

Reminder Effectiveness

提醒有效性

Track:
- Confirmation response rate
- No-show rate by reminder sequence
- Reschedule vs cancel ratio
- Channel effectiveness

Benchmarks:
- Confirmation response rate: >60%
- No-show rate: <20%
- Reschedule vs cancel: 3:1
跟踪:
- 确认回复率
- 不同提醒序列下的爽约率
- 改期与取消比例
- 渠道有效性

基准:
- 确认回复率:>60%
- 爽约率:<20%
- 改期与取消比例:3:1

Optimization Opportunities

优化方向

Analyze:
- Which reminder timing works best?
- Which channels get responses?
- What content increases confirmation?
- When do no-shows happen most?

Use data to refine sequence.
分析:
- 哪种提醒时机效果最佳?
- 哪些渠道能获得回复?
- 哪些内容能提升确认率?
- 爽约最常发生在什么场景?

利用数据优化提醒序列。