How to automate a Kit presentation? A complete tutorial on registration confirmation, event reminders, and post-event follow-up.

Imagine you're going to hold a briefing next month.

After the first person registers, send them a confirmation email. A few days before the event, remind them to prepare their questions. On the day of the event, remember to send out the live stream link. After the event, those who attended will receive a summary of the key points, and those who missed it will receive a replay.

Each letter is easy to read individually. What's really easy to miss is who should receive which letter, when, and where different people should go after the event.

If this briefing is held every month or every quarter, you'll be constantly repeating the same set of confirmations, reminders, and follow-ups. That's when Kit really has the opportunity to help you take over the repetitive work.

This article will use an advisory session as an example to fully demonstrate how to use Kit to set up registration confirmation emails, event reminders, fixed dates, and post-event grouping.

You don't understand yet. Sequence,Visual Automation That's alright. We'll explain these terms first, then guide you through the setup process step by step. Even if you'll be teaching a colleague how to do it, you'll still be able to understand whether this process is reasonable.

What are Kit Sequence, Visual Automation, Tag, Date Event, and Condition?

Names in Kit	You can think of it as...	What are we going to do with it this time?
Sequence	A stack of letters arranged in order	After registration, confirmation, pre-registration, and reminder emails will be sent in sequence.
Visual Automation	A process route map	Decide where a person will go next
Tag	The note stuck next to the list	Mark this person as "registered" or "present".
Date Event	An alarm clock set on a fixed date	When the time comes, move those who are still ahead to this position, and then continue from the back.
Condition	A problem at the intersection	Ask, "Was he present?" and then take a different route.

What is a Kit Sequence?

A sequence is a set of emails arranged in order. Once someone joins, Kit will start from the first email and send them one by one according to the time interval you set.

What is Kit Visual Automation?

Visual Automation is a process roadmap. It determines where a process starts, which sequence it receives first, when it waits, and which branch it eventually ends up on.

What is a Kit Tag?

The tag is a label placed next to a subscriber. This time, it will be used to distinguish between "registered" and "attended".

What is a Kit Date Event?

A Date Event is a node for a fixed date. When the date arrives, those who are still at the beginning of the event will be moved to this node, skipping the unfinished parts and continuing from the end.

What is Kit Condition?

Condition is a judgment question in the process. This time, only one question is asked: "Did this person attend?" Different answers lead to different follow-up actions.

You don't need to memorize all these English words yet.

Just remember:Sequence is the message, Visual Automation is the path.

Write the letter first, then connect the dots. That will do.

What does the Kit presentation automation process do?

In the first paragraph, after someone signed up, four letters were received in sequence.

In the second part, when the event date arrives, those still in the pre-event process will be moved to the date point, and the unfinished parts of the process will be skipped, and the process will continue from the post-event process.

The third point is to check attendance the day after the event. Those who attended receive a summary, while those who didn't receive a replay.

What you are seeing now is the complete picture. It may seem like a lot at first glance, but that's okay; we'll break it down section by section later.

In what situations is it appropriate to use Kit to automate documentation?

I'll ask that question first.

If you only hold one event a year and only a dozen or so people register, mailing the emails yourself might be faster. Creating an automated system just for a dozen or so emails, and then having to maintain it afterwards, doesn't seem as convenient as it is.

The following situations are worth noting:

• The same type of briefing will be held repeatedly.
• They send out similar confirmation and reminder emails every time.
• I forgot to send the link, or I didn't follow up after the event.
• The consequences of those who attend and those who don't are inherently different.

Kit can only help if you feel like you're repeating the same things over and over again.

What emails are needed to automate the Kit presentation?

If it were me, I wouldn't go into the Kit and click the button right away.

I will first take a piece of paper and write down what I will definitely repeat during this briefing:

opportunity	What does the other party need now?	The task of this letter
Just registered	Confirm your registration was successful	Tell him the date and ask him to keep the calendar.
A few days before the meeting	Know what to bring	Ask him to prepare a question about where he most often stops at a certain step.
Before the meeting	First find out what will be discussed at the event.	Show him an example of a consultant process interrupted.
Approaching the event	Preparing to enter the live stream	Three things to prepare
Attendees	Knowing what to do next	Send key points for organization and a small trial run
absent	I'll add more content when I have the chance.	Sending replays and a starting problem

This table is more important than the buttons in the kit. Because tools can only guide you, they can't decide for you what the other person needs to hear right now.

What sequences and tags need to be created to automate the Kit presentation?

