Security
Security and operating boundaries for Cleiro.
Cleiro is designed around scoped call flows, limited intake fields, controlled handoffs, and human-owned decisions for home-service businesses. This page describes operating boundaries, not a certification claim.
Security
Cleiro active
Incoming call
Answered
AI conversation
Qualified
Routing rule
Applied
Next step
Ready
Call summary
Security starts with clear operating rules.
The pilot maps what Cleiro should ask, what it should capture, what it should route, and what it should never promise before calls are handled for the business.
Service boundaries
Approved categories, locations, hours, and escalation paths
Defined in pilot
Human review
Staff own scheduling commitments and technical decisions
Configured
Data minimization
Call intake focuses on details needed for follow-up
Scoped
Certifications
No SOC 2, HIPAA, ISO, SLA, or penetration-test claim is made on this page
Not claimed
What Cleiro should not do.
Security and quality depend on avoiding unsupported promises and unsafe advice.
No unsafe troubleshooting
Electrical, plumbing, HVAC, roofing, and restoration calls should route details to staff rather than diagnose hazards.
No fake guarantees
The website and product flow should not promise recovered revenue, booked jobs, or guaranteed response times.
No hidden replacement claim
Cleiro supports staff coverage gaps; humans remain responsible for customer-sensitive follow-up.
What should be confirmed during implementation.
Security review should be tied to the actual customer workflow, providers, data fields, retention expectations, notification paths, and staff responsibilities. Do not rely on a generic website page for customer-specific controls.
Data fields
Confirm which caller details Cleiro should collect and which information should never be requested in the call flow.
Recipients
Confirm who receives summaries, how they are notified, and who owns follow-up.
Review status
Claims beyond operating boundaries need technical, legal, or security confirmation before publication.
Dispatch intake
What we test before live call handling.
Security and quality review should include the practical places where a call flow can create risk: wording, recipients, escalation language, and summary content.
Sample calls
Confirm the greeting, questions, and no-advice boundaries
Review
Escalation wording
Confirm urgent categories without promising service timing
Review
Summary recipients
Confirm who receives caller details and who owns action
Review
No-promise QA
Confirm Cleiro avoids pricing, diagnosis, guarantees, and commitments
Required