1. Scope of Service
Go Live Command provides operational command software for launches, support events, go-lives, onboarding projects, staff intake, routing, communications, reporting, training readiness, and governed knowledge workflows.
Service surfaces include the Staff Help Portal, ATE Console, Command Center, Projects & Map, Readiness Planner, Lifecycle, Vendor Hub, Admin setup, Industry Operations Boards (Restaurant, Retail, Mall, Pharmacy, Airline), Group Chat, the Workforce Lifecycle Suite (time clock, timesheets, expenses, open shifts, recognition, surveys, credentials), and the Training Center.
The service is not a clinical decision support tool, patient care system, emergency medical dispatch system, payroll system of record, or replacement for customer-required safety, HR, regulatory, or incident-response procedures.
2. Customer Responsibilities
Customers are responsible for configuring their organization, project, roles, routing rules, access policies, approved vendors, integrations, retention settings, QR or launch links, and staff-facing instructions.
Customers must train users not to enter PHI, patient identifiers, customer private data, payment data, passwords, badge secrets, or other sensitive identifiers into operational request fields, board items, group chat messages, timesheets, expense notes, training submissions, or any other free-text surface.
Customers must ensure that integrators connecting to Go Live Command — including any commerce webhook bridges — do not push PHI, payment card numbers, or other regulated data through those connections. Commerce webhooks are HMAC-signed operational signals only.
3. Acceptable Use
Users may submit operational support context, approved workflow questions, device or access blockers, location or callback points, non-sensitive notes, acknowledgements, and resolution documentation.
Industry Operations Boards (including Pharmacy and Restaurant boards) and Group Chat must not be used to capture PHI, patient identifiers, prescription contents, payment card data, or any clinical or regulated content. These surfaces are scoped to operational queue metadata, workflow status, and team coordination only.
Users may not use Go Live Command to request clinical advice, make patient care decisions, transmit illegal content, bypass customer security controls, harass others, or collect sensitive data outside the approved customer workflow.
4. Integrations
Optional integrations can connect Go Live Command to identity, chat, Microsoft Forms, Microsoft Excel exports, workflow automation, ticketing, staffing, scheduling, storage, monitoring, email, SMS, push, and customer-owned systems.
Each integration requires customer-approved credentials, scopes, provider policies, and security review. Go Live Command remains the operational system of record unless the customer explicitly configures an external system as the record of authority for a workflow.
5. AI and Automation
AI and automation features may classify operational issues, suggest routes, summarize interactions, detect issue themes, draft reports, recommend training follow-up, and prepare knowledge drafts.
AI output is advisory and operational. Human approval is required before staff-facing Answer Hub answers, knowledge articles, or client-visible reports are published.
6. Accounts and Access
Users are responsible for safeguarding credentials, SSO sessions, MFA devices, passkeys, and approved devices. Customers should remove project access when users no longer participate in a project.
Project offboarding removes active access while preserving historical audit data required to prove what happened during the launch or support event.
7. Availability and Changes
Production availability depends on configured hosting, database, identity, notification, storage, and integration providers. Provider outages may affect specific features even when Go Live Command remains available.
Go Live Command may update the service to improve security, reliability, workflows, integrations, compliance posture, and usability.
8. Contract Controls
These public terms summarize intended product use. Signed order forms, subscription agreements, BAAs, data-processing agreements, service-level terms, and customer-specific policies control where they differ.
Customers should review these terms with counsel before production use in regulated environments.