Post: How to Automate Your New Hire Welcome Sequence in Keap: A Step-by-Step Guide

By Published On: January 12, 2026

How to Automate Your New Hire Welcome Sequence in Keap: A Step-by-Step Guide

Most onboarding failures happen in the silence between offer acceptance and day one. Your new hire signs the offer, gets a single confirmation email, and then hears nothing for two weeks — long enough to take a counter-offer or simply lose enthusiasm. The fix is a structured, automated welcome sequence that starts the moment the offer is accepted and runs through the 90-day integration milestone.

This guide shows you exactly how to build that sequence in Keap — from tag architecture through campaign construction, conditional logic branching, and the internal task notifications that keep managers and IT accountable. It is the operational layer underneath the broader Keap recruiting automation blueprint we cover in the parent pillar.


Before You Start

Before building a single campaign step, confirm these prerequisites are in place. Skipping them is the most common reason onboarding sequences fail in production.

  • Keap account with Campaign Builder access. The sequence described here uses Keap’s visual Campaign Builder. Both Keap Max and Keap Classic support the core functionality — see our Keap Max vs. Classic comparison for recruiting firms if you are not sure which plan you are on.
  • Custom fields defined. You need at minimum: Department, Work Location (Remote / On-Site / Hybrid), Role Level (IC / Manager), and Start Date. These drive conditional logic throughout the sequence.
  • Content drafted before you build. Writing emails inside Campaign Builder while simultaneously configuring logic is slow and error-prone. Draft all emails in a document first.
  • Internal team aligned on task ownership. Keap can notify your IT team and hiring manager automatically — but only if those people know to expect the notifications and act on them. Brief them before launch.
  • A test contact ready. Create a fake contact in Keap (e.g., “Test NewHire”) you can use to walk through every branch of the campaign before going live.
  • Time estimate: 6–12 hours for an experienced Keap user with content pre-written. Budget 15–20 hours if you are writing content during the build.

Step 1 — Map Every Existing Onboarding Touchpoint

Audit what your HR team currently does manually between offer acceptance and the 90-day mark before automating anything. Automating a broken process creates a faster broken process.

List every email sent, every phone call made, every form collected, every task assigned to IT or a manager, and every piece of information given to a new hire — along with the timing and who currently owns each item. Research from Asana’s Anatomy of Work Index consistently shows that knowledge workers spend a significant portion of their week on work about work — status updates, follow-ups, and coordination — rather than the job itself. Onboarding administration is a textbook example of that pattern.

From your audit, you will find three categories:

  • Automate fully: Timed emails, document links, system access notifications to IT, parking/building access instructions. No human judgment required.
  • Automate + flag: Check-in surveys, satisfaction pulse questions. The automation sends the form; a human reviews the responses and acts on red flags.
  • Keep human: First-day lunch with the manager, 90-day performance conversation, culture mentorship. These are high-value interactions — automation frees time to do them better, not replace them.

Output of this step: A documented touchpoint map with timing (day -14, day 0, day 1, day 7, day 30, day 60, day 90) and ownership (HR auto, manager auto-notification, HR human, IT auto-notification).


Step 2 — Build Your Tag and Custom Field Architecture in Keap

Tags are the engine of Keap onboarding automation. Every campaign trigger, every conditional branch, and every milestone checkpoint runs on tags. Get this architecture right before touching Campaign Builder.

Trigger Tags

  • Onboarding - Offer Accepted — Applied by HR when the offer is signed. This tag starts the entire sequence.
  • Onboarding - Started — Applied on day one (either manually or via a dated automation).

Milestone Tags (applied by form completion or campaign logic)

  • Onboarding - 30-Day Complete
  • Onboarding - 60-Day Complete
  • Onboarding - 90-Day Complete

Conditional Routing Custom Fields

  • Department — Text or dropdown. Drives content branching.
  • Work Location — Dropdown: Remote / On-Site / Hybrid. Drives logistics branching.
  • Role Level — Dropdown: Individual Contributor / Manager. Drives content depth.
  • Start Date — Date field. Used to calculate delays from a known date rather than tag application date where needed.

Keep tag names consistent and prefixed with “Onboarding -” so they are easy to filter. This discipline pays off when you have 40 tags in your account and need to find these quickly. For broader context on structuring candidate management workflows in Keap, the sibling satellite covers tag architecture across the full recruiting lifecycle.


Step 3 — Build the Pre-Boarding Segment (Days −14 Through Day 0)

The pre-boarding segment starts the moment the Onboarding - Offer Accepted tag is applied and runs until the start date. Its job is to make the new hire feel employed — not just offered a job.

Campaign Entry Point

In Campaign Builder, create a new campaign. Set the Goal (entry trigger) to: Contact is tagged with Onboarding - Offer Accepted. This is the only trigger. Every subsequent action flows from here.

Pre-Boarding Email Sequence

Email 1 — Immediate (Day 0, within 1 hour of tag): A personalized welcome from the hiring manager or CEO. Short — 150 words maximum. Confirms the start date, expresses genuine enthusiasm, and previews what happens next. Include a direct reply-to so the new hire can ask questions immediately. According to Harvard Business Review, extended onboarding programs and early connection touchpoints significantly improve new hire confidence and time-to-productivity.

