Employee onboarding workflow
Coordinate employee onboarding with tasks, calendar milestones, policy resources, internal assistant answers, and visible activity.
Use this product state to connect the visible UI to the operational decision the lesson is teaching.
Learn the system by following the product states.
Use the screenshots as the primary map: start with the full context, trace the connected workflow, inspect the focused UI, then compare against the completed operating state.
Customer signalWorkflow pathVisible outcomeUse this product state to connect the visible UI to the operational decision the lesson is teaching.
Customer signalWorkflow pathVisible outcomeThis is the state to compare against when the system is configured, connected, or ready for review.
Summary
Coordinate employee onboarding with tasks, calendar milestones, policy resources, internal assistant answers, and visible activity.
Concepts covered
Step breakdown
- Define the system to deployStart from this HR operating system and confirm the business outcome, source signals, owners, and review gates.
- Create the Frontline assetsBuild the workflow canvas, agent prompt, channels, CRM records or tables, routing logic, and Max Activity evidence described in the blueprint.
- Launch the narrow versionDeploy the smallest reliable version first, keep human review visible, then use activity and analytics to expand the system.
What you will build
An employee onboarding workflow that creates structured onboarding tasks at key milestones (Day 1, Day 7, Day 30), answers common onboarding questions through an internal AI assistant using approved policy resources, routes People-team follow-up for required approvals, and tracks completion in Max Activity.
After deployment: when a new hire's start date arrives, Frontline automatically creates their onboarding checklist, provides answers to common questions via WhatsApp, routes required approvals to the People team, and logs what has been completed — giving HR visibility without manual status tracking.
When to use this
New hire onboarding is inconsistent — some people get all the information, others miss steps.
HR teams spend time answering the same onboarding questions repeatedly.
Onboarding completion is tracked in spreadsheets rather than in a system.
Managers don't know where new hires are in the onboarding process without asking HR.
System components
CRM Person record: employee type, start_date, onboarding_status, manager_owner, HR_owner.
Studio Table: onboarding checklist with tasks, owners, deadlines, and completion status.
Knowledge Base: approved answers for onboarding FAQ (benefits, IT setup, policies, first-week schedule).
AI onboarding assistant: answers questions using the approved knowledge base, routes anything outside scope.
Studio workflow: triggered on start_date, with milestone checkpoints at Day 1, Day 7, Day 30.
Max Activity: onboarding tasks created, questions asked and answered, completion status, escalations.
Step-by-step implementation
Agent prompt
You are an internal employee onboarding assistant. Answer onboarding questions using only the approved knowledge base provided.
You can answer questions about: IT setup and access, benefits enrollment deadlines and process, expense policy, office location and hours, and first-week schedule.
For questions outside this scope (compensation details, performance review process, team-specific questions): say 'Great question — I'll connect you with the right person' and route to HR.
Be warm and supportive. This is someone's first week. Keep answers clear and actionable.
Output JSON: { action: 'reply' | 'escalate', reply_text: string | null, escalation_topic: string | null }.
Workflow logic
Day 1: create all tasks, assign to owners, send welcome message to employee, write Max Activity.
Day 3: check IT setup and benefits enrollment tasks. If incomplete: send reminder to assigned owner. Write Max Activity.
Day 7: policy acknowledgment due. If not completed: escalate to HR owner. Send employee check-in message. Write Max Activity.
Day 30: 30-day check-in. Send employee a brief satisfaction question. Route reply to manager. Write Max Activity.
Employee asks question (any day): route to onboarding AI assistant. If answerable → reply. If not → route to HR owner with the question logged in Max Activity.
Final operating state
Every new hire's onboarding checklist is created automatically on their start date with tasks assigned to the correct owners.
Common onboarding questions are answered instantly via WhatsApp using approved resources — without HR needing to respond manually.
Managers and HR can see onboarding task completion status in CRM without asking the employee.
Max Activity shows the full onboarding journey: tasks created and completed, questions asked, and any escalations.
Troubleshooting
Workflow not triggering on start date: verify the trigger is a date-field trigger, not a record creation trigger. The start_date field must be set at least one day before the target date.
AI answering questions outside its scope: add explicit 'do not answer' categories to the agent prompt. List topics like compensation, visa, and performance as out-of-scope.
Tasks not being assigned to correct owners: verify that the Table rows have the correct owner field values that match the Person or user IDs in CRM.
Employee not receiving WhatsApp messages: confirm the Person record has a valid phone number and WhatsApp consent is marked as true.
Operational playbook
Use Employee onboarding workflow as part of the Frontline Solutions HR operating loop: inspect the current product state, confirm the source context, and decide what should happen next.
The goal is not to memorize screens. The goal is to understand how the product surface supports repeatable work, AI assistance, and accountable handoff.
Best practices
Start with the operational job before changing configuration. Name the owner, define the trigger or source context, and decide how the result should be reviewed.
Prefer narrow, inspectable setups over broad automation. Teammates should be able to explain why the system took an action from the visible product state.
Platform layers involved
Studio defines the workflow and AI agent behavior. Channels capture the customer interaction. CRM provides customer memory. Max Activity shows what the system did and what needs follow-up.
Use the solution page as the business-facing map, then open the related product tutorials when you need configuration detail.
Outcome metrics
Track a small set of operational signals: response time, handoff rate, completion rate, escalation quality, CRM field completeness, reply rate, and repeated failure patterns.
The metric should reflect the business outcome, not only whether the automation ran.
Agent Builder visual map
FAQs
What does Employee onboarding workflow teach?
Coordinate employee onboarding with tasks, calendar milestones, policy resources, internal assistant answers, and visible activity.
How should teams use this lesson?
Use it as an implementation guide: create the assets, connect the systems, verify the completed state, and operate the blueprint with review gates.
Which Frontline products are involved in this solution?
Most solution playbooks connect Studio workflows, Channels, CRM records, AI agents, and Max Activity. The business outcome is the entry point; the platform layers make it operational.
How should we decide whether to automate this use case?
Automate when the path is repeated, has clear source context, needs consistent follow-up, or benefits from AI classification, routing, summaries, or structured capture. Keep human review where judgment or risk is high.
What should be visible before this goes live?
Verify the workflow trigger, CRM context, channel permissions, AI agent instructions, handoff owner, logs, and Max Activity output so the team can trace what happened.
How do we keep the customer experience personal?
Use CRM context, conversation history, and approved message patterns. AI should use relevant customer memory, not generic copy, and workflows should escalate when context is missing.
What is the best first version of this playbook?
Start with one channel, one workflow, one owner group, and a narrow success metric. Expand only after logs, activity, and customer-facing outputs are trustworthy.