Current product scope: Features that require third-party services remain unavailable until an authorized administrator connects and configures those services.
Technical home
Documentation, service information, integration guidance, security disclosures, and operating boundaries now live together on StaffRooster.com.
Implementation guidance
- Use this page for onboarding, Roosters, workflows, approvals, payments, and operations.
- Open Rooster guides for role-specific setup and test requirements.
- Use the FAQ for short answers and the status page for service posture.
- StaffRooster.net has been retired and its content consolidated here.
Security and compliance
- Review security safeguards and customer responsibilities.
- Read AI transparency for model use and human-accountability boundaries.
- Use the compliance center for privacy, terms, data processing, and subprocessors.
- Report concerns through the published customer-support channel.
Get started
Move from a new workspace to an approved deployment without skipping the human controls.
Eight-step onboarding
- Complete the company profile and workflow objective.
- Add approved knowledge sources and integrations.
- Define guardrails, tests, and escalation owners.
- Submit for human review before deployment.
How StaffRooster works
- Agents own narrow roles.
- Playbooks coordinate complete workflows.
- Policies define what can happen automatically.
- Approvals preserve human accountability.
Agents and workflows
Configure a specialist around a measurable business outcome, not an open-ended prompt.
Try a Rooster demo
- Open any available Rooster profile.
- View the no-token guided example or enter fictional context.
- Live trials allow three short turns and no integrations.
- Use the consultation path to configure a production workflow.
Rooster workbench
- Choose the agent and operating mode.
- Write workspace-specific instructions.
- Set confidence, volume, and escalation limits.
- Save changes before running validation.
Test before launch
- Use realistic inputs and edge cases.
- Review draft output and confidence.
- Approve at least one current test.
- Retest whenever guardrails change.
Multi-Rooster handoffs
- Define the initiating event.
- Assign each step to one role.
- Specify the shared context and completion condition.
- Insert approvals at consequential actions.
Exception handling
- Failed work enters operator review.
- Repeated signals become incidents.
- Operators acknowledge and resolve incidents.
- Emergency pause stops workspace execution.
Embeddable Concierge
Deploy a branded website conversation layer with approved knowledge, durable history, and a deliberate path to a person.
Confirmed preview model
- $499 per month includes one authorized website and 1,000 AI responses.
- Additional AI responses are $0.15 each; additional websites are $199 per month.
- Standard $2,500 guided onboarding applies.
- The preview and waitlist do not collect payment or create a subscription.
Brand and behavior
- Choose the logo, color, launcher position, greeting, and suggested prompts.
- Define voice, supported topics, collection fields, business hours, and handoff language.
- Preview every device size before publishing.
- Version changes so customers and reviewers can see what changed.
Conversation continuity
- Public previews keep short history only on the visitor’s device.
- Production history is scoped to the customer workspace and conversation identity.
- Set retention, export, and deletion rules before deployment.
- Summarize or compact long conversations to control context cost.
Multi-domain website deployment
- StaffRooster generates a signed embed only after configuration and human approval.
- Assign the same approved configuration to one or more exact domains.
- Origin validation prevents the widget from running on unapproved sites.
- Each additional website is $199/month; emergency pause disables new responses everywhere.
Collapse and reopen
- Concierge loads as a compact branded launcher by default.
- Visitors may expand or minimize it without losing the current conversation.
- Choose bottom-left or bottom-right placement for each approved configuration.
- Keyboard labels and touch-sized controls remain available across screen sizes.
Human escalation
- Define topics and confidence thresholds that require a person.
- Send the conversation summary and source messages to the approved queue.
- Tell the visitor what will happen and when to expect a response.
- Never claim a handoff, booking, or message was completed unless the connected system confirms it.
Governance and access
Permissions and approval boundaries are enforced on the server, not only hidden in the interface.
Workspace permissions
- Owner: workspace and access control.
- Admin: configuration and operations.
- Reviewer: human decisions.
- Billing: subscriptions and payments.
- Operator: permitted daily workflows.
Human decision points
- High-impact tasks remain queued.
- Reviewers see inputs, drafts, risk, and confidence.
- Every decision records reviewer and time.
- Changed policies invalidate stale validation.
Data controls
- Workspace-scoped storage.
- Governed export and deletion requests.
- Human review before destructive completion.
- Published privacy and processing terms.
Operational evidence
- Agent runs and decisions are retained.
- Outbound delivery is idempotent.
- Administrative changes enter the audit trail.
- Launch readiness is recalculated continuously.
Integrations
Every external system requires explicit authorization and has a visible readiness state.
Gmail delivery
- Connect an authorized sender.
- Approved drafts stage before delivery.
- Delivery attempts use idempotency keys.
- Internal lead-generation notes are excluded from customer email.
Lead sources
- Create a revocable source credential.
- Send a unique external inquiry ID.
- Rate limits and duplicate protection apply.
- New leads pause for human review.
Billing and Connect
- StaffRooster subscriptions use Stripe Billing.
- Client payments use direct Connect charges.
- The client business remains merchant of record.
- Payment fees and caps are disclosed before Checkout.
Credential safety
- Secrets stay in encrypted runtime configuration.
- The dashboard displays readiness, never values.
- Use restricted keys and a separate sandbox.
- Rotate revoked or exposed credentials immediately.
Payments and reconciliation
StaffRooster separates its SaaS billing from the payments each customer business accepts.
Connected business setup
- Stripe-hosted onboarding collects verification details.
- Charges remain disabled until Stripe approves the account.
- Businesses receive their own Stripe Dashboard.
- Stripe manages payouts and processing fees.
Transparent economics
- Starter: 0.50%, capped at $10.
- Growth: 0.25%, capped at $7.50.
- Scale: no StaffRooster transaction fee.
- Stripe processing fees remain separate.
Payment status
- Created links enter the payment ledger.
- Signed webhooks mark paid or expired sessions.
- Refunds and disputes remain visible.
- Amounts and StaffRooster fees stay reconcilable.
Responsibilities
- The business sets prices and delivers service.
- Stripe processes and pays out funds.
- StaffRooster coordinates workflows and applies its disclosed fee.
- The customer pays through secure Stripe Checkout.
Launch and operations
Use the launch gate and operator center to keep every deployment supportable.
Go-live checklist
- Onboarding is submitted and approved.
- Active Roosters have current policies and tests.
- Required integrations are configured.
- No critical incident or emergency pause is active.
Daily operations
- Review Rooster health and failure rates.
- Clear outstanding approvals.
- Resolve delivery and intake incidents.
- Watch usage, cost, and subscription status.
Release rehearsal
- Use a separate test customer identity.
- Complete Checkout, onboarding, one approved Rooster task, and delivery.
- Confirm invoices, notifications, cancellation, and access changes.
- Record defects before inviting a customer.
Revenue recovery
- Stripe webhooks are the subscription source of truth.
- Failed payments pause new paid work and notify the workspace.
- Customer Portal handles payment methods, invoices, and cancellation.
- Operators reconcile failed events before restoring access.
Response runbook
- Acknowledge the incident and identify affected workspaces.
- Pause execution when data, delivery, or authorization could be unsafe.
- Preserve audit evidence and communicate only verified facts.
- Resolve, document cause, and validate recovery before resuming.
Staged rollout
- Start with internal rehearsal.
- Invite three to five design partners.
- Keep every external action approval-required.
- Expand only after reliability and support targets are met.