GPT-Live quickstart
GPT-Live quickstart
This quickstart creates a simple front-desk assistant and makes a browser call to it. It needs no server of your own. It uses one built-in tool, endCall, so you can see a delegation happen and find it in the call record.
Before you start
- GPT-Live enabled for your Vapi organization. See access.
- A browser with a microphone.
- For the API path, a Vapi private API key.
- If you use your own OpenAI API key, it needs access to GPT-Live and to the reasoner model. This quickstart uses the default,
gpt-5.6-terra.
Create the assistant
The assistant answers for Example Service Studio, a fictional business. It greets the caller, asks for their name and reason for calling, and ends the call when they’re done. It has two prompts: the speaker prompt shapes the conversation, and the reasoner prompt handles tasks, which here is only ending the call.
Dashboard
API
Create an assistant
Open Assistants and select Create Assistant. This creates a new Classic assistant.
Talk to it
Open the assistant in the dashboard and select Talk. Allow microphone access. Try these, one at a time:
- Give several details at once. “Hi, it’s Sam, I’m calling about moving my appointment.” The assistant should use both and not ask for your name again.
- Interrupt it. Start speaking while it’s talking. It should stop and listen.
- Change the pace. “Could you slow down a little?” It should adjust.
- Say goodbye. “Thanks, that’s everything. Bye.” The call should end.
The greeting and replies are generated, so the wording varies from call to call and may not match your first message exactly. The assistant may also be cut off before it finishes saying goodbye, because ending the call is an action that happens as soon as the reasoner takes it.
Check what happened
Open the call in Call Logs. You’ll find:
- The transcript of both sides of the conversation.
- The recording, if recording is enabled.
- An
endCalltool call in the call’s messages. This is the reasoner acting on the speaker’s delegation. - The ended reason, which shows that the assistant ended the call.
That endCall entry is the thing to look for. The assistant saying “goodbye” and the call actually ending are separate events, so check for the action as well as the words.
If the call didn’t end
If the assistant said goodbye but the call stayed open, look in the call’s messages for an endCall tool call:
- No
endCallentry. The speaker may not have delegated, or the reasoner may not have called the tool. Check that the speaker prompt lists ending the call as a delegation trigger, the reasoner prompt says to callendCall, and the tool is attached. Delegation is a model decision, so try a few calls. - An
endCallentry is there. The delegation happened, so look at the tool’s result for an error.
See the troubleshooting guide for more checks.
Next steps
- Design conversations: how to shape a conversation that reaches the caller’s goal while work runs in the background.
- Build with tools: connect your service so the assistant can look things up and take actions.
- Migrate to GPT-Live: move an existing assistant.