Actions
Your server steers a call with an actions object. It can send one in three places:
The same actions work in all three:
Actions need an agent where jambonz runs speech-to-text, the language model and text-to-speech (a
cascaded voice pipeline) on jambonz 11.1.13 or later. On other agents
every action except end_call is refused.
The actions
One actions object can carry any of them. Studio applies them in the order of the table, whatever order you write
them in.
situation and resolve_situation
Start and resolve situations exactly as described in Starting situations from your server. Your server can start any situation, including one set to Only your server.
A resolve in a tool’s result waits until the model has answered that result. A resolve from a call event’s reply or a push reaches the agent at once.
update_instructions
Adds your own instructions to the agent’s prompt, under a heading of their own:
- Each
update_instructionsreplaces the previous one.""removes the block. - It never replaces the prompt you wrote in Studio, or a situation’s instructions.
- It stays through situation changes, and for the rest of the call.
Use it for something your system knows that changes how the agent should behave from now on. For a fact the model
should use once, inject_context is lighter.
inject_context
Adds a note to the conversation:
The model reads it on its next reply. It doesn’t make the agent speak: add generate_reply for that. The note stays
in the conversation history, so a later change to the instructions doesn’t erase it.
generate_reply
Makes the agent speak now, rather than waiting for the caller.
Without interrupt, a reply asked for while the agent is speaking or thinking waits until it has finished. If several
are waiting, only the newest is used.
On jambonz 11.1.13 the reply is spoken but isn’t shown as a turn in Calls. jambonz 11.1.14 and later show it as a turn.
transfer
Asks the agent to transfer the caller with its own transfer tool, so the transfer is checked and recorded exactly as
when the agent decides to transfer. The agent tells the caller briefly first. Text, or reason, tells the agent why.
transfer is refused when the agent has no transfer destination.
end_call
Ends the call. With text, or say, the agent says it in its own voice first, then hangs up. It works on every agent,
whatever its engine.
Limits
Actions from call-event replies and pushes are limited per call:
An action over a limit is refused. Actions in a tool’s result aren’t limited: the model already paces them.
Seeing what happened
Every action is recorded on the call’s timeline in Calls, with where it came from: the tool’s name, the event your server replied to, or a push from your server.
An action is refused when:
- the call has ended, or has been handed to another agent;
- the agent’s engine can’t take it;
- the agent has no situations (
situation,resolve_situation), or no transfer destination (transfer); - it is over a limit;
- the call’s connection to jambonz has closed.
A situation change that can’t apply, for example to a situation that isn’t active, shows as Refused to start or Refused to resolve, as for tool results.
Your server is never told that an action was refused. Check the call’s timeline.