Email 2 — Day −10 (3–4 days after tag if start date is two weeks out): Practical logistics. Work location details (office address and parking, or equipment shipping confirmation for remote), dress code, first-day schedule, and who to ask for when they arrive or who their Slack/Teams point of contact is. This email should be branched by Work Location — see Step 5 for conditional logic setup.

Email 3 — Day −5: Team introduction. Include photos, names, roles, and one personal detail about each teammate (their favorite project, their go-to lunch spot, their time zone). This removes the awkwardness of not knowing who anyone is on day one.

Email 4 — Day −1: A simple “we’re ready for you” message. Confirm the start time, first-day agenda, and one action item (e.g., “Download Slack before tomorrow”). Keep it short. The goal is confidence, not information overload.

Internal Notification: IT Provisioning

Immediately after Email 1 (or on the same day), add an Internal Notification action in Keap addressed to your IT team’s email alias. The notification should contain: new hire name, start date, department, role, work location (remote needs equipment shipped; on-site needs badge and desk setup), and required system access list. This fires automatically — no HR follow-up required.

Document Collection (Pre-Boarding Forms)

For sensitive HR documents — tax forms, banking details, identification verification — link to your external e-signature or HR system from within the Day −10 email rather than trying to collect these inside Keap. Keap tracks the click; the dedicated tool captures the legally compliant signature. Do not build workarounds inside Keap for documents that have legal requirements.


Step 4 — Build the First-Week Segment (Days 1–5)

The first-week segment focuses on orientation, culture immersion, and removing friction. Gartner research on employee experience consistently shows that clarity of role expectations and early peer connection are the strongest predictors of new hire engagement in the first 30 days.

Email 5 — Day 1 (Send at 6:00 AM local time):

“Welcome to your first day” message. Bullet-point first-day agenda. Link to your company handbook or culture resource (a Notion page, Google Drive folder, or intranet link works fine — embed the link, not the content). Include a direct line to their HR contact for any questions.

Email 6 — Day 3:

Culture and mission reinforcement. A short message about why the company exists and how their role connects to that mission. Include a short 2–3 minute video from leadership if available. This is the touchpoint most teams skip — and it is the one that most directly reinforces the new hire’s decision to join.

Email 7 — Day 5 (End of First Week):

A check-in from HR. Ask two questions: “What went well this week?” and “What do you wish you had known before day one?” Link to a short Keap form to capture responses. When the form is submitted, apply a tag (Onboarding - Week1 Feedback Received) and route the response to HR for review. This is the first feedback loop in the system.

Internal Notification: Manager Check-In Reminder

On Day 3, send an internal notification to the hiring manager: “Reminder: [New Hire Name] is in their first week. Suggested action: 15-minute informal check-in today.” This is a nudge, not a mandate — but it makes the manager’s job easier by surfacing the right action at the right time.

This is the same principle driving the staffing agency that cut onboarding drop-offs by 25% — structured nudges at the right moment, not manual reminders from HR.


Step 5 — Add Conditional Logic Branches by Role and Location

A single flat sequence treats a remote senior engineer the same as an on-site junior sales rep. That disconnect is detectable — and it signals that the organization does not actually know who you are. Conditional logic eliminates this.

How to Add a Decision Diamond in Keap Campaign Builder

  1. After the campaign entry tag, drag a Decision Diamond onto the canvas.
  2. Set Condition 1: Custom Field “Work Location” equals “Remote.” Connect this path to the remote-specific email sequence (equipment shipping confirmation, virtual team intro link, digital badge/access instructions).
  3. Set Condition 2: Custom Field “Work Location” equals “On-Site.” Connect this path to the on-site sequence (parking, building access, desk location).
  4. Set a Default path for contacts where Work Location is not populated — route them to the on-site sequence and trigger an internal alert to HR to update the field.

Department Branching

Add a second Decision Diamond downstream. Branch on Department to deliver role-specific resources: the Engineering new hire gets a development environment setup guide; the Sales new hire gets CRM login instructions and the sales playbook; the Operations new hire gets process documentation links. Each branch rejoins the main sequence after the department-specific email — you are not building separate campaigns, just inserting a personalized touchpoint.

The conditional logic workflows satellite covers the Decision Diamond mechanic in detail if you need a deeper reference. Using well-structured Keap email templates for consistent candidate messaging makes populating each branch significantly faster.


Step 6 — Build the Integration-Phase Segment (Days 6–90)

The integration phase is where most automated onboarding sequences end prematurely. They send a flurry of emails in week one, then go silent. McKinsey research on talent management identifies sustained engagement in the first 90 days as a critical factor in whether new hires reach full productivity — or start quietly looking for an exit.

Day 14 — Two-Week Check-In Email

Brief pulse check. Two questions: “How clear is your role so far?” and “What is one thing that would make your next two weeks better?” Link to a Keap form. On submission, apply Onboarding - 14-Day Feedback Received tag and route responses to the hiring manager and HR.

Day 30 — 30-Day Milestone Email + Survey