type	Demo name	Current status
Flowchart	DEMO | Consultant Briefing | Automation	Inactive (off), 0 subscribers
Four letters after registration	DEMO | Consultant Briefing | Post-Registration Warm-up	Inactive, 4 Drafts
Attendees Follow-up Letter	DEMO | Consultant Briefing | Attendees Follow-up	Inactive, 1 Draft
Follow-up letter for absence	DEMO | Consultant Briefing | Follow-up for those who did not attend	Inactive, 1 Draft
Registration Note	DEMO | Consultant Briefing | Registered	Demo only
Attendance note	DEMO | Consultant Briefing | Attendees	Demo only

I deliberately added a prefix to each name DEMO｜.

This way, it's immediately obvious that it's a demonstration, and it's less likely to accidentally trigger the original, official process in the account.

All processes remained inactive this time, and all six emails were drafts. No subscribers were added, and no test emails were sent out.

If you are not familiar with these statesinactive It means to turn off.Draft It's just a draft. Neither of them can be sent out yet.

How do I set up a pre-warm-up message for the Kit Sequence?

Remember? A sequence is a stack of letters arranged in order.

Go to Kit's Automation → Email Sequences and create a new Sequence.

I'll name it first:

DEMO | Consultant Briefing | Post-Registration Warm-up

There were four letters inside:

1. [DEMO] Registration complete: Please save the September 30th information session for your calendar.
2. [DEMO] First, bring a question that you most frequently repeat.
3. [DEMO] Let's first look at why an advisory process might be interrupted.
4. [DEMO] Before the presentation, please prepare these three things.

How do I set the email delay in Kit Sequence?

The first email can be sent immediately after the applicant joins. For the next three emails, I will demonstrate setting them to "one day after the previous email was sent".

When actually setting it up, you can find it in this order:

1. First, open the email you want to set in the email list on the right.
2. Find it below the main idea. Send this email.
3. Click to view the current display As soon as possible or After 1 day The field.
4. Enter the waiting time in the number field, then select from the drop-down menu. day or hour.

It's easy to make a mistake here.

On the screen 1 day It's "one day after the previous email was sent," not "the day before the event." If someone registers only the day before the event, and emails are sent out at this pace, they might still be receiving pre-event emails after the event has ended.

So we'll need a fixed date alarm, or Date Event, to bring everyone together at the same event time.

Should I select Yes or No for Kit Sequence Behavior?

In the Sequence Settings, there is a very long question:

Should subscribers added via Visual Automations stay in the email sequence?

Don't be intimidated by the English. It's simply asking, "After receiving this last letter, do these people want to stay here?"

This time we need to choose No.

We want him to receive four letters, then leave this section and continue towards the event date. If you choose Yes, he will remain in this Sequence and won't be able to receive further messages.

The operation path is Settings → Sequence BehaviorThere are two questions in this section; we'll look at the second one:Should subscribers added via Visual Automations stay in the sequence?

Please select the first one. NoThis allows subscribers to leave the Sequence after receiving the last published email.

The same page can also exclude people who shouldn't receive it, such as those who have already purchased the same service or internal test accounts.

This demo did not use any tags from the official account, nor did it borrow any real names for the visuals.

How do I set up the workflow for a Kit Visual Automation presentation?

Go to Automation → Visual Automation, select Empty Automation, and start from the blank.

Kit has ready-made templates, but it might also create a bunch of blank forms, tags, and sequences. When I already have official data in my account, I'd prefer to start from scratch and only use what I need right now.

After entering the blank Automation window, there are only two buttons in the center of the screen. First, press... Start building.

How can I use a Kit Tag as the entry point for Automation?

Here we need to define the entry point, which is "what happens before this road starts running".

Press Start building Next, Kit will ask the person how to access Automation. You will see four options: Add Form, Add Tag, Change Custom Field, or Purchase Product.

This election Tag is added.

Next click Search or create tagSearch and select DEMO | Consultant Briefing | RegisteredFinally press Add Event.

You can think of a tag as a note stuck next to the person. When Kit sees "Registered," he knows he can proceed with the process.

If the registration page is already in Kit, you can add this note directly. If the registration page is on another event platform, you need to confirm whether the "registered" signal can be sent back to Kit, for example, through a connection tool or manually.

How do I integrate Kit Sequence into Visual Automation?

After the entrance is set up, click the button below it. +Kit will let you choose one of three node types:

• EventWhen the date arrives, or when something happens, people are brought here.
• ActionWhat should Kit do next?
• ConditionAsk a question, then divide people into different routes.

This step involves sending out pre-sales emails, so select... Action → Email sequence.

Then click Search or create sequenceSearch and select DEMO | Consultant Briefing | Post-Registration Warm-upPress again Add Action.

In layman's terms:

Upon seeing someone post a "Registered" note, they began sending out those four letters.

A sequence is simply a stack of letters. Only after integrating it into Visual Automation does Kit know when to start mailing them.

How do I set up a fixed-date event for Kit Date Event?

Click again below the preheat Sequence. +This election Event → Date occurs.

Date occurs When the Kit is first opened, it will initially display the current date and time. Please change these to the actual event time and then click [the button]. Add EventThis demonstration is scheduled for 8:00 PM on September 30, 2026.

A Date Event is like an alarm clock.

When the time is up, those who haven't finished walking ahead will be brought here. This way, the pre-event warm-up won't drag on until after the event is over.

I set a second alarm for the morning after the event. This was because the attendance records might not be ready yet after the event had just ended, so I wanted to give the event platform or someone else some time to confirm them.

If you're copying a previous process, remember to check the date first. The official Kit documentation warns that if the date has passed, newcomers will skip the previous steps.

How does Kit Condition separate attendees from absentees?

After the second alarm rang, the process came to a crossroads.

Click below the second Date Event +,select ConditionThe kit will ask you whether you want to use Tags, Custom Fields, Advanced filters, or Email Opens for traffic splitting; this time, I chose... Tags.

Next, open the Tag dropdown menu, search and select. DEMO | Consultant Briefing | AttendeesPress again Add Condition.

The next step in the Condition check is: Does this person have...? DEMO | Consultant Briefing | Attendees Tag?

Once the Condition is set up, the screen will be divided into sections. Yes and No Two paths. Each of these paths must connect to an Action.

First come Yes Click below the route +,select Action → Email sequence.

Next, search and select. DEMO | Consultant Briefing | Attendees Follow-upPress again Add Action.

Then No Click below the route +same choice Action → Email sequence.

This search and selection DEMO | Consultant Briefing | Follow-up for those who did not attendPress again Add Action.

• Attendees: Sent key points for organization and the next small action.
• Absent: Send a replay and a better starting point.

This is something to pay special attention to.

Kit won't automatically know who actually attended. Attendance tags need to be added by the registration/live streaming platform, conferencing tools, or manually. The actual tools might be Zoom, Luma, Zapier, or Make, but the decision-maker just needs to confirm "who is responsible for sending the attendance signal back to Kit."

Having registered only proves that he/she has registered. Attendance still needs to be confirmed separately.

What should be checked before the Kit is automatically deployed?

After completing the process, I won't just stop when I see "Saved".

I will start from the first cell and work my way down:

• Is the entry point marked "Registered"?
• Were the four letters I received correct?
• Will you leave the Sequence after receiving the emails?
• Are the event date and account timezone correct?
• At the crossroads, is the question asking "Are you present?" or did you accidentally select "Registered"?
• Are all three sequences still inactive?
• Are all six letters still drafts?
• Are there really no subscribers in it?

The results of this readback are: Automation inactive, 0 subscribers; all three sequences are inactive; all six emails are drafts.

So right now it's a demo that can be viewed and used for teaching, but you can't send letters yet.

Kit presentation automation common problems

Kit Sequence 1 day How to calculate it?

The first letter follows the schedule of joining. The following... 1 dayIt starts counting from when the last letter was sent.

Why hasn't the Kit Sequence been shipped yet after I finished writing it?

The letter won't be mailed automatically after it's written. Someone needs to be tagged "registered" first, and then Visual Automation will send it to the Sequence.

Why didn't Kit Sequence continue after receiving the email?

Select "No" for Sequence Behavior. If you select "Yes," the person will remain here, and you won't be able to receive offers for later events.

How does Kit determine whether a registered participant has attended?

These are two different notes. Without confirmation from the event platform or personnel, don't speculate about whether he attended or not.

Why does the preceding message skip directly after copying Kit Automation?

This is especially true when replicating old events. Once the date has passed, the entire process can yield completely different results.

Which tasks should be automated and which should be handled manually during the Kit presentation?

Kit is great for handling recurring tasks, such as confirming dates, reminding people to prepare, and providing links.

I will leave these matters to the consultant's judgment:

• Where is the opponent truly stuck?
• Is this a suitable case for a paid diagnosis?
• Does he need more clarification now, or is it already time to discuss cooperation?
• What kind of invitation should be extended after the event to reflect our current relationship?

I will leave the repetitive reminders to the tools, and leave the part that requires understanding a person to myself.

Kit Instruction Meeting Automation Official Teaching Documents

• How to use Kit Visual Automations
• Creating and sending an email Sequence in Kit
• How to hold subscribers in evergreen Email Sequences
• Visual Automations: Events
• Visual Automations: Conditions
• How to use Visual Automation Templates