We separate customer-ready paths from controlled rollouts and active development so the website does not overstate what is universally live.
These pages separate outcomes, trust, readiness and implementation so each question can be answered clearly.
Use the capability table to understand what can be represented as available, controlled, early access or still in development.
| Capability | Status | What that means |
|---|---|---|
| Websites & Digital Presence | Available | Customer-ready website, hosting and digital-presence work. |
| Appointments | Controlled availability | Live in enabled deployments. New-customer setup and supported scheduling scope are reviewed individually. |
| Sales | Controlled availability | Live in enabled deployments. New-customer setup, roles and supported scope are reviewed individually. |
| Reporting & Insights | Live subset | A governed report subset is launched. Reports depend on enabled features, roles and accepted scope; the full catalog is not included automatically. |
| Events | Controlled availability | Enabled event workflows have a defined scope. New events and provider-specific payment actions require readiness review. |
| Payments | Controlled rollout | Implemented payment/merchant foundation; production activation remains gated. |
| Social Media Operations | Early access | Reusable TEST-ready workflow; live provider authorization and publishing remain separately gated. |
| Church Next Steps | Early access | Reusable pilot foundation; production authorization remains gated. |
| People & team operations | TEST / limited | Authorized TEST access with a supported scope agreed before rollout. General production availability is not established here. |
| Customer Support & Help Center | Public help / TEST software | Public help is available without sign-in. Anyone with an email address can request a secure sign-in link for their own Support requests; organization workspaces require permission. Deploying the reusable Support software for another organization remains TEST / limited and requires separate readiness review. |
| Customer Portal & CareFlow | TEST / limited | Implemented TEST foundations. General production availability is not established. |
| Gift Cards | Controlled availability | TEST / limited setup. New purchases and funded activation remain gated; a hosted interface does not establish a released buying path. |
| Retail Checkout | Controlled rollout | Production-capable endpoint exists, with activation still hard-gated by payment, tax and release readiness. |
| Sales Tax Intelligence | In development | Nationwide rules/evidence infrastructure exists; production determination remains fail-closed. |
It means the capability exists in the platform or active implementation program but is not being represented as universally production-ready. Controlled rollout means activation is deliberate and may require readiness checks.
If the readiness, trust and implementation model fits what you need, the next step is to bring us the actual operating problem.
Readiness, implementation, trust and planning resources stay close at hand without taking over the primary navigation.