More substantial check-in. Ask about team integration, clarity of expectations, and any resource gaps. Link to a Keap form. On submission, apply Onboarding - 30-Day Complete tag. Trigger an internal notification to HR confirming the milestone is hit.

The absence trigger: Add a timer in the campaign — if the new hire has NOT been tagged Onboarding - 30-Day Feedback Received within 32 days of sequence start, fire an internal notification to HR: “[Name] has not completed their 30-day check-in. Manual outreach recommended.” This is your early attrition radar.

Day 60 — 60-Day Milestone Email

Focus on performance and development. Ask about progress toward 60-day goals (which should have been set in week one), any skill gaps, and interest in development resources. Apply Onboarding - 60-Day Complete tag on form submission.

Day 90 — 90-Day Completion Email

Celebrate the milestone. Acknowledge their contributions. Preview what comes next — the annual review cycle, career development conversations, internal mobility options. Apply Onboarding - 90-Day Complete tag. This tag is your reporting anchor: every contact with this tag completed the full sequence. Contacts without it, who should have it, are the cohort to investigate.

SHRM research consistently identifies structured 90-day onboarding programs as a primary driver of new hire retention — organizations with formal onboarding programs see substantially higher retention rates compared to those with informal or absent processes.


Step 7 — Test the Full Sequence End-to-End

Do not launch without a full end-to-end test. Onboarding sequence errors are visible — a new hire who receives the wrong email or no email on day one notices immediately, and the cost to your employer brand is disproportionate to the fix.

Testing Protocol

  1. Apply the Onboarding - Offer Accepted tag to your test contact.
  2. Verify Email 1 fires within the expected window (immediately or within 1 hour).
  3. Manually advance the test contact through each delay to confirm subsequent emails trigger correctly. In Keap, you can use the “Move to Now” option in test mode for timed sequences.
  4. Test each conditional branch: set Work Location to “Remote,” confirm the remote branch fires; change to “On-Site,” confirm the on-site branch fires.
  5. Submit each Keap form as the test contact. Confirm the correct milestone tag is applied and the correct internal notification fires.
  6. Test the absence trigger: do NOT submit the 30-day form. Confirm the HR alert fires at day 32.
  7. Verify all internal notifications arrive at the correct email addresses with the correct new hire data populated.

Log every test result. Fix before launch. Retest after fixes.


How to Know It Worked

Track these four metrics consistently for the first 90 days post-launch:

  • Email open rate by stage: Benchmark against your existing email performance. Pre-boarding emails should open at 70%+ (recipients are highly motivated). If open rates drop below 40% in the first week, subject lines or send timing need adjustment.
  • Form completion rate: Each check-in form should complete at 60%+. Below that signals the form is too long, the link is broken, or the ask is poorly timed.
  • 90-Day Complete tag rate: What percentage of new hires who enter the sequence exit with the Onboarding - 90-Day Complete tag? This is your sequence completion rate. Target 80%+ in the first quarter.
  • 90-day retention rate: Pull from your HR system — not from Keap. Compare cohorts before and after the automated sequence launch. Deloitte’s Human Capital Trends research links structured onboarding directly to retention outcomes, but your own data is the only number that matters for your organization.

Common Mistakes to Avoid

Front-loading content. Sending six emails in three days overwhelms new hires and trains them to ignore your messages. Spread content across the full 90-day window, timed to when each piece becomes relevant.

Ignoring the absence trigger. Building the positive path (what happens when everything works) without building the failure-state alerts (what happens when nothing happens) means disengaged new hires fall through the cracks undetected.

One sequence for all roles. A flat sequence with no conditional logic produces generic messages that feel like they were written for someone else. Add Department and Work Location branches minimum.

Skipping the manager notifications. HR automation without manager activation leaves the most important onboarding relationship — the direct manager relationship — unsupported. Internal notifications are not optional.

Never revisiting the sequence. Run a quarterly review of open rates, form completions, and feedback responses. Content that resonated in Q1 may be stale by Q3. The sequence is a living system, not a set-and-forget build.

The broader patterns behind reducing manual admin in recruiting — including what the Parseur Manual Data Entry Report documents about the cost of repetitive data work — apply directly here. Every manual email an HR team member sends instead of reviewing a new hire’s check-in response is a misallocation of their highest-value time.


Next Steps

Once your onboarding welcome sequence is live and stable, the natural expansion is backward integration with your recruiting pipeline. The pre-onboarding workflow automation in Keap satellite covers the handoff from candidate to new hire in detail — specifically how to pass the right data from your recruiting tags into the onboarding sequence without manual re-entry.

For teams ready to connect onboarding automation to broader HR operations — payroll triggers, benefits enrollment systems, and compliance tracking — the Keap HR integrations that reduce manual errors satellite covers the integration layer. And if you want the full picture of how onboarding fits into a complete recruiting automation stack, the essential Keap automation workflows for recruiters listicle maps all seven workflow categories in one place.

The sequence described in this guide is buildable by any Keap-proficient HR team. The OpsMap™ process we use at 4Spot Consulting identifies which onboarding steps carry the highest drop-off risk before a single campaign step is built — so the automation targets the highest-value gaps first, not just the easiest ones to automate.