WEBVTT

1
00:00:00.160 --> 00:00:01.568
The conversation went well.

2
00:00:01.748 --> 00:00:02.879
What happens next?

3
00:00:03.119 --> 00:00:06.681
If the answer is only in your head, the follow-up can slip away.

4
00:00:06.811 --> 00:00:09.691
Give it three things: a name, a time, and a reason.

5
00:00:09.821 --> 00:00:11.891
Now you have a next step you can act on.

6
00:00:12.940 --> 00:00:13.772
Follow-ups.

7
00:00:15.640 --> 00:00:21.763
Tell Mish to remind you about Sarah on Friday at nine, with the starter program and her budget as the reason.

8
00:00:21.893 --> 00:00:26.885
The useful detail stays with the reminder, so you know what the next conversation is about.

9
00:00:27.840 --> 00:00:30.507
Mish saves the reminder against Sarah’s record.

10
00:00:30.637 --> 00:00:34.477
You can see the reminder in her history, alongside the conversation.

11
00:00:34.607 --> 00:00:36.953
Check the Friday time in Mish’s reply.

12
00:00:37.083 --> 00:00:40.518
When the reminder comes due, the next step already has context.

13
00:00:41.480 --> 00:00:44.125
Sarah replies and you agree on the next step.

14
00:00:44.255 --> 00:00:46.730
Tell Mish to mark that follow-up reminder done.

15
00:00:46.860 --> 00:00:51.980
Closing the reminder keeps the pending work clear, while the person’s history stays in place.

16
00:00:53.480 --> 00:00:56.531
The record now shows that Sarah’s reminder was checked off.

17
00:00:56.661 --> 00:00:59.989
The note and her earlier conversation stay in the history.

18
00:01:00.119 --> 00:01:04.833
You can see what happened, and the finished reminder no longer sits among your pending work.

19
00:01:05.800 --> 00:01:10.749
When Sarah replies, log what happened and set the next reminder if she needs more time.

20
00:01:10.879 --> 00:01:12.863
Review any message before you send it.

21
00:01:12.993 --> 00:01:18.348
A steady follow-up process helps you return at the right time with something useful to say.