First contact
Reception, intake, and the first response
Ruby and Maya are the lanes to compare when the company wants a front-door experience and a clear handoff path.
AI employees and services
Choose the service lane before choosing the workflow.
CoreStaff presents the roster as a managed product system: each AI employee lanes into setup, preview pricing, support, and request-access routes so buyers can see how the service works before any owner-approved next step.
Assigned AI employees are explained through setup and service pages.
Billing and credits remain policy-based and human-reviewed.
Setup routes buyers toward the right package, scope, and timeline.
Use-case map
Commercial buyers can see what each lane is for before they compare setup, preview pricing, and support paths.
This is the page that connects the employee roster to real buyer needs without pretending the live runtime already exists.
Lead follow-up
Summaries, next steps, and sales handoff
Miles turns lead context into drafts and notes while keeping the approval boundary human-reviewed.
Support triage
Support routing and customer success notes
Nora helps buyers see a support lane that keeps escalation organized and routes work to the right owner.
Service roster
Ruby, Maya, Miles, Nora, and Custom are managed AI employee lanes, not generic chatbot features. Ruby leads the roster as the front-office AI employee for first contact and workflow coordination.
Each card tells the buyer what the employee does, what they get, how setup works, where it appears in the public path, and where to go next.
R
- Role / use case: front-desk intake, visitor context, and next-step summaries.
- What the customer gets: a draft-first reception lane that reduces ambiguity.
- Setup implication: greeting style, FAQ summary, and escalation contact are scoped first.
- Public cue: appears as a managed front-door role in setup and role comparison pages, with Ruby positioned as the flagship front-office lane.
- Public route: review Ruby flagship or view setup path.
M
- Role / use case: inquiry sorting, first-response drafts, scheduling prep, and weekly recap notes.
- What the customer gets: a structured intake lane with clear handoff notes.
- Setup implication: website summary, safe greeting, and support escalation rules are defined first.
- Public cue: appears in setup, support, and privacy-facing guidance.
- Public route: view help center or support path.
M
- Role / use case: follow-up drafting, qualification notes, objection summaries, and meeting prep.
- What the customer gets: a follow-up lane that improves clarity without implying autonomous outreach.
- Setup implication: lead context, approval style, and handoff rules are captured before launch.
- Public cue: connected to pricing clarity, setup scoping, and manual review language.
- Public route: view pricing or contact CoreStaff.
N
- Role / use case: support routing, FAQ drafts, onboarding notes, and escalation summaries.
- What the customer gets: a support lane that clarifies the next step before anything live exists.
- Setup implication: support categories, reply style, and owner review rules are defined upfront.
- Public cue: linked to support tasks, privacy controls, and escalation guidance.
- Public route: support path or help center.
C
- Role / use case: deeper workflow scoping, multi-step handling, and owner-reviewed expansion paths.
- What the customer gets: a managed custom setup path rather than a generic marketplace claim.
- Setup implication: requirements, package scope, and approval boundaries are handled before expansion.
- Public cue: custom setup surfaces into request-access, preview pricing, and support guidance.
- Preview-safe route: view custom setup or contact CoreStaff.
Product system
Service lanes connect into setup, preview pricing, support, and request-access paths.
This page is intentionally product-led. It shows how the roster becomes a customer workflow instead of pretending the live runtime already exists.
Setup
Assigned AI employees and workflow scoping
The public setup path shows where the employee lane appears once setup is scoped.
Support
Help, privacy, and support controls
The help and support pages show the owner-facing controls that sit around the service lanes.
Pricing
Credits, preview pricing visibility, and refund boundaries
The pricing page keeps credit usage and cancellation language human-reviewed.
1. Choose the lane
Pick Ruby, Maya, Miles, Nora, or Custom based on the workflow you want to review publicly.
2. Scope the workflow
Define what the employee gets, what the business provides, and where the manual boundary stays.
3. Configure previews
Use setup, preview pricing, and support pages to see how the product system fits together.
4. Owner review boundary
Any live action remains future-only until a later phase explicitly changes that truth.
Boundary note
No live automation claim
These are managed AI employee product lanes and setup previews, not public claims of live autonomous runtime.
Support path
Need help choosing a lane?
Use support or contact when a buyer needs routing, scoping, or custom setup guidance.