Avaya Cloud Office

The implementation of Avaya Cloud Office is designed to be a streamlined and low-disruption process, leveraging its cloud-based architecture. The platform handles most of the system maintenance and updates, which simplifies the typical, lengthy implementation cycle for on-premise solutions. The overall duration from account creation to full operational status is typically very short.

Overview

Avaya Cloud Office focuses on a rapid path to cloud communication, particularly for existing Avaya customers, by providing a tailored migration that retains familiarity with existing Avaya telephony features and devices. The initial digital setup is immediate, making the service accessible almost instantly, with the main time constraint being the physical delivery of any new hardware required. Administration is simplified through automatic updates and a "hands-off" approach managed by Avaya.

Bullet Points

• Account Activation: The user account and associated phone numbers are activated immediately upon sign-up.
• Hardware Delivery: Physical desk phones or other hardware typically arrive within 5 to 7 business days, depending on the chosen shipping method.
• Migration Approach: A tailored cloud migration path is provided, minimizing business disruption, especially for customers transitioning from previous Avaya telephony systems.
• Administration: Post-implementation, the system is designed for simplified administration with automatic updates, requiring no manual effort for platform maintenance.

The software is engineered with a wide range of customizable options, enabling businesses of any size to tailor the communication experience. This includes integrating the communication platform directly into existing business applications to improve productivity, and providing tools for administrators to configure the system and monitor performance based on their specific needs.

Bullet Points

• App Integration: The platform supports over 300 integrations with popular business applications, including services like Salesforce, Office 365, and G Suite, allowing communication to be embedded directly into workflow tools.
• Custom Dashboards: Users can track key performance indicators (KPIs) and operational metrics by creating custom dashboards with the built-in analytics and reporting tools.
• User Experience: Features like team collaboration, voice and messaging, and meeting capabilities can be configured to match a company's preferred methods of communication.
• Migration Flexibility: The tailored cloud migration process itself is a form of customization, allowing businesses to transition to the cloud while maintaining familiar features and devices.

Avaya Cloud Office operates on a subscription model where continuous maintenance and basic support are generally included, eliminating the need for separate fees for system updates and hardware upkeep. This is a "hands-off" cloud solution, meaning the provider manages the infrastructure. Any potential setup fees or premium support charges would be outlined during the selection of the pricing package.

Bullet Points

• Maintenance: There are no separate maintenance fees for the core platform. The solution is cloud-based, meaning Avaya manages the system, providing automatic and seamless updates with no manual effort required from the customer.
• Setup Fees: The presence and amount of one-time setup fees are typically dependent on the complexity of the deployment and the negotiated subscription package. Customers should consult the specific pricing tiers for this detail.
• Support Charges: Enterprise-grade support is often bundled into the subscription price, but premium or dedicated support options may be available for an additional charge.
• Hardware Costs: While the software is a service, the purchase or lease of compatible Avaya desk phones and other endpoints would represent an initial hardware cost, separate from the monthly per-user license fees.

Training is offered to both end-users (employees) and customer administrators. New customers often receive dedicated training sessions as part of their Professional Services engagement, scheduled after the initial planning and design phases. Additionally, a comprehensive library of online, web-based training (WBT) courses is available to facilitate self-paced learning on specific features and application usage across different devices. Support services are also available to ensure the smooth operation of the system post-deployment.

Detailed Bullet Points

• Dedicated Training Sessions:
  • Administrator Training: New customers typically receive dedicated online sessions, often about two hours long, focused on the Admin Basics Agenda. This covers introducing the solution, building out the organization's call flow, making regular updates in the Admin Portal, and configuring the company view.
  • End-User Training: Sessions are targeted at employees who will use the system, demonstrating how to get started with the Avaya Cloud Office system and applications. The specific topics are customized based on the phones and applications the customer will be using.
• Web-Based Training (WBT) Courses: A suite of complimentary, self-paced courses is available for different user roles and applications, including:
  • User Application Training: Specific WBTs for using the Desktop App, Mobile App, Service Web (My Extension), and compatible J-Series desk phones.
  • Administrator Training: Courses focused on Introducing and Administering the Avaya Cloud Office Service Web and using the mobile app for administration tasks.
