Your first PrismVox call

Start with one test caller and one transfer destination. Validate each link in the chain before attaching a production number or enabling additional tools.

1. Check the service overview

Overview should show database and embeddings readiness and a registered SIP trunk. Speech marked configured means settings are present; use a preview and a call to verify the provider really accepts them. A registered trunk alone does not prove the audio path works.

2. Give the receptionist a focused role

In Configuration → Agent, set a short inbound persona and greeting in the call language. State what the receptionist may answer and when to transfer or take a message. Keep transfer instructions consistent with the directory; put factual opening hours or procedures in Knowledge. Save the form.

You are the receptionist for Example Workshop.
Answer briefly in English using the approved knowledge base.
If information is missing, ask one question and wait.
Transfer only when the caller asks; otherwise offer to take a message.

3. Add a small reference document

Create a Knowledge collection and upload a short, non-sensitive text with test opening hours and contact instructions. Enable knowledge search in Agent settings. Ask one question whose answer is in the document and one whose answer is absent; the agent should acknowledge the missing information.

4. Preview and call

Use Listen to check the selected synthesis voice. Then call your SIP number from an authorized test handset. Confirm you hear the greeting, recognition captures your question, a response arrives, and the call appears in Call Logs/Conversations. Preview requests and real calls may consume paid provider usage.

5. Verify real call actions

• Ask to leave a message, supply the details, then confirm it appears in call/conversation history.
• Add a test contact in Directory, choose blind or attended transfer, and test with a consenting recipient. For attended transfer, test both acceptance and refusal.
• Say goodbye and verify the agent actually ends the call. A spoken farewell without a hang-up tool call is not sufficient.
• Interrupt a longer reply and check that playback stops without repeated false interruptions from echo.

6. Try one outbound mission

In Outbound Calls, use a consenting test number and a precise mission, then inspect status, attempts and outcome. Keep the number and mission fictional in screenshots or shared logs. Only widen access after the basic call path and actions work.