Skip to main content

An AI Onboarding Buddy for New Hires

By the end of this recipe, every new hire will be greeted the moment they join, handed a checklist of assigned tasks with due dates, pointed to the handbook, and checked in on through their first weeks — all automatically, so no one's first day depends on a manager finding time. Because chat, boards, and documents live in one workspace, the buddy can welcome, assign, and follow up from a single flow.

Readiness: Available now (built as two Automations). The version where a named onboarding teammate personally guides each hire is rolling out in early access.

What it does

First impressions compound. A new hire who's greeted, oriented, and given a clear first-week checklist ramps faster and feels the difference. But onboarding is exactly the kind of task that slips when a manager is busy — so this recipe makes it run itself.

It's two automations working together:

  1. The welcome fires the instant a new member joins. It DMs them a warm hello, creates their onboarding checklist as assigned tasks with due dates, and shares the essentials — the handbook, the team directory, their first-week doc.
  2. The check-ins run on a schedule over the following weeks. At day 3, week 1, and week 2 they ask how it's going, surface anything blocking the new hire, and nudge any checklist task that's overdue.

Consistent, warm, and identical for every hire — without anyone assembling it by hand.

Build it yourself

Automation 1 — the welcome

Trigger: Workspace member joined

In Automations, start a flow with the Workspace member joined trigger so it runs automatically for every new hire.

AI step: Personalize the greeting (optional)

Add an AI → Generate step to write a warm, personal welcome using the new member's name and role. Keep it human — a few friendly sentences, not a form letter.

Action: Send the welcome DM

Add a Send direct message action to the new member with the greeting, a link to the handbook, and a one-line "here's what to do first."

Action: Create the checklist

Add Create row actions (or one batched create) on an Onboarding board — one row per onboarding task ("Set up your profile," "Read the handbook," "Meet your manager"). Assign each to the new hire and set a due date so the checklist has a rhythm.

Action: Share the essentials

Add a Share document action to give them the onboarding doc and handbook, or a Create document action to spin up a personalized "Welcome aboard!" page with their first-week plan.

Automation 2 — the check-ins

Trigger: Schedule or Date reached

Add a second automation. Use a Date reached trigger offset from the hire's Start date (fire at +3 days, +7 days, +14 days), or a Schedule that sweeps the onboarding board daily for new hires at those milestones.

Condition: Still onboarding

Add a condition so check-ins only go to people still in their onboarding window — not someone who joined months ago.

Action: Check in

Add a Send direct message action: "You're a few days in — how's it going? Anything blocking you?" Include a link to their checklist so open tasks are one click away.

Action: Nudge overdue tasks

Add a Find rows step for the hire's overdue onboarding tasks and a Send direct message (or in-app notification) reminding them what's still open — a gentle push, not a pile-up.

Or just ask Copera AI

Setting up one hire right now, or want the buddy to handle a question? Open Ask Copera AI and describe it:

"We just added Sam to the workspace. Send Sam a welcome message, create their onboarding checklist as assigned tasks on the Onboarding board with due dates over their first two weeks, and share our employee handbook with them."

Ask Copera AI drafts the message, builds the checklist, and — with Ask before acting on — shows you each step on a review card before it happens. And any time a new hire has a question, they can ask Copera AI directly and get an answer from your own handbook (see the knowledge-base answer bot recipe for that pattern).

Make it a standing teammate

Early access

Standing AI teammates are rolling out gradually. When one is available in your workspace, a named "Onboarding Buddy" teammate can personally shepherd each hire — greeting them, keeping their checklist moving, answering their questions from the handbook, and checking in — on its own, under its own identity. Until then, the two automations above deliver the same experience today. Everything here can be built now as an Automation.

Tips

tip

Make the checklist real tasks, not a static doc. Assigned rows with due dates show up in the new hire's work, can be nudged when overdue, and give a manager a live view of who's ramped. A PDF checklist can't do any of that.

tip

Let the handbook answer the FAQs. Most new-hire questions — time off, expenses, tools, who-does-what — are already written down. Pointing hires at Ask Copera AI, which answers from your own documents, unblocks them instantly and saves the team the repeat questions.

tip

Tailor the checklist by role. Add a condition on the new member's team or role so an engineer gets the repo-and-environment tasks and a salesperson gets the CRM-and-territory tasks. One automation, the right checklist for each hire.

Frequently Asked Questions

What does an AI onboarding buddy do?

When a new member joins, it sends a warm welcome, creates their onboarding checklist as assigned tasks with due dates, points them to the handbook, and checks in over their first weeks — automatically, so onboarding is consistent for every hire.

Does it trigger on its own when someone joins?

Yes. The automation starts from a "workspace member joined" trigger, so the moment a new hire is added, their welcome and checklist go out without anyone kicking it off.

Can the new hire ask it questions?

Yes. Point them at Ask Copera AI, which answers from your own handbook and onboarding documents, so a new hire gets unblocked without waiting on a person.

Does it check in after the first day?

Yes. A second scheduled automation sends check-ins at intervals you choose — day 3, week 1, week 2 — asking how it's going and nudging any checklist task that's overdue.

Do I need to build it for every role separately?

No. One automation covers everyone; add a condition on team or role to branch the checklist so each hire gets the tasks that fit their job.