Version 1.1 · Effective August 24, 2026 · Last updated: September 07, 2026
Important: This public document states Work-A-Beez's standard service-level objectives and support practices. It is not a guaranteed uptime SLA, service-credit schedule, fixed recovery commitment, or guaranteed response-time contract unless a Customer Order Form or other signed agreement expressly incorporates specific service levels.
Linton Business Solutions, LLC ("LBS") seeks to operate Work-A-Beez as a reliable cloud workforce-management service. These objectives describe how LBS prioritizes availability, support, maintenance, and incident response for standard subscriptions.
These objectives apply to the core Work-A-Beez production web service, organization administration, employee timekeeping functions, scheduling/PTO/reporting functions that are generally available in the subscribed plan, and related authentication functions operated by LBS.
They do not create commitments for beta/preview functionality, customer networks or endpoints, customer-created integrations, unsupported browsers or devices, internet providers, third-party systems outside LBS's control, or features not included in the Customer's plan.
LBS uses commercially reasonable efforts to maintain reliable production availability. Standard self-service plans do not currently include a public numeric uptime guarantee or automatic service-credit entitlement. If a Customer requires a specific uptime percentage, measurement methodology, exclusion list, or service-credit remedy, those terms must be stated in a signed agreement.
LBS may evaluate service health using application health checks, provider monitoring, error information, support reports, and other operational signals. Different components can have different availability characteristics. The existence of a health check or monitoring signal does not itself create a contractual uptime measurement method.
LBS may perform maintenance to deploy security updates, product releases, database changes, performance improvements, or infrastructure changes. LBS will use commercially reasonable efforts to reduce customer impact and provide advance notice when practical for maintenance expected to materially affect service availability.
Emergency maintenance may occur without advance notice when reasonably necessary to protect security, data integrity, platform stability, or customer access; respond to an active incident; address a critical provider issue; or prevent material harm.
Work-A-Beez depends on third-party infrastructure and services, including hosting/database providers, payment processing, transactional email, and integration/notification providers. A third-party incident may affect functionality even when the Work-A-Beez application itself remains operational. LBS will use commercially reasonable efforts to coordinate restoration when a provider affects the Service, but LBS does not control the provider's recovery timeline.
Standard support is available through info@lbsconnect.net and any support channels made available inside the Service. Telephone, priority, after-hours, or dedicated-account support is available only if included in the Customer's plan or a separate written agreement.
LBS prioritizes support and operational incidents based on customer impact, number of affected users, security implications, data integrity, availability, existence of a workaround, and business criticality.
LBS will use commercially reasonable efforts to acknowledge and investigate support requests in accordance with severity and available staffing. Unless a signed agreement states otherwise, the standard service does not guarantee a fixed one-hour, four-hour, one-business-day, or other response time, and does not guarantee restoration within a fixed number of hours.
Resolution timing depends on technical complexity, reproducibility, customer cooperation, security considerations, provider dependencies, and whether a code or infrastructure change is required.
Work-A-Beez maintains business-continuity and disaster-recovery practices intended to restore critical service functions after significant disruption. Standard self-service plans do not include a fixed contractual RTO or RPO. Backup and point-in-time recovery capabilities depend in part on the active managed-database and hosting plan.
Security incidents are managed under the Work-A-Beez incident-response process. If LBS confirms a Security Incident affecting Customer Personal Data, LBS will notify affected Customer without undue delay as required by applicable law and contract. Security investigation and customer notification are distinct from ordinary support-response targets.
Any negotiated availability calculation or service-level commitment may exclude, as specified in the applicable signed agreement, events such as planned or emergency maintenance, Customer acts or omissions, unsupported configurations, Customer networks/devices, third-party systems outside LBS's reasonable control, force majeure, internet backbone failures, malicious attacks outside LBS's reasonable control, lawful government action, and suspension permitted under the Agreement.
Standard self-service subscriptions do not include automatic service credits for downtime unless a signed agreement expressly provides a service-credit remedy. If a negotiated SLA applies, the signed agreement will define the exclusive measurement and remedy terms.
Customers with material regulatory, operational, procurement, or availability requirements may request negotiated service levels. Any negotiated uptime target, support-response commitment, RTO/RPO, service credit, or escalation procedure is effective only when set out in a signed agreement.
This document should be read with the Terms of Service, DPA, Security Policy, Business Continuity Summary, Disaster Recovery Summary, and Backup Overview. If a signed Customer agreement conflicts with this public document, the signed agreement controls.
Operational and support questions may be sent to info@lbsconnect.net.