Sagecom Customer FAQ

Generally, no. Sagecom cloud services are designed to operate over the internet and can be accessed through supported IP phones, computers, mobile devices, applications, browsers, or other supported endpoints. Your specific setup depends on the Sagecom service and configuration selected.

Yes. Sagecom supports business number porting where the number is eligible for transfer. Porting generally requires accurate account information and authorization from the current carrier. Porting timelines vary by carrier, number type, location, and complexity. Customers should not cancel their existing service before the port has successfully completed unless specifically instructed to do so.

Yes. Where available, customers can select or be assigned eligible telephone numbers as part of service provisioning. Availability depends on geographic location, number type, carrier inventory, and regulatory requirements.

Yes. Sagecom services can be configured for businesses with multiple employees, departments, extensions, locations, and call flows, subject to the applicable service plan and configuration.

An extension is a user or endpoint within your Sagecom phone system. Employees can have individual extensions that can be called internally or used as part of inbound and outbound call routing.

Supported Sagecom configurations can allow employees to use mobile applications or mobile call-routing features instead of relying exclusively on a desk phone. Availability depends on the service and supported application.

Yes. Because the service is cloud-based, employees can generally use supported internet-connected devices from different locations. This makes Cloud PBX suitable for remote employees, hybrid teams, distributed businesses, and multi-location organizations.

Yes. Call transfer is a standard Cloud PBX capability, subject to the features included in your service configuration.

Yes. Sagecom supports IVR and automated call-routing functionality. An IVR can be configured to provide options such as: “Press 1 for Sales, Press 2 for Support, Press 3 for Billing.” Calls can then be routed to the appropriate department, employee, voicemail, or other configured destination.

Yes. Call flows can be configured to behave differently during business hours, after hours, holidays, or other defined periods where supported.

Virtual Office is particularly suitable for:

• Solopreneurs
• Consultants
• Independent professionals
• Small businesses
• Remote workers
• Home-based businesses
• Businesses establishing a professional phone presence

Yes. Customers can move to a more comprehensive communications configuration as their business grows, subject to Sagecom’s available plans and provisioning requirements.

No. Sagecom AI is designed primarily to augment business operations, automate repetitive interactions, and improve customer responsiveness. Businesses remain responsible for determining which activities should be handled by AI and which require human intervention.

Yes. AI deployments can be configured with human escalation pathways where supported. Businesses should define appropriate escalation rules during onboarding, particularly for sensitive, complex, urgent, or customer-specific interactions.

A typical Connect AI deployment is designed for approximately 48–96 minutes, assuming the customer has the required information available and no unusual configuration requirements. Actual implementation time may vary.

Depending on configuration, Connect AI may support:

• AI call answering
• Basic customer questions
• Business information
• Call routing
• Basic lead/customer qualification
• Appointment-related interactions
• Human escalation
• Supported SMS notifications

A basic AI configuration can operate from the information provided during setup. More sophisticated customer-controlled knowledge environments are generally more appropriate for Growth AI or Intelligent AI.

Yes. Connect AI is specifically intended to provide a relatively simple entry point into AI-powered business communications.

A typical Growth AI implementation is designed for approximately 72–120 minutes, depending on the complexity of the business process and integrations.

Connect AI focuses on quick deployment and straightforward AI interactions. Growth AI is designed for businesses that need more business-process configuration and customization. Examples include:

• Detailed call qualification
• More sophisticated routing
• Appointment scheduling
• Business-specific FAQs
• Customer intake
• CRM workflows
• SMS notifications
• Customized escalation
• More detailed knowledge configuration

Where supported, Growth AI can integrate with business systems and APIs to perform approved workflows. Examples may include CRM systems, scheduling systems, SMS services, and other supported integrations.

Intelligent AI may be appropriate for organizations that need:

• Advanced AI workflows
• Customer-controlled knowledge bases
• Multiple business processes
• Complex routing
• Advanced integrations
• Role-based access controls
• Audit logging
• AI governance
• Human escalation pathways
• Enterprise-level configuration
• Ongoing optimization

A typical Intelligent AI implementation begins with an enterprise discovery and configuration process of approximately 96–120 minutes. More complex deployments may require additional implementation work.

Yes. Customer-controlled knowledge bases are an important part of advanced AI deployments. Customers can provide approved business information that the AI is authorized to use, subject to the applicable configuration, security controls, and service limitations.

Yes. Intelligent AI is designed to support secure API integrations where applicable. API integrations may be used to connect AI workflows to business systems, subject to technical compatibility, authentication, permissions, security requirements, and the applicable Sagecom service configuration.

Yes. Businesses can start with a simpler AI deployment and expand their capabilities as their requirements grow, subject to Sagecom’s available plans and configuration requirements.

Yes. Businesses with increasingly sophisticated requirements can expand into a more advanced AI configuration. The upgrade may require additional discovery, configuration, integration, testing, and knowledge-base work.

For applicable AI plans, customers can provide and manage approved business information and knowledge used by the AI. Customers should ensure that information supplied to the AI is accurate, current, authorized, and appropriate for the intended use.

Yes. AI systems can produce incorrect, incomplete, outdated, or inappropriate responses. Customers should not rely on AI output as a substitute for professional judgment where accuracy is critical.

Sagecom’s AI approach may incorporate controls such as:

• Defined system instructions
• Customer-controlled knowledge
• Human escalation
• Role-based access
• Audit logging
• Monitoring
• Secure integrations
• Privacy-by-design principles
• Responsible AI governance
• Periodic security and compliance reviews
• Continuous platform improvement

No AI system can guarantee that errors will never occur.

AI should not be treated as a substitute for qualified professional advice. Where an AI deployment operates in a regulated or sensitive environment, the customer should establish appropriate guardrails, escalation procedures, disclaimers, and human review requirements.

Yes, where supported. Human escalation rules can be established during implementation. Examples include:

• Customer requests a human
• Sensitive issue
• Complaint
• Complex request
• Account-specific issue
• AI confidence or knowledge limitation
• Emergency or urgent situation
• Business-defined escalation criteria

Where configured, the AI workflow can trigger supported SMS or other notifications.

This depends on the scheduling integration and workflow configured for the business.

Where the applicable integration supports it, AI can be configured to create or update records according to defined rules and permissions.

This depends on the selected plan, integration, workflow, and configuration. Customers should define what information should be recorded and which activities require human approval.

Where enabled and properly configured, AI workflows may trigger SMS messages. The customer is responsible for ensuring that its messaging practices comply with applicable laws, regulations, consent requirements, and Sagecom policies.

Not necessarily. Availability and activation depend on the applicable service configuration.

Customers are responsible for determining and implementing legally required notices and consent procedures applicable to their calls. Sagecom provides technology and configuration capabilities but does not determine the customer’s legal obligations.

Sagecom’s handling of customer information is governed by its applicable Privacy Policy and contractual commitments. Customers should review the applicable privacy documentation for details regarding collection, use, disclosure, retention, and processing of information.

Yes, where supported by the applicable service. Role-based access can help organizations limit administrative and operational access according to job responsibilities.

Advanced AI configurations may support audit logging and monitoring. The scope and retention of logs depend on the applicable service, configuration, and contractual terms.

Where available, enterprise configurations may support SSO or other centralized authentication capabilities. Availability depends on the applicable service and implementation.

Supported services can provide administrative controls for managing users, extensions, services, and permissions.

No. Cloud/VoIP emergency calling can have important operational limitations. Customers should review Sagecom’s emergency-service provisions and ensure that employees understand how to contact emergency services if the Sagecom service is unavailable.

Customers should maintain appropriate alternative means of contacting emergency services where necessary.

Sagecom works to restore affected services as quickly as reasonably practicable. The applicable Service Level Agreement establishes the specific service commitments, exclusions, support procedures, and remedies.

No. The SLA identifies circumstances that are excluded from downtime calculations, including certain scheduled maintenance, emergency maintenance, third-party failures, customer-side issues, internet connectivity problems, force majeure events, and other specified exclusions.

Where applicable, service credits are generally the exclusive remedy for qualifying SLA failures, subject to the terms and limitations of the applicable SLA.

Service-credit provisions may contain limits and restrictions, including provisions preventing cumulative or duplicative credits for the same underlying event.

Yes. Emergency maintenance may be performed when necessary to address security, reliability, infrastructure, operational, or other urgent issues. Emergency maintenance may not always allow for the same advance notice as scheduled maintenance.

Depending on the service, customers may need to provide:

• Business information
• Authorized contact information
• Billing information
• Telephone numbers
• Number-porting information
• Users and extensions
• Business hours
• Call-routing requirements
• IVR prompts
• AI business information
• FAQs
• Scheduling information
• CRM/integration credentials
• Escalation rules
• Compliance requirements

Training and onboarding support may be provided according to the applicable service plan or implementation package. Enterprise implementations may include more extensive configuration and training.

AI plans may include a defined quantity of AI usage. Additional usage may be billed according to the applicable plan’s overage rates. Customers should review their specific plan and order documentation for current pricing and included usage.

Yes. Customers can generally upgrade when additional users, features, AI capabilities, usage, or integrations are required.

Cancellation is governed by Sagecom’s applicable Refund & Cancellation Policy and the customer’s order or service agreement. Customers should review applicable notice periods, outstanding charges, non-refundable amounts, and other cancellation conditions before terminating service.

Automated calling may be permitted for legitimate business purposes, but customers are responsible for complying with applicable telecommunications, telemarketing, consent, calling-time, messaging, and privacy laws.

AI services must be used responsibly and in accordance with Sagecom’s AI Services Terms and applicable policies. Customers should not use AI to deceive, defraud, impersonate, manipulate, or unlawfully misrepresent individuals or organizations.

Sagecom and its licensors retain ownership of Sagecom’s technology, software, platforms, systems, trademarks, service configurations, documentation, and other proprietary materials except where expressly provided otherwise by agreement.

Not necessarily. AI configurations, software, prompts, workflows, platform components, and related materials may be subject to intellectual-property and licensing restrictions. Customers should review the applicable agreement before attempting to reproduce or transfer Sagecom technology or configurations.

No. Administrator credentials should be assigned only to authorized personnel. Customers should use individual accounts and appropriate access controls wherever supported.

Yes, applicable AI services can be configured with business-specific instructions, tone, behavior, knowledge, and escalation rules.

Where supported, customers can configure an AI persona or agent identity appropriate to their business.

Yes. AI configurations can generally be updated as the business, products, services, policies, and customer requirements change.

No. AI access should be limited to information, systems, tools, and permissions explicitly made available to the AI configuration. Advanced deployments can use role-based access controls and other governance mechanisms to restrict access.

Where supported, AI can execute approved workflows through configured tools and integrations. Businesses should define which actions AI may perform automatically and which require human approval.

Such capabilities should not be assumed. They require specific system integrations, authorization, workflow controls, and business approval. Customers should establish appropriate controls before enabling AI to perform sensitive transactions or business actions.

Cloud PBX is designed for businesses that need extensions, call routing, IVR, voicemail, transfers, and broader business phone functionality. I want basic AI answering and customer interaction. Connect AI is designed for quick deployment of AI-powered communications. I want AI customized around my business processes. Growth AI is designed for more customized workflows, business knowledge, scheduling, qualification, routing, and integrations. I need advanced AI, integrations, knowledge management and governance. Intelligent AI is designed for more sophisticated and enterprise-oriented AI deployments.