Plan the outcome before adding steps
Open Voice Agent Studio and the intended agent’s Call Flow. Start with the basic setup or telephone menu guide. A useful flow has a clear entry, a response or action, and a safe path when input or an external service is unavailable.
Work only on the intended agent and review its existing destinations before editing. A step’s label does not configure its target. Changing an active flow can affect future customer calls.
Collect input and use variables
- Add a Collect step and choose Menu for digit choices or Capture input for a value.
- Select keypad, speech or the offered combined input mode. Set the prompt, input limit and timeout.
- Give the captured value a clear variable name. Use the variable selector or
{{var_name}}where the editor supports it. - Connect valid input, no-input and invalid-input paths as offered. Use Conditions to branch on an expected value rather than assuming every answer is usable.
Fresh input is the normal choice. If the editor offers reuse of a previously supplied answer, use it only for suitable ordinary information. Do not configure reuse for passwords or verification codes. Avoid speaking private values back unnecessarily.
Connect an HTTP service deliberately
A Webhook/HTTP flow step calls your receiving application; it is different from account webhooks that notify you about call or SMS events. Choose the method, HTTPS URL, timeout and required headers/body. Insert only the variables the receiver needs. If using response extraction, check the returned JSON fields and configure both success and failure paths.
Use a test endpoint that does not change real customer records when developing. The flow simulator can execute an HTTP step against the configured URL. It is not an offline sandbox. Do not run a payment, booking or other irreversible action repeatedly to troubleshoot. A timeout does not prove the receiving application did nothing; check its result before retrying.
Keep credentials out of greetings, knowledge, URLs that will be shared, and screenshots. Limit access to the integration settings. Never send more personal data than the workflow needs.
Review hours and transfers
Check Business Hours, the displayed timezone and after-hours greeting/path. Review each day and test the intended closed-hours result. For transfers, choose the actual SIP line, queue or offered destination and verify that someone can answer it. Configure the offered failure/no-answer path instead of assuming an unavailable destination will find another person automatically.
Apply and verify the complete path
Resolve validation errors, use Update or Publish as offered and wait for its result. Check the published state before changing an incoming number’s destination. The simulator helps inspect branching but does not prove a real transfer rings or that two-way audio works.
With permission, test ordinary input, no input, an external-service error and the human transfer. Calls and integrations can incur charges. Use call history and the Voice Agent report to compare the public call reference, start time, duration, transcript and recording when available. A missing transcript may reflect the storage setting; a transcript does not prove a complete recording exists. A report’s call result is not proof that your external booking or update succeeded.
For problems, keep the public reference, agent name, time/timezone, step and sanitized error. Do not repeatedly publish or replay external actions without identifying what failed.