Ruby / Maya
Front desk and reception lanes
Use the standard lanes when the buyer needs first-contact, intake, or support-routing clarity.
Custom setup
Custom Built Employee Setup
Use Custom when the standard roster is close, but the workflow needs deeper scoping, owner-specific routing, or a timeline that does not fit a standard lane. The page explains the path, not a gate.
Managed setup comes first. Company + budget is enough to start the conversation, and CoreStaff routes the request toward the right package, scope, and pricing posture.
Custom setup is for bespoke workflows, not for deciding whether a company deserves service.
Custom vs standard
Compare the roster lanes before you choose the custom route.
This section makes the template-backed page feel more like a product detail page. It helps the buyer understand when the standard lanes are enough and when custom scoping is the right move.
Miles / Nora
Follow-up and support triage lanes
Use the standard lanes when the buyer wants structured follow-up drafts, handoffs, or support notes.
Custom
Bespoke workflow lane
Use Custom when the buyer needs a workflow that extends beyond the standard roster and needs explicit scoping.
When Custom fits
Choose Custom when the request is more specific than the starter lanes.
Ruby, Maya, Miles, and Nora cover the common first-launch lanes. Custom is the route for a workflow that needs a bespoke scope, a custom review boundary, or a plan that should be shaped around the business instead of a fixed roster lane.
Standard roster
Use Ruby, Maya, Miles, or Nora when the job fits a known lane.
- Front desk, intake, follow-up, or support triage.
- Simple routing with a clear approval boundary.
- Fast setup with a clear public preview path.
Custom path
Use Custom when the workflow needs more than one standard lane.
- Multi-step handoff or deeper scoping.
- Owner-specific logic or a special review sequence.
- A budget band, timeline, and package that need tailoring.
Buyer fit
Company + budget is a valid buyer.
- The page routes the conversation toward the right package.
- It does not act like a public qualification quiz.
- The goal is routing, scoping, and next-step clarity.
What happens next
The setup path stays human-reviewed and easy to scan.
1
Describe the workflow
Share the business outcome, the kind of work the custom lane should handle, and where the manual review boundary should stay.
2
Match the package and scope
CoreStaff routes the request toward the right plan, timeline, and pricing posture so the buyer can see the setup path clearly.
3
Review setup, preview pricing, and support
The buyer can inspect the public pages that show where the custom lane, plan, and support controls will be discussed before anything live exists.
4
Confirm the manual boundary
No live action happens on this page. Any future expansion stays owner-approved and future-only until a later phase changes that truth.
Public routes
Custom setup connects directly into the public pages buyers use now.
These are static public routes, not live portals. They help the buyer see how setup, preview pricing, policy, and support fit together.
Setup intake
Assigned role, request, and scope visibility
See where the custom lane is described once the setup is scoped.
Support and privacy
Plan, security, privacy, and support boundaries
Show the public help and policy controls that sit around the custom workflow.
Pricing and policy
Credits, plan visibility, and refund boundaries
Explain the pricing posture without claiming live checkout or token metering.
Preparation
Bring enough detail to route the custom request without making it a quiz.
Scope
What you want the custom lane to do
Describe the business result and the workflow shape. If the standard roster is close but not enough, say where it falls short.
Examples
The first few tasks you want reviewed
Share safe examples of the work without including secrets or production customer data. The request should be understandable in preview form.
Budget and timing
Budget band and desired timeline
Company + budget is enough to start the conversation. The page routes the request toward the right package and timeline instead of gating the buyer.
Fallback
What should remain human-reviewed
Confirm the work that must stay owner-reviewed until a later phase explicitly changes that boundary.
Related paths
Use the setup route that best matches the buyer's next question.
Route to setup intake
Use this when the buyer is ready to describe the workflow and get routed toward the right AI employee package.
Need to compare first?
Use the roster and pricing pages when the buyer wants to compare standard lanes before choosing Custom.
Boundary
Managed setup comes first while customer access is opened in stages.
This page explains the custom setup path and the manual review boundary. It does not claim live signup, live billing, live connectors, live OAuth, live portal behavior, or live setup completion.
Clear boundary, clear route
Use the page to explain the custom request, the package shape, the preview surfaces, and the support route. If something needs future expansion, it stays future-only until a later approved phase says otherwise.