An eligible account can request an ordinary outgoing call directly in the console. You do not need an agent readiness message or an attended test window. Call now and Schedule create real call requests; review the recipient and call brief before submitting.
Check eligibility and destination
Open Agents → your agent → Outgoing. Use an account administrator session and an active published agent with an eligible outgoing subscription, available usage and a valid calling route. Outgoing calling is available on eligible Pro/Max subscriptions; Plus is forwarding-only. Availability is checked again before execution.
Currently qualified ordinary destinations are Turkish mobile numbers. Enter +90 followed by the ten-digit mobile number; spaces and parentheses are accepted. The form’s general hint also mentions landlines, but ordinary landline calling is not currently qualified and is rejected. International, special/premium and protected ingress numbers are unsupported. A correctly formatted number alone does not establish eligibility.
Give the call a specific job
- Enter Phone number for the intended recipient. Do not use an example number for a real request.
- Fill the required Goal with a short, specific outcome.
- Review the required First message. It starts with a neutral Turkish introduction identifying the speaker as an AI voice assistant and asking whether now is a suitable time to talk. Edit it for this call, using no more than 500 characters. It is separate from the inbound greeting; do not leave it blank.
- Add context, questions or limits in Additional instructions (optional) if needed. This field starts empty and can stay empty, including for a feedback conversation. The agent’s published configuration still applies.
- Under Timing, keep the default Call now or choose Schedule.
- Review the recipient, goal, first message, optional instructions and timing, then select the submission button with the same label.
Use this fictional feedback brief as a writing example, not a request to place a call:
Goal: Learn what went well at the workshop visit and what could improve.
First message: Hello, I am Example Workshop's AI voice assistant. I am calling
for feedback about your visit. Is now a suitable time for a short conversation?
Additional instructions (optional): [Leave this field empty for this example.]
The first message is the opening you ask the agent to use, not a guarantee of exact spoken wording or timing. Review the conversation afterward. Do not use a feedback goal as implicit permission to book, save or send anything.
Review published Available actions
Available actions shows the agent’s published custom actions. Use Manage connections to return to Configuration, where connections and tool selections are managed. Identity, voice, knowledge and tools stay in the shared agent configuration; there is no separate outgoing setup.
If you changed the shared configuration or tool selection, Save draft and Publish before relying on it in a new call. Draft selections do not become available merely by entering a goal or instructions. A listed action does not guarantee that the external service will accept or complete it. See Custom MCP servers for the published connection workflow; provider-specific drafts do not establish working Google or payment capabilities.
Conversation feedback is native: the agent can converse and report what was learned without a connected MCP service. Connect a service only when the task needs its external action. Collecting feedback and confirming its save are separate outcomes.
Schedule in the displayed timezone
Choose Schedule, then set Date and time in the future within the next 30 days. The form shows the timezone resolved for your browser; an Istanbul browser displays Europe/Istanbul. Review the displayed timezone and time before submitting; do not assume it uses the recipient’s local timezone.
Eligibility, agent state, funding and capacity are checked when work proceeds. A scheduled request is not a guarantee that a call will connect. Paused or ineligible agents may have requests skipped or denied. A missed execution is not automatically caught up, and an unsuccessful call is not automatically redialed.
Read the request status
After Call request accepted, inspect Call requests. Use Refresh when the latest state is unclear.
| Status or outcome | Meaning |
|---|---|
| Scheduled / Queued / Waiting for availability | The request is waiting; it has not established a conversation. |
| Ringing / Connected | The call is progressing. Connection alone does not prove the task succeeded. |
| Busy / No answer / Call failed | The attempt did not establish the intended conversation. Review before making another request. |
| Conversation ended | The conversation ended; inspect available call evidence for what was achieved. |
| Submission unconfirmed / Call submission unconfirmed | Submission is uncertain. Do not create a second request merely to obtain a success message. |
| Skipped — agent paused / Could not start / Call not placed | Work did not proceed as intended. Read the reason and check agent/account availability. |
If creation cannot be confirmed, keep the same details and use the console’s same-request retry flow. Existing request found. No duplicate was created identifies a recovered request, not a second call. If there is a request-key conflict, refresh requests rather than changing details and blindly submitting again. For insufficient usage or eligibility errors, resolve that specific condition first.
Cancel work that has not started
On a waiting request, select Cancel request, read the confirmation and confirm only the intended request. Cancellation is available only before the request moves forward. If it has already progressed, the console refreshes its status; cancellation is not confirmed by pressing the button alone. Refresh after an unclear cancellation result.
Use View call result when available, or the agent’s Calls tab, to review a finished call. A summary or transcript can help establish the next step, but is not proof of an external booking or message. Review Call history and usage and the underlying business record before claiming completion.
Separate conversation assessment from external results
In Call history or the agent’s Calls tab, review the learned facts, next action and Conversation goal (AI assessment). Assessed as achieved, Assessed as not achieved and Unclear from the conversation describe the AI’s assessment of the conversation. Neither that assessment nor Conversation ended confirms an external save, booking or message.
Read External actions separately. Service returned a result reports a service response, not verified business success. The external change has not been verified still requires checking the underlying business record. Request failed, Request denied and Request outcome unconfirmed retain their own meaning; an unknown effect is not a successful effect. A protocol-valid tool reply or model statement alone does not confirm a business change.
For example, the conversation may collect useful feedback while its external save fails or remains uncertain. Report both facts. Do not blindly retry an uncertain external submission; first check whether it took effect.
If the summary or assessment is unavailable, the goal remains unconfirmed. Review the available Transcript and its coverage rather than inventing a result. Ambiguous summary submission may stop automatic retries to avoid duplication; a separately available transcript can still support manual review. A missing or partial transcript does not establish the missing conversation. See Call history and usage.