What Cleo is designed to do
Cleo is designed for a single, user-approved job that still requires a phone conversation. The task contains a destination, an objective, context, constraints, success criteria, a result schema, and a maximum duration. Cleo reports whether the call completed, failed, or was cancelled and returns a summary and structured result when available.
Appointments
Ask about availability and coordinate a booking or reschedule within approved preferences.
Business questions
Ask about availability, pricing, policies, requirements, or other information the business must confirm.
Status follow-up
Request a current update on an order, repair, reservation, or service and return the expected next step.
Structured outcomes
Return task-specific fields so the result can be reviewed or used by the requesting workflow.
Read the detailed task boundaries for appointment calls, business information calls, and order and service follow-up.
Controls before and during a call
- A task is prepared and reviewed before a live call is requested.
- The destination and objective are shown again at the final confirmation boundary.
- A purpose evaluator blocks prohibited requests and treats ambiguous or insufficiently authorized requests as non-callable.
- A short-lived authorization is bound to the exact safety-relevant call payload; a changed payload must be evaluated again.
- Rate limits, loop prevention, a deployment call switch, and an absolute duration limit remain independent controls.
- API call creation requires both a bearer key and an idempotency key.
Current limits
- Public personal signup is not open.
- Business and API access are limited to approved projects.
- Public country and language coverage has not been announced; approved work confirms both before live use.
- Inbound answering and human-transfer infrastructure are not exposed as current public product features.
- Persistent call recording is not enabled; transcripts and structured results may be retained as service records.
- x402 is an optional advanced path under development and is not required for the default Cleo platform experience.
- A successful phone connection does not guarantee that a business will answer, provide information, or complete the requested action.
How to evaluate fit
Start with a narrow, lawful workflow that has an accountable owner and a clear finish condition. Define what Cleo may say or do, what information it may use, what result must come back, and which outcomes require a human decision. Review Responsible Calling before requesting access.