Terms of Agreement
These terms set the public operating boundary for Go Live Command: real-time support routing, no-PHI intake, governed AI, customer-controlled integrations, and audited launch operations.
Last updated: May 21, 2026Go 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.
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.
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.
Users may submit operational support context, approved workflow questions, device or access blockers, location or callback points, non-sensitive notes, acknowledgements, and resolution documentation.
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.
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.
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.
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.
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.
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.