Professional tier · Customer Success
ELRA-01
AI Onboarding Coordinator
“I run the onboarding flow your CS team designed, so their hours go to the kickoff calls and the strategic accounts — not to chasing scheduling and tracking milestones.”
Scope the role first. Deploy only after approval.
At a glance
- Tier
- Professional · $500/month
- Reports to
- Your CS lead, in Slack
- Primary work
- Onboarding scheduling, milestone tracking, slip-risk surfacing
- Coverage
- Sub-enterprise onboarding (threshold configurable)
- Will not do
- Modify the playbook, handle enterprise accounts, improvise SLA commitments
- Success criterion
- On-time onboarding completion lift the CS lead defines
- Deployment
- Slack-native; live the same day. First weekly digest at end of week one.
About this role
ELRA runs the new-customer onboarding flow — kickoff scheduling, milestone tracking, gap surfacing — under your CS lead's onboarding playbook, so your CSMs walk into kickoffs already prepared.
Onboarding slip is the leading indicator of churn at month four. ELRA keeps every customer on the playbook so the CSM's time goes to the conversations that matter.
Areas of focus
- Runs the kickoff scheduling sequence end-to-end (calendar coordination, prep doc, attendee confirmation)
- Tracks every customer against the playbook milestones; flags slip risk before it becomes a CSM problem
- Drafts and sends the standard milestone-check messages (under CSM review for the first 60 days)
- Maintains a running per-account onboarding log in Slack — every signal, every action, every milestone status
- Surfaces patterns across accounts (e.g., 'three customers stalled at the integration step this cohort') for CS-lead review
“ELRA names the milestone the customer is closest to slipping on, the early signal that triggered the flag, and the standard playbook step the CSM should run — every Monday morning, before the team's standup.”
“Three of your customers are about to slip the integration milestone — ELRA flagged them on Monday morning, with the playbook step the CSM should run already drafted.”
My stack
My stack
Tools I use
Background
Background
- Where I come from
- Customer-onboarding work is the place where small CS teams quietly slip the most: kickoff scheduling drags, milestone tracking falls behind, and the early-warning signals that predict churn at month four go unnoticed. ELRA was formed from CS operations practice — the cognitive structure of playbook-driven onboarding and slip-detection — to run the flow your team designed without taking time from the conversations that move retention.
- How I think about the work
- Runs the playbook your CS lead wrote, never invents steps
- Maintains a per-account onboarding log with every signal, every milestone, every action
- Operates against a four-tier constitution: autonomous on scheduling and milestone-check messages, review-required on customer-facing escalations, escalate on enterprise-threshold accounts, refuse on contract-commitment questions
- Surfaces cross-account slip patterns weekly so the CS lead can refine the playbook
- How I've been tested
- Every release runs through an EvalOps suite covering milestone-tracking accuracy against held-out customer journeys, slip-detection precision (false-positive and false-negative bounds), and customer-facing message tone fidelity to your brand. The agent fails its suite, it doesn't ship.
- Where I'm running today
- Pre-launch as of May 2026. First cohort onboarding May 2026. Operating-record metrics (on-time completion rate lift, slip-detection precision, CSM hours recovered) publish with the next quarterly cohort review.
What I won't take on
ELRA will not modify the onboarding playbook itself. She runs it; the CS lead writes it.
ELRA will not handle accounts above your enterprise threshold. Those route to the senior CSM directly.
ELRA will not send escalation messages to executives without a CSM review.
ELRA will not improvise SLA or contract commitments. If a customer asks, ELRA escalates.
At the floor, not the average
ELRA escalates ambiguity rather than guessing. When a customer's signal conflicts with the playbook, she names the conflict and the question — and pings the CSM.
The first 30 days
Day 1
Provisioned to your CS Slack. Reads the last 90 days of onboarding flows, customer messages, and your CS lead's onboarding playbook. First clarifying questions to the CS lead.
Week 1
First weekly onboarding-status digest ships under CS-lead review. Milestone tracking calibrated. Slip-detection thresholds tuned.
Month 1
Onboarding flow runs end-to-end. CSM team reports 5+ hours/week of recovered kickoff-and-strategic-account time. 90-day success metric (onboarding-completion rate, time-to-value) gets first reading.
What success looks like at 30 days
On-time onboarding completion lift at the level your CS lead defines, within 90 days.
What I'll need from you
What I'll need from you
Read access to Slack (CS, onboarding, sales channels). Read/write access to HubSpot or your CRM for customer-account data. Calendar access via Calendly or equivalent for kickoff scheduling. Read/write access to Notion or your CS playbook home. Optional: read access to your product analytics for activation signals.
Engagement
Professional tiera small fraction of a junior onboarding coordinator salary
A junior onboarding coordinator costs $65–95K/year fully loaded (Levels.fyi 2025). ELRA runs the playbook your CS lead wrote at $6K/year — the senior CSMs work the renewals.
ELRA-01 costs a small fraction of what a mid-market junior onboarding coordinator costs. We don’t price ELRA-01 against a salary; we price it against the part of a junior onboarding coordinator role that scales — drafts, briefs, monitors, summaries, the work that should already exist by the time your team arrives Monday morning. A full-time mid-market junior onboarding coordinator in NYC costs roughly $8–12K/month fully loaded, and that money buys things ELRA-01 can’t replace: judgment in unfamiliar territory, accountability your customers can shake hands with, taste built from ten years of doing the work. ELRA-01 does the part that scales. Spend the rest on the part that doesn’t. See the math on /pricing.
Terms
- Cancel any month with 30 days' notice
- Every flag includes the early signal that fired and the playbook step that should run; no black-box escalations
- Your CS lead writes the playbook; ELRA does not invent steps
- 60-day CSM-review window on every customer-facing message before ELRA ships autonomously
- EvalOps suite gates every release; if it fails, ELRA doesn't ship
What you actually get
How it lands
Every Fidelic agent ships with a published operating plan. You know what it will do before you pay.
- First forty-five minutes
- TESS-01, the AI Hiring Manager, runs a voice intake. A three-name shortlist of role-and-configuration pairs lands in your inbox. You pick one. Slack OAuth. The agent appears in your Slack.
- Day 1
- The agent reads approved context — Slack channels, docs, customer notes, prior decisions. First clarifying questions land in your DMs; no pretending to know what it doesn’t.
- Week 1
- The first useful deliverable ships under review: a brief, a draft, a routing recommendation, a triage report, a scorecard. You sign off; the configuration agent calibrates.
- Month 1
- The role is operational. Escalation patterns are calibrated. The 90-day success metric (one number, published in the role brief) has its first reading.
Security model
How a Fidelic agent runs
- Each customer deployment runs in an isolated Anthropic project.
- Agents operate through approved Slack channels and approved context only.
- Fidelic logs operational metadata, not message or file contents.
- Every agent ships with written limits, escalation rules, and review-required actions.
The line we don’t cross
What humans still own
Fidelic agents do not replace human judgment in unfamiliar, political, relational, or high-stakes situations. The agent handles the repeatable work around those decisions so the human can move faster.
- Final approval on strategic accounts.
- Budget, refunds, policy, legal, and hiring decisions.
- Customer relationships and any sensitive escalation.
- Any action above the agent’s written authority.
Pairs well with