A voice agent answering the phone does the same jobs a chat agent does: book, reschedule, check an order, change an account. The caller speaks instead of typing, but the job underneath is identical.
So the jobs compile the same way. The conversation happens out loud; the lookups and the write behind it are the ones your agent already repeats in chat.
Why it matters more on the phone
On a call, every model call is something the caller waits through. When the repeated jobs don't need your agent's model, there are fewer of those waits, and your agent's attention goes to the calls that need it.
Everything else about the call stays yours: your voice stack, your model and your prompts.
The same jobs, out loud
Listen to a day of calls to a booking line and you hear the same handful of jobs: book a table, move a booking, cancel one, check what's on file. Callers ramble, interrupt and change their minds, and your voice stack handles all of that. Underneath the speech, the job is a lookup and a write, exactly as in chat.
Without AgentCompile
- Every turn of the call waits on your agent's model.
- Routine bookings get the same deliberation as hard ones.
- Your agent's capacity is spent evenly across easy and hard calls.
With AgentCompile
- Known jobs run compiled, so the caller waits through fewer model calls.
- Routine bookings follow the same proven steps every time.
- Your agent's model is kept for the calls that need it.
A reschedule, walked through
- The caller says they need to move Thursday's appointment.
- The job is known: find the caller, find the appointment, find the open times.
- The new time is read back, and the caller confirms before anything changes.
- If the caller asks something nobody planned for, the call goes to your agent, with everything said so far.
What stays yours
- Your speech recognition and your voice.
- Your model and your prompts, for everything that isn't a known job.
- Your rules for what needs a yes before it happens.