Work-A-Beez Support Center

Last updated: July 24, 2026

Support & Escalation Guide

Welcome to the Work-A-Beez Support & Escalation Guide.

This guide explains how customers obtain technical assistance, submit support requests, monitor case progress, escalate issues, and work with the Work-A-Beez Customer Success team.

Our objective is to provide responsive, transparent, and effective support that minimizes disruption to your business.


Table of Contents

  1. Purpose
  2. Support Overview
  3. Support Channels
  4. Support Hours
  5. Before Contacting Support
  6. Creating a Support Request
  7. Ticket Lifecycle
  8. Ticket Priorities
  9. Escalation Process
  10. Communication During an Incident
  11. Customer Responsibilities
  12. Administrator Responsibilities
  13. Case Closure
  14. Feedback & Satisfaction
  15. Frequently Asked Questions
  16. Related Documentation

Purpose

The Support & Escalation Guide defines the processes used to:

This guide applies to all supported Work-A-Beez subscription plans.


Support Overview

The Work-A-Beez Customer Success team provides assistance with:

Support requests are prioritized according to business impact.


Support Channels

Customers may contact support through:

Email Support

Appropriate for:

Currently, email is the primary support channel for Work-A-Beez customers.


Support Hours

Support availability depends on the customer's subscription agreement.

Typical support availability includes:

Emergency production incidents may receive priority attention outside standard business hours according to the applicable service agreement.


Before Contacting Support

To help resolve issues more quickly, gather the following information before submitting a request:

Providing complete information helps reduce resolution time.


Creating a Support Request

A quality support request should include:

Summary

A brief description of the issue.

Example:

Employees unable to clock in from the office computer.

Business Impact

Explain how the issue affects daily operations.

Expected Behavior

Describe what should have occurred.

Actual Behavior

Describe what actually occurred.

Supporting Evidence

Attach screenshots or other relevant information whenever available.


Ticket Lifecycle

Support requests progress through the following stages:

  1. Submitted
  2. Acknowledged
  3. Assigned
  4. Investigation
  5. Resolution in Progress
  6. Customer Validation
  7. Closed

Customers receive status updates throughout the lifecycle of the ticket.


Ticket Priorities

Support tickets are assigned a priority based on business impact.

Critical

Examples:

Immediate attention is provided.


High

Examples:

High-priority issues receive accelerated investigation.


Medium

Examples:

Operations continue with workarounds where available.


Low

Examples:

These issues are addressed according to product planning and operational priorities.


Escalation Process

If additional attention is required, customers may request escalation.

Typical escalation path:

  1. Customer Support Representative
  2. Technical Support Lead
  3. Engineering Team
  4. Engineering Manager
  5. Executive Leadership (when appropriate)

Escalation is based on business impact rather than the age of the ticket alone.


Communication During an Incident

For significant service disruptions, Work-A-Beez provides regular updates regarding:

Communications are delivered by email.


Customer Responsibilities

Customers can help expedite issue resolution by:

Customer cooperation is often essential for effective troubleshooting.


Administrator Responsibilities

Organization administrators are responsible for:

Administrators serve as the primary point of contact between the organization and Work-A-Beez Support.


Case Closure

A support case may be closed when:

Closed cases may be reopened if additional related information becomes available.


Feedback & Satisfaction

Customer feedback helps improve support services.

After a case is resolved, customers may be invited to provide feedback regarding:

Feedback is reviewed regularly as part of Work-A-Beez's continuous improvement process.


Frequently Asked Questions

Can I reopen a closed ticket?

Yes. If the issue recurs or additional information becomes available, you may request that the ticket be reopened or submit a new request referencing the previous case.


How are enhancement requests handled?

Enhancement requests are reviewed by the Product Management team and evaluated based on customer value, strategic priorities, and technical feasibility. Submission does not guarantee implementation.


Will I receive updates while my issue is being investigated?

Yes. Work-A-Beez provides periodic updates for active support cases, particularly those involving high-priority or customer-impacting issues.


Related Documentation


Revision History

Version Date Description
1.0 July 23, 2026 Initial publication

© 2026 LBS. All rights reserved.

Work-A-Beez® is a product of LBS.