Clear answers before you automate.

StaffRooster is a governed operations platform for deploying specialized AI Roosters. Each Rooster has a defined role, approved knowledge, explicit guardrails, and measurable outcomes.

No. Chat is only one possible interface. StaffRooster manages triggers, workflows, approvals, integrations, delivery, audit history, usage, and Rooster health.

The core roster covers lead qualification, scheduling, follow-up, support, invoice recovery, and operating reports. Additional specialists are published with waitlists before release.

Yes. Playbooks coordinate multiple roles, pass approved context between steps, and stop at defined human checkpoints.

StaffRooster is designed to remove repetitive coordination and drafting work while people retain judgment, relationships, exceptions, and accountability.

Only within the mode and thresholds configured by the business. Consequential or out-of-policy work is held for review.

The task is escalated with its context and recommendation rather than being executed silently.

Changing an agent policy invalidates prior validation. The agent must pass a new human-approved test before launch readiness is restored.

Yes. Authorized administrators can pause workspace execution. The action is recorded and must be deliberately reversed.

StaffRooster records relevant inputs, draft output, confidence, risk, reviewer decisions, delivery state, and timestamps where the workflow supports them.

A focused workflow can be configured quickly, but deployment depends on knowledge preparation, integration authorization, testing, and human approval.

The platform is designed for email, calendars, CRM, support, inbound forms, payments, and other approved business systems. Availability depends on configured integrations.

No. Credentials belong in encrypted runtime configuration or the provider’s authorization flow. StaffRooster surfaces connection status without exposing secret values.

Yes. Onboarding records the approved knowledge sources and instructions for each workflow. Sensitive or unverified material should not be added.

The task is marked failed, delivery is not assumed, and repeated failures can become operator incidents requiring acknowledgement and resolution.

Plans combine a monthly platform subscription with included capabilities. Optional agents, onboarding, usage, and enterprise services may be priced separately and are disclosed before purchase.

A customer business connects its own Stripe account and accepts direct charges. That business remains merchant of record and controls its prices, service, refunds, and disputes.

Starter is 0.50% capped at $10 per successful payment; Growth is 0.25% capped at $7.50; Scale has no StaffRooster transaction fee.

No. Stripe processing fees are separate and paid by the connected business according to its Stripe agreement.

The connected business manages them through Stripe. StaffRooster’s ledger reflects webhook-reported refund and dispute states; the application-fee reversal policy is disclosed before live enablement.

Yes. Protected APIs scope records to the active workspace and enforce server-side role checks.

StaffRooster provides governed data export and deletion request workflows. Destructive completion requires an authorized human review.

No certification is implied unless explicitly documented. The Security page describes current safeguards and shared responsibilities.

StaffRooster’s handling is governed by its published privacy terms, configured providers, and customer agreements. Consult the DPA and subprocessors page for contractual scope.

Use the support area inside StaffRooster for account-specific help or the public contact form for product, partnership, privacy, or access questions.