Client Onboarding Agent
Deploy an AI-powered onboarding orchestrator that automates the entire client intake workflow — from welcome emails and workspace creation to kickoff scheduling, checklist tracking, deadline monitoring, and escalation management. Reduce time-to-value by 60%, eliminate dropped tasks, and deliver a consistently professional first impression across every engagement.
Connected Apps & Services
Gmail
Notion
Asana
Google Calendar
Client onboarding is one of the most consequential phases in any service business. Research consistently shows that 60-70% of client churn traces back to a poor onboarding experience, with disorganized kickoffs, missed follow-ups, and unclear expectations topping the list of complaints. Agencies, consultancies, and SaaS companies lose an estimated 25-40% of new clients within the first 90 days when onboarding is handled manually and inconsistently. The cost is staggering: replacing a churned client costs 5-7x more than retaining one through a solid first impression.
The Client Onboarding Agent transforms this critical workflow into a structured, automated, and trackable process. Built on OpenClaw's agent framework with connections to Gmail, Google Calendar, Slack, and Notion, it orchestrates every step from signed contract to productive engagement — creating project workspaces, sending personalized welcome emails, scheduling kickoff calls, managing checklists with deadlines, and sending progress reminders — all while keeping your team informed and your clients impressed.
Why Onboarding Fails Without Automation
Manual onboarding suffers from predictable failure modes that compound as your client base grows: Inconsistency across team members. When onboarding lives in someone's head or a static spreadsheet, every account manager does it differently. One remembers to send the welcome packet on day one; another forgets until day five. One creates the project folder structure immediately; another waits until the kickoff call. Clients receive wildly different experiences depending on who draws them. Dropped tasks and missed deadlines. A typical agency onboarding involves 15-25 discrete tasks across multiple tools and team members. Without automated tracking, tasks slip through the cracks — the NDA that never got sent, the brand assets that were requested but never followed up on, the kickoff call that was discussed but never scheduled. No visibility into progress. Leadership cannot answer basic questions: How many clients are currently onboarding? Which ones are stuck? What is our average time-to-value? Without structured data, onboarding quality is invisible until clients complain or churn. Context switching overhead. Account managers spend 30-35% of their onboarding time on administrative tasks — copying information between systems, sending routine emails, creating folders, updating spreadsheets. This is time stolen from relationship-building and strategic setup work that actually drives client success.
The Client Onboarding Agent addresses each of these failure modes by codifying your onboarding process into an executable, trackable workflow that runs consistently for every client.
Architecture: Multi-Step Workflow Orchestration
The onboarding agent operates as a stateful workflow orchestrator that manages the full lifecycle from contract signature to engagement completion. The architecture leverages OpenClaw's exec tools for file operations, hooks system for event-driven automation, and browser capabilities for web-based integrations.
Core Components
Workflow State Machine. The agent maintains a structured state for each onboarding engagement, tracking which phase the client is in (intake, setup, kickoff, activation, handoff), which tasks are complete, which are pending, and which are overdue. State persists across sessions using OpenClaw's workspace files, so the agent picks up exactly where it left off. Checklist Engine. A dynamic checklist system that adapts based on client type, service tier, and engagement scope. Each checklist item has an owner (agent-automated or human-assigned), a deadline (relative to engagement start or previous task completion), and a status. The agent automatically advances items it can handle and prompts humans for items requiring judgment. Integration Layer. Connected apps handle specific automation domains:- Gmail dispatches personalized welcome emails, document requests, and progress updates using templates populated with client-specific data
- Google Calendar finds mutual availability and schedules kickoff calls, check-ins, and milestone reviews
- Slack posts real-time notifications to internal channels when onboarding events occur — new client started, task completed, deadline approaching, blocker identified
- Notion creates structured project workspaces from templates with client-specific pages, databases, and task boards
Event-Driven Automation with Hooks
OpenClaw's hooks system enables the agent to respond to events without polling. Key hook configurations:
on:messagehook processes inbound client communications, extracting action items and updating the onboarding checklist automaticallyon:boothook runs a daily digest check on startup, reviewing all active onboardings and flagging items that need attention- Session memory hooks preserve onboarding context across conversation resets, ensuring no client context is lost
Execution Model
The agent uses OpenClaw's exec tools to perform file system operations (creating folder structures, generating documents from templates, writing configuration files) and shell commands (API calls to connected services, data transformations, report generation). Browser automation handles any web-based steps that lack API access — filling forms in client portals, capturing screenshots of completed setups, or verifying that provisioned accounts are accessible.
Step-by-Step Setup
Prerequisites
- An active OpenClaw instance (self-hosted or via Donely)
- Gmail, Google Calendar, Slack, and Notion integrations connected via OAuth
- Admin access to configure agent skills and hooks
1. Create the Agent Workspace
mkdir -p /data/.openclaw/skills/client-onboarding
Create the agent's skill directory where templates, checklists, and configuration will live.
2. Configure the BOOTSTRAP.md
Create /data/.openclaw/skills/client-onboarding/BOOTSTRAP.md with the following content:
---
name: client-onboarding
description: Automated client onboarding workflow orchestrator
triggers:
- "onboard new client"
- "start onboarding"
- "new client setup"
# Client Onboarding Agent
You are a client onboarding specialist. When a new client engagement begins,
you orchestrate the complete onboarding workflow.
Core Responsibilities
- Intake & Validation
- Collect client company name, primary contact, email, engagement type, and start date
- Validate all required fields before proceeding
- Create the onboarding record in the tracking system
- Workspace Setup
- Create Notion project workspace from the appropriate template
- Set up folder structure: /clients/{company}/contracts, assets, deliverables, communications
- Generate and populate the onboarding checklist based on engagement type
- Welcome Communication
- Send personalized welcome email via Gmail with:
- Introduction to the team and key contacts
- Overview of what to expect in the first 30 days
- Links to the client portal and project workspace
- Document/asset request list with deadlines
- Post internal Slack notification: new client onboarding started
- Kickoff Scheduling
- Check Google Calendar availability for account team
- Propose 3 time slots to the client within the first 5 business days
- Send calendar invite once confirmed with agenda and prep materials
- Checklist Management
- Track all onboarding tasks with owners and deadlines
- Auto-complete tasks you can verify (workspace created, email sent, etc.)
- Send reminders 24 hours before deadlines
- Escalate overdue items after 48 hours
- Progress Reporting
- Post daily summary to Slack #onboarding channel for active engagements
- Generate weekly onboarding status report
- Flag at-risk engagements (>2 overdue items or no client response in 3+ days)
Checklist Templates
Standard Agency Onboarding (15 business days)
- [ ] Day 0: Welcome email sent
- [ ] Day 0: Notion workspace created
- [ ] Day 0: Internal Slack announcement
- [ ] Day 1: Document request sent (NDA, brand guidelines, access credentials)
- [ ] Day 1-3: Kickoff call scheduled
- [ ] Day 3: Client documents received and filed
- [ ] Day 5: Kickoff call completed
- [ ] Day 5: Kickoff notes and action items distributed
- [ ] Day 5-7: Strategy/scope document drafted
- [ ] Day 7: Client review of strategy document
- [ ] Day 10: Strategy approved, work begins
- [ ] Day 10: Project milestones set in Notion
- [ ] Day 12: First deliverable check-in
- [ ] Day 15: Onboarding complete, transition to ongoing management
SaaS Customer Activation (10 business days)
- [ ] Day 0: Account provisioned and welcome email sent
- [ ] Day 0: Notion customer workspace created
- [ ] Day 1: Product walkthrough scheduled
- [ ] Day 2: Walkthrough completed, recorded, and shared
- [ ] Day 3: Integration setup assistance
- [ ] Day 5: First value milestone check
- [ ] Day 7: Usage review and optimization suggestions
- [ ] Day 10: Activation confirmed, transition to success team
Consulting Engagement (20 business days)
- [ ] Day 0: Engagement letter confirmed, welcome email sent
- [ ] Day 0: Secure document workspace created
- [ ] Day 1: Data request list sent with deadlines
- [ ] Day 3: Kickoff workshop scheduled
- [ ] Day 5: Pre-workshop materials distributed
- [ ] Day 7: Kickoff workshop conducted
- [ ] Day 7: Workshop synthesis and preliminary findings shared
- [ ] Day 10: All requested data received and cataloged
- [ ] Day 12: Initial analysis complete
- [ ] Day 15: Draft recommendations prepared
- [ ] Day 17: Client review meeting
- [ ] Day 20: Onboarding phase complete, transition to execution
Escalation Rules
- Yellow flag: Any task >24 hours overdue → reminder to owner + account manager
- Red flag: Any task >48 hours overdue → escalate to team lead via Slack DM
- Critical: No client response for 3+ business days → account manager personal outreach required
- Blocker: 3+ red flags on single engagement → leadership notification with summary
3. Set Up Onboarding Templates
Create email templates, Notion workspace templates, and checklist configurations that the agent will use. Store these in the skill directory:
/data/.openclaw/skills/client-onboarding/
BOOTSTRAP.md
templates/
welcome-email-agency.md
welcome-email-saas.md
welcome-email-consulting.md
document-request.md
kickoff-agenda.md
checklists/
agency-standard.json
saas-activation.json
consulting-engagement.json
4. Configure Hooks for Automated Monitoring
Set up a daily digest hook that reviews all active onboardings:
{
"hooks": {
"entries": {
"onboarding-monitor": {
"enabled": true,
"events": ["gateway:ready"],
"config": {
"checkInterval": "daily",
"slackChannel": "#onboarding",
"escalationChannel": "#onboarding-alerts"
}
}
}
}
}
5. Connect Integrations
Ensure all four connected apps are authenticated:
- Gmail: OAuth connection with send permissions for your onboarding email address
- Google Calendar: Read/write access to the account team's calendars
- Slack: Bot token with permissions for posting to channels and sending DMs
- Notion: Integration token with access to the workspace where client projects live
6. Test with a Dry Run
Start a test onboarding to verify the full workflow:
> Onboard new client: Test Company, contact: Jane Doe, email: jane@test.com, type: agency-standard, start: today
The agent should execute the complete workflow: create workspace, send welcome email, schedule kickoff, initialize checklist, and post Slack notification.
Capabilities in Detail
Folder Creation and Workspace Setup
The agent creates consistent project structures across Notion and any file storage systems. Each new engagement gets a standardized workspace with sections for contracts, brand assets, deliverables, meeting notes, and communications. The structure adapts based on engagement type — a SaaS onboarding workspace emphasizes integration documentation and usage tracking, while an agency workspace focuses on creative briefs and approval workflows.Welcome Email Automation
Personalized welcome emails are generated from templates populated with client-specific data — contact name, company, engagement type, team assignments, and relevant links. The agent uses Gmail integration to send these from a real team email address (not a no-reply), making the communication feel personal while being entirely automated. Follow-up document requests are sent as separate emails with clear deadlines and itemized lists.Kickoff Call Scheduling
The agent queries Google Calendar to find available slots across all required team members, then proposes options to the client. Once confirmed, it creates a calendar event with a pre-populated agenda, video conference link, and any prep materials attached. Post-kickoff, it can extract action items from meeting notes and add them to the onboarding checklist.Checklist Tracking and Progress Management
Every onboarding engagement is tracked against a deadline-aware checklist. The agent distinguishes between automated tasks (which it verifies and marks complete) and human tasks (which it monitors and reminds). Progress is visible through Slack updates and Notion dashboards, giving leadership real-time visibility into onboarding health across all active engagements.Deadline Monitoring and Escalation
The background monitoring system evaluates all active checklists against their deadline schedules. The escalation ladder is configurable but defaults to: gentle reminder at -24 hours, direct reminder at deadline, escalation at +48 hours, leadership alert at +72 hours or when multiple items are overdue simultaneously.Configuration
openclaw.json Settings
{
"skills": {
"load": {
"extraDirs": ["/data/.openclaw/skills"]
}
},
"hooks": {
"entries": {
"onboarding-monitor": {
"enabled": true
}
}
}
}
Environment Variables
| Variable | Description |
|---|---|
ONBOARDING_GMAIL_FROM | Email address for outbound onboarding emails |
ONBOARDING_SLACK_CHANNEL | Default Slack channel for onboarding notifications |
ONBOARDING_NOTION_TEMPLATE_DB | Notion database ID for workspace templates |
ONBOARDING_ESCALATION_HOURS | Hours before overdue escalation (default: 48) |
ONBOARDING_REMINDER_HOURS | Hours before deadline for reminder (default: 24) |
Checklist Configuration Schema
{
"name": "agency-standard",
"duration_days": 15,
"tasks": [
{
"id": "welcome-email",
"title": "Send welcome email",
"owner": "agent",
"day": 0,
"automated": true,
"depends_on": null
},
{
"id": "workspace-setup",
"title": "Create Notion workspace",
"owner": "agent",
"day": 0,
"automated": true,
"depends_on": null
},
{
"id": "kickoff-scheduled",
"title": "Schedule kickoff call",
"owner": "agent",
"day": 1,
"automated": true,
"depends_on": ["welcome-email"]
},
{
"id": "docs-received",
"title": "Client documents received",
"owner": "client",
"day": 3,
"automated": false,
"depends_on": ["welcome-email"]
}
]
}
Real-World Examples
Example 1: Digital Marketing Agency Client Onboarding
Scenario: BrightEdge Marketing signs a new retainer client, Coastal Realty, for SEO and content marketing services. Trigger: Account manager tells the agent: "Onboard new client: Coastal Realty, contact: Sarah Chen, sarah@coastalrealty.com, type: agency-standard, services: SEO + Content Marketing" What the agent does:- Minute 0: Creates a Notion workspace "Coastal Realty" with sections for SEO Audit, Content Calendar, Brand Guidelines, Monthly Reports, and Meeting Notes. Posts to #new-clients in Slack: "New client onboarding started: Coastal Realty (SEO + Content) — Account Manager: @jessica"
- Minute 1: Sends a welcome email to Sarah Chen from jessica@brightedge.com introducing the team, outlining the first 30 days, and requesting brand guidelines, website access credentials, Google Analytics/Search Console access, and competitor list — all due within 3 business days.
- Minute 5: Checks Jessica's, the SEO lead's, and the content strategist's calendars. Finds three mutual openings in the next 5 business days. Sends Sarah a scheduling email with the three options.
- Day 2: Sarah confirms the Tuesday 2pm slot. Agent creates the calendar event with a kickoff agenda covering goals review, current SEO baseline, content strategy discussion, and timeline alignment. Attaches a pre-kickoff questionnaire.
- Day 3, 9am: Sarah hasn't sent the brand guidelines yet. Agent sends a friendly reminder: "Hi Sarah, just a quick reminder that we're looking forward to receiving your brand guidelines and access credentials before our kickoff on Tuesday. This will help us make the most of our time together."
- Day 5: Kickoff call completed. Agent extracts action items from the meeting notes the account manager pastes in: complete SEO audit (due day 10), draft content calendar (due day 12), set up reporting dashboard (due day 8). Each is added to the checklist with owners and deadlines.
- Day 15: All checklist items complete. Agent posts a summary to Slack, marks the onboarding as complete, and transitions Coastal Realty to the ongoing management workflow.
Example 2: SaaS Customer Activation
Scenario: DataPipe, a data integration platform, signs up a new enterprise customer, LogiTech Solutions, on their Professional plan. Trigger: CRM webhook fires when the deal closes, or the CS manager says: "Onboard new customer: LogiTech Solutions, contact: Marcus Webb, marcus@logitech-solutions.com, type: saas-activation, plan: professional" What the agent does:- Minute 0: Sends a welcome email with account credentials, quickstart guide link, and a link to schedule a product walkthrough. Creates a Notion customer page with company profile, plan details, integration requirements, and success milestones. Slack notification to #customer-success: "New Professional customer: LogiTech Solutions — CSM: @david"
- Day 1: Marcus books the walkthrough for tomorrow at 10am. Agent confirms with a calendar invite, attaches the pre-walkthrough checklist (what data sources to have ready, admin access to target systems), and sends David a prep briefing with LogiTech's company profile and likely use cases based on their industry.
- Day 2: Walkthrough completed. Agent creates a follow-up email summarizing the three integrations Marcus wants to set up (Salesforce, PostgreSQL, Snowflake) with links to the relevant documentation for each.
- Day 3-4: Agent monitors LogiTech's account for integration activity. Detects that Salesforce integration was connected but PostgreSQL setup hasn't started. Sends Marcus a helpful nudge with the PostgreSQL setup guide and offers to schedule a technical support session.
- Day 5: First value milestone check. Agent queries the platform API and finds LogiTech has successfully synced 50,000 records across two integrations. Posts to Slack: "LogiTech Solutions hit first value milestone: 50K records synced. PostgreSQL integration still pending." Sends Marcus a congratulatory email with tips for optimizing their pipeline.
- Day 7: Usage review. Agent generates a usage report showing active integrations, data volume, error rates, and feature adoption. Identifies that LogiTech hasn't used the scheduling feature. Includes a recommendation in David's weekly digest.
- Day 10: All three integrations active, usage patterns healthy. Agent marks activation complete, sends Marcus a "You're all set" email with links to advanced features, community forum, and support channels. Transitions to the ongoing success workflow with monthly check-in scheduling.
Example 3: Management Consulting Engagement Setup
Scenario: Meridian Consulting wins a digital transformation assessment engagement with Hartwell Manufacturing. Trigger: Engagement partner says: "Onboard new engagement: Hartwell Manufacturing, sponsor: VP Operations Robert Hartwell, robert@hartwellmfg.com, type: consulting-engagement, scope: digital transformation assessment, duration: 8 weeks" What the agent does:- Minute 0: Creates a secure Notion workspace with sections for Engagement Letter, Data Room, Interview Schedule, Analysis Workstreams, Findings, and Recommendations. Sets up access controls limiting visibility to the engagement team. Sends a formal welcome email to Robert confirming the engagement start, introducing the project team, and attaching the data request list organized by department (Operations, IT, Finance, HR). Slack alert to #active-engagements.
- Day 1: Agent sends the detailed data request as a separate email with a structured table: 23 items across 4 departments, each with a description, format requested, and deadline (Day 7 for critical items, Day 10 for supplementary). Creates a tracking matrix in Notion that Robert's team can reference.
- Day 3: Agent proposes three dates for the kickoff workshop (full-day session). Sends a pre-read package to all participants with the engagement overview, transformation framework, and preparation questions for each department head.
- Day 5: Nine of 23 data items received. Agent updates the tracking matrix, sends a progress summary to Robert ("9 of 23 items received — great progress. Items still outstanding from IT and Finance departments, due in 2 days."), and alerts the engagement manager about potential gaps in IT infrastructure documentation.
- Day 7: Kickoff workshop conducted. Agent processes the engagement manager's workshop notes: extracts 15 key findings, 8 stakeholder concerns, and 12 follow-up data requests. Distributes a workshop synthesis document to all participants within 2 hours. Updates the project timeline in Notion with refined milestones based on workshop outcomes.
- Day 10: All critical data received, 3 supplementary items outstanding. Agent creates a consolidated data catalog in the Notion data room, organized by workstream. Flags two data quality issues (incomplete inventory records, conflicting headcount figures) for the engagement team to address with the client.
- Day 12-20: Weekly progress reports auto-generated. Agent tracks analysis deliverables against milestones, sends reminders for upcoming internal review deadlines, and maintains the Notion workspace as the single source of truth. When the preliminary findings document is due on Day 15, the agent reminds the lead analyst 3 days in advance, then sends the draft to the engagement partner for review.
Best Practices
Start with your most common engagement type. Do not try to build onboarding automation for every client type simultaneously. Pick your highest-volume engagement, document the exact workflow, convert it to a checklist, and automate that first. Expand to other types once the pattern is proven. Keep humans in the relationship loop. The agent handles logistics and administration; humans handle strategy, judgment, and relationship-building. The welcome email should come from a real person's address. The kickoff call should be led by a real person. The agent ensures these things happen on time — it does not replace the human connection. Set realistic deadlines with buffer. If your team typically takes 3 days to prepare the strategy document, set the checklist deadline at 4 days. Automation highlights delays; overly aggressive deadlines create noise and erode trust in the system. Customize templates per client segment. A Fortune 500 enterprise client needs different welcome language, more formal document handling, and longer timelines than a startup. Build 2-3 template variants rather than one-size-fits-all. Review and iterate monthly. Track which checklist items are consistently late, which emails get the best response rates, and where clients get stuck. Use this data to refine your templates, adjust deadlines, and improve the workflow. The agent's structured data makes this analysis straightforward. Use the escalation ladder, do not skip it. The temptation is to alert leadership immediately when anything is overdue. Resist this. The graduated escalation (reminder, direct follow-up, manager alert, leadership alert) resolves most issues at the lowest level and avoids alarm fatigue. Protect client data. Onboarding involves sensitive information — contracts, credentials, financial data. Ensure your Notion workspace has appropriate access controls, email templates do not include sensitive data in subject lines, and the agent's workspace is properly secured.Troubleshooting
Agent does not send welcome email. Check that the Gmail integration is properly authenticated and theONBOARDING_GMAIL_FROM address is a valid alias on the connected account. Verify that the email template exists in the templates directory and does not contain syntax errors. Test with a simple email first to isolate whether the issue is template parsing or Gmail connectivity.
Calendar scheduling fails to find availability.
Ensure the Google Calendar integration has read access to all team members' calendars, not just the primary calendar. Check that the calendars are not set to "free/busy only" visibility which prevents the agent from reading event details to find open slots. Verify timezone settings match between the agent configuration and the team calendars.
Slack notifications not posting.
Confirm the Slack bot token has chat:write permission and has been invited to the target channel. The agent cannot post to channels it has not been added to. Check that ONBOARDING_SLACK_CHANNEL includes the # prefix. If using a private channel, the bot must be explicitly invited.
Checklist deadlines not triggering reminders.
The deadline monitoring runs on the hooks system. Verify the onboarding-monitor hook is enabled in your openclaw.json configuration. Check that the checkInterval is set correctly and the hook's events array includes gateway:ready for startup-based checks. Review the agent logs for any hook execution errors.
Notion workspace creation fails.
Verify the Notion integration token has "Insert content" permission on the parent page where workspaces are created. Check that the template database ID in ONBOARDING_NOTION_TEMPLATE_DB is correct and accessible. Notion API rate limits (3 requests/second) can cause failures during rapid workspace setup — the agent should implement retry logic.
Client receives duplicate communications.
This typically occurs when the agent is restarted mid-workflow and session state is not properly restored. Ensure the session-memory hook is enabled to preserve onboarding state across restarts. Each communication task should check its completion status before executing. If duplicates persist, verify that the checklist state file is being written to persistent storage, not ephemeral workspace memory.
Onboarding stuck in one phase.
Check the dependency chain in your checklist configuration. A task with depends_on referencing a task that can never be auto-completed (e.g., waiting for client action) will block downstream automated tasks. Ensure human-dependent tasks have reasonable timeout escalations so the workflow does not stall indefinitely. Use the agent's status command to see exactly which task is blocking progress.