pub struct UpdateTransferCallToolDto {
pub messages: Option<Vec<CreateDtmfToolDtoMessagesInner>>,
pub destinations: Option<Vec<CreateTransferCallToolDtoDestinationsInner>>,
pub function: Option<OpenAiFunction>,
}
Fields§
§messages: Option<Vec<CreateDtmfToolDtoMessagesInner>>
These are the messages that will be spoken to the user as the tool is running. For some tools, this is auto-filled based on special fields like tool.destinations
. For others like the function tool, these can be custom configured.
destinations: Option<Vec<CreateTransferCallToolDtoDestinationsInner>>
These are the destinations that the call can be transferred to. If no destinations are provided, server.url will be used to get the transfer destination once the tool is called.
function: Option<OpenAiFunction>
This is the function definition of the tool. For endCall
, transferCall
, and dtmf
tools, this is auto-filled based on tool-specific fields like tool.destinations
. But, even in those cases, you can provide a custom function definition for advanced use cases. An example of an advanced use case is if you want to customize the message that’s spoken for endCall
tool. You can specify a function where it returns an argument "reason". Then, in messages
array, you can have many "request-complete" messages. One of these messages will be triggered if the messages[].conditions
matches the "reason" argument.
Implementations§
Source§impl UpdateTransferCallToolDto
impl UpdateTransferCallToolDto
pub fn new() -> UpdateTransferCallToolDto
Trait Implementations§
Source§impl Clone for UpdateTransferCallToolDto
impl Clone for UpdateTransferCallToolDto
Source§fn clone(&self) -> UpdateTransferCallToolDto
fn clone(&self) -> UpdateTransferCallToolDto
1.0.0 · Source§const fn clone_from(&mut self, source: &Self)
const fn clone_from(&mut self, source: &Self)
source
. Read more