Voice-agent lifecycle - Sendora

Voice agents combine configuration with real-world communication. Treat every test-call, publish, inbound-channel, and phone operation as a controlled side effect.

Build sequence

draft → configuration → knowledge/tools → channels → browser test → phone test → publish

Create or save a draft.
Update the agent prompt, voice, greeting, and safeguards.
Attach processed knowledge bases and only the tools the agent needs.
Configure channels and inbound behavior explicitly.
Use browser test calls with synthetic data first.
For browser microphone setup and the website widget path, see WebRTC browser calls.
Use phone test calls only with an approved test number.
Publish after human review of the transcript and tool behavior.

Test calls

Test calls may consume credits, create call records, and contact a real number. They are not safe to repeat automatically after a timeout. Query call history or the returned job/call ID before retrying.

Publishing

Publishing changes which configuration can receive traffic. Keep a copy of the reviewed configuration, record the agent public ID and publish result, and disable or update channels deliberately if the agent behaves unexpectedly.