• Pre-Work and Self-Service Resources:
  • Customers are encouraged to access Getting Started Tutorials and How-To information on the support portal prior to attending formal training.
  • Resources cover overviews of the Unified Mobile Application, Desktop Phone Application, User Portal (My Extension) settings, messages, contacts, and call logs.
• Ongoing Support Services: Comprehensive, cost-effective support is offered to maximize system performance, reliability, and availability, with an emphasis on quickly resolving issues.

Security is a foundational element of the platform, managed by Avaya’s cloud security teams. The security architecture includes strong encryption, advanced access controls, proactive monitoring, and compliance with numerous industry and regulatory certifications. This ensures all communication and stored data are protected against unauthorized access and threats.

Detailed Bullet Points

• Encryption for Data Protection:
  • Encryption at Rest: Sensitive data stored in the cloud is protected by encryption.
  • Encryption in Transit: Communications are secured using protocols like Transport Layer Security (TLS), often employing the latest versions and strong ciphers. Voice communications between endpoints are encrypted.
• Access Controls and Authentication:
  • Role-Based Access Control (RBAC): Access to system resources is controlled based on a user's role, ensuring a principle of least privilege where users only access what is necessary for their job.
  • Strong Authentication: Authentication mechanisms are based on industry standards, with encrypted or hashed storage of passwords, strong password policies, and support for Single Sign-On (SSO) integration.
• Platform Security and Compliance:
  • High Availability and Disaster Recovery: Comprehensive Business Continuity and IT Disaster Recovery plans are in place to ensure system reliability and quick recovery following a disruptive incident.
  • Security Certifications: The platform adheres to global security certifications and standards, which may include compliance with standards like ISO 27001, SOC2, and in certain regions or services, regulations like HIPAA (for healthcare) and PCI DSS (for credit card data).
  • Continuous Monitoring: The infrastructure is monitored 24/7/365 to detect, respond to, and isolate threats in real-time.

Updates for Avaya Cloud Office are released continuously and automatically to the platform. Unlike traditional on-premise software that requires manual installation and patches, the cloud model ensures that users are always running the latest version with the newest features, security patches, and performance enhancements with minimal to no disruption. The change management process is handled by the provider.

Detailed Bullet Points

• Automatic and Continuous Updates: Updates are managed entirely by Avaya, eliminating the need for customer IT staff to manually download, test, or deploy patches or new versions. This means the system is always current.
• Disruption-Free Management: The updates are designed to be automatic and disruption-free, ensuring that the platform remains current without any manual effort or downtime that would impact business operations.
• New Feature Releases: New features, performance enhancements, and security improvements are deployed centrally to the cloud environment, making them available to all customers as soon as they are rolled out.
• Change Management: Significant changes to the system or service are managed via a formal Change Management Process, ensuring that all necessary parties are notified and prepared for any planned maintenance or substantial updates.

As a provider of a cloud communication platform, the software vendor (Avaya, in partnership with RingCentral) operates as the Data Processor, while the customer organization retains ownership and control of their proprietary data, content, and communications (such as call logs, voicemails, and messages). The commitment to data ownership is typically outlined in a Data Processing Addendum (DPA) that accompanies the main service agreement. Data portability is supported to comply with global regulations and ensure customer flexibility, allowing for the transfer of personal data in a usable format.

Detailed Bullet Points

• Customer Data Ownership: The customer explicitly maintains full legal rights and ownership over all proprietary data they input and generate within the system, including call recordings, messages, user information, and configurations.
• Service Provider as Data Processor: The software vendor acts solely as the Data Processor or Service Provider, obligated to process the data only on the customer's instruction and for the purposes of providing the agreed-upon services. This relationship is formalized in a Data Processing Addendum (DPA).
• Data Portability Rights: The platform is designed to support the customer's right to data portability, especially as mandated by regulations like GDPR. This right allows the customer to obtain and reuse their data across different services.
• Data Retrieval and Transfer: While specific terms are governed by contract, the provider ensures the ability to assist the customer with data requests and the transfer of personal data in a structured, commonly used, and machine-readable format (e.g., CSV files) upon request, such as at the termination of the contract.

The cloud model of Avaya Cloud Office is inherently scalable, designed to support businesses of any size from small startups to large enterprises. Scaling is primarily managed by adjusting the number of user licenses through the administrative portal or the sales/partner channel. The subscription-based pricing model ensures that organizations only pay for the users they need, though the precise terms for adding or reducing licenses are governed by the specific Service Level Agreement (SLA) or Master Cloud Agreement (MCA). Scaling up is typically immediate, while scaling down is subject to the contract's minimum commitments and renewal terms.

Detailed Bullet Points

• Ease of Scaling Up:
  • Immediate Provisioning: Customers can easily add new users, phone numbers, and services on-demand, often through the administrative portal, which facilitates quick provisioning of new employees or locations in minutes.
  • No Hardware Constraints: Scaling up does not require purchasing, installing, or configuring new on-premise hardware infrastructure, as the solution is entirely cloud-based.
• Flexibility in Scaling Down:
  • Subscription-Based Model: The service uses a per-user, per-month pricing model, allowing for a degree of cost predictability and consumption-based billing.
  • Contractual Terms: The ability and timing of scaling down (reducing the total number of user licenses) is subject to the specific terms of the customer's subscription agreement. Most cloud contracts will have minimum user counts or commitment periods that govern when licenses can be removed to reduce the monthly cost.
• License Management:
  • Centralized Administration: Administrators can manage all users and licenses from a single, cloud-based interface, simplifying the process of adding or deactivating seats.
  • Global Reach: The platform allows for scaling across multiple geographic locations, connecting remote and international workers to a single communication system with unified features.

Renewal of the contract is often structured as an automatic renewal for successive periods (e.g., one year) unless one of the parties provides a written notice of non-renewal within a specified timeframe (commonly 30 or more days) before the end of the current term. Cancellation is generally permitted under two main conditions: termination for convenience by the customer, which may result in termination fees or the forfeiture of prepaid amounts, or termination for cause by either party in the event of an uncured material breach of the agreement, such as non-payment or failure to provide service as agreed.

Detailed Bullet Points

• Contract Renewal (Automatic):
  • Automatic Renewal: Contracts for recurring services, such as user subscriptions, typically automatically renew for successive terms (e.g., annual) unless explicitly opted out.
  • Notice of Non-Renewal: To prevent automatic renewal, the customer must provide a written notice of non-renewal to the vendor, usually at least 30 days before the expiration date of the current term.
• Cancellation (Termination for Convenience):
  • No Refund Policy: If the customer cancels a subscription before the end of a committed term (e.g., a one-year contract), they generally will not be entitled to a refund or credit for any fees already paid or due for the remainder of the committed period.
  • Applicable Fees: Termination for convenience may subject the customer to specific termination fees as outlined in the Order Form or Service Description.
• Cancellation (Termination for Cause):
  • Material Breach: Either the customer or the vendor may terminate the agreement for cause if the other party commits a material breach of the terms and conditions.
  • Cure Period: The terminating party is typically required to provide written notice of the breach, and the defaulting party is given a specific cure period (e.g., 30 days) to remedy the breach before the termination takes effect.

As a global Unified Communications as a Service (UCaaS) solution, the software adheres to strict global data privacy and security frameworks. The platform aims to be compliant with major international and regional regulations concerning personal data protection and financial data security, such as those related to the European Union, the healthcare industry, and payment card processing. The compliance is often a shared responsibility, but the vendor guarantees the platform's certification for these standards.

Detailed Bullet Points

• Global Data Privacy Standards:
  • GDPR (General Data Protection Regulation): Compliance with this European Union regulation, ensuring strong protection for the personal data of EU residents, including requirements for data processing and data portability.
  • CCPA (California Consumer Privacy Act): Adherence to the privacy and consumer rights requirements for residents of California, which is a key regulation in the United States.
• Industry-Specific Compliance:
  • HIPAA (Health Insurance Portability and Accountability Act): Compliance with the necessary security and privacy standards required for handling protected health information (PHI) in the healthcare sector, often formalized via a Business Associate Agreement (BAA).
  • PCI DSS (Payment Card Industry Data Security Standard): Adherence to security standards for organizations that handle branded credit cards from the major card schemes, particularly relevant for contact center functionalities.
• Emergency Service Regulations:
  • Kari's Law and RAY BAUM'S Act (US): Compliance with US federal laws concerning multi-line telephone systems to ensure immediate and accurate dispatchable location information is transmitted with 911 calls.
• Platform Security Certifications:
  • SOC 2 (Service Organization Control 2): Certification demonstrating that the service provider's systems and controls meet professional standards related to security, availability, processing integrity, confidentiality, and privacy.