Trust & Security
CarbonML is built to support critical business operations like phone lines and scheduling. Trust, security, and control are treated as foundational requirements, not as optional features. The platform’s design centers on enabling responsible operation and reliable oversight for every integration.
Access control in CarbonML is rooted in limited-scope permissions. Account passwords are never required. Access is granted only via API keys or specific routing permissions, and always restricted to defined functions such as scheduling or call routing. Businesses can revoke access at any time, maintaining autonomy and oversight.
Scheduling integrations use platforms like Cal.com. CarbonML can view only the calendar availability required for booking—no personal emails or unrelated calendar data are accessed. API keys are managed solely by the business, which can delete or regenerate them as needed.
Phone System Responsibility
CarbonML operates strictly within carrier and telecom requirements. It never bypasses carrier rules. Call routing behaviors are precisely defined and approved before deployment. Human escalation endpoints are set to prevent loops, and all call flows are tested thoroughly before going live.
Operational Transparency
CarbonML prioritizes transparency, clearly documenting capabilities and limitations. Trade-offs between deployment models are explained before any rollout.
There is no hidden behavior or automated change. All configuration changes require business approval—nothing happens without review.
Integrations can be disabled
Call forwarding can be turned off
Routing configurations adjusted or removed
Ownership of phone numbers/systems retained