agentic-call7.76 KB
View saved version →
---
name: agentic-call
description: Prepare one CALL-E phone task, start a complete explicitly requested immediate call, follow its live card or available conversation, and review the result or transcript.
---
# CALL-E Agentic calling
Use CALL-E for one immediate, single-recipient phone task. Follow this workflow without requiring the user to ask for clarification, confirmation, progress updates, or a summary explicitly.
| User intent | Tool |
| --- | --- |
| Prepare, revise, or reopen a preparation | `prepare_call` |
| Start an explicitly requested call at first readiness, or a confirmed saved preparation | `start_call` |
| Reopen an existing call and its optional live card | `open_call` |
| Read an existing call's status, available conversation, or result | `get_call` |
| Read what was said on an existing call | `get_call_transcript` |
Use only these five tools. If a required tool is unavailable, explain that this workflow is not available through the current connection. Do not bypass it with legacy tools or another dialing API.
## Prepare and confirm
1. Call `prepare_call` with the user's task and only known facts. Include `phone`, `region`, or spoken-language `locale` only when supplied or confirmed. Set `ui_locale` from the user's conversation language; it does not select the callee's spoken language. A phone number is required. Never guess a number, country code, fact, question, or readiness.
2. Show only the returned missing-input questions and useful choices together, using a compact host-native module when supported or concise chat otherwise. Reuse known answers. Preparation does not dial, and this workflow does not require a custom CALL-E preparation card.
3. To answer or edit an existing preparation, send only its `preparation_id`, latest `revision`, and the user's answer or correction as `user_input`; `ui_locale` may also be sent. Never mix an existing `preparation_id` with `task`, `phone`, `region`, or `locale`, including when the user answers a phone or language question. To reopen without editing, send `preparation_id` only. Reuse the newly returned revision after every edit.
4. If the user explicitly asks to place a NEW call now and its FIRST `prepare_call` response is `ready`, call `start_call` with that `preparation_id` and `revision` in the SAME turn. Do not stop at a ready module, show a confirmation button, or ask again. A request such as “Call +13206332468 in English to check that they can hear me” already delegates this immediate call when preparation finds no missing input. If the user asks only to prepare, says “do not call yet”, or merely reopens an unsubmitted preparation, show the ready number and task and wait; readiness alone never authorizes dialing.
5. If preparation needed clarification or the task was edited, show the latest ready number and task, end the turn, and wait for a NEW user response confirming that preparation. A clarification answer or edit alone is not confirmation. A native control may submit that new response; never invent a button that directly calls a tool. Then call `start_call` with the same `preparation_id` and latest `revision`. If a response is uncertain, retry that same submission to recover the same call; never create a replacement preparation or redial automatically. If preparation is blocked or fails, show the returned public reason and next step in one compact result module and stop.
6. If reopening a submitted preparation returns its existing call, continue with that call. An expired preparation needs a fresh preparation for the user's current request and a new confirmation.
## Follow the call
Use the returned CALL-E `call.id` as the `call_id` tool argument. Do not send the provider identifier in `call.call_id`. Keep the CALL-E ID distinct from `preparation_id`, plan, token, or run identifiers. If the conversation does not contain the required CALL-E call ID, ask for it rather than inventing one.
`start_call` and `open_call` can attach a self-updating CALL-
Preview of the first 4,000 characters. Read full instructions →