Introduction: CarbonML Documentation
The CarbonML documentation is designed to provide clear, transparent explanations of how the system operates, including available configurations, responsibilities, and operational constraints. Every section prioritizes clarity and accuracy, ensuring business stakeholders understand the platform’s capabilities and expected boundaries.
Onboarding and setup guides
Onboarding and setup guides
Phone routing and deployment models
Scheduling and calendar integrations
Operational constraints & limitations
Security, access, and adjustments
Plain Language and Audience
Documentation is purposefully written in plain, straightforward language. It is intended for business owners and decision-makers, not engineers, to ensure transparency and ease of understanding for operational leaders.
Deployment Models
This documentation provides detailed explanations of the supported deployment models. You will find guidance on call forwarding pilot setups, parallel AI number configurations, and ported number or call control platform integrations.
Every deployment method is described with its key steps, requirements, trade-offs, and limitations—empowering you to make informed choices based on operational needs.
All configuration options are presented with their constraints explained clearly to avoid unintentional misconfigurations.
Operational Transparency
The documentation highlights not only CarbonML features but also its boundaries and constraints.
Carrier-level restrictions, operational limitations, and non-negotiable rules are described directly—removing ambiguity for business planning.
Our aim is transparency: both what is possible, and what is not, are explained concretely.
Updates and Documentation Accuracy
Documentation is actively maintained to reflect the real platform and system behavior. Updates are made promptly as CarbonML evolves, ensuring accuracy and reliability in every operational detail.
Access
Some specialized documentation may be provided during onboarding or after consultation, making sure each recipient receives information appropriate to their scenario and deployment phase.
Documentation as an Extension of Trust
CarbonML treats documentation as an extension of trust and operational clarity—not as marketing material. The goal is to empower responsible, effective use through open, precision-guided explanations.
When using CarbonML, rely on documentation as a source of truth for configuration, process, and expectations.