----------------------------- **While I generate an answer, here are some sources that might be helpful**: * [Function Calling]() * [Outbound Sales Example]() * [Prompting Guide]() * [Server Events]() -----------------------------

### Answer For ensuring that the booking date and time get submitted accurately through functions, it's crucial to design your prompt with clear instructions that guide the language model on how and when to call the function. Incorporating a custom function for booking appointments into your assistant's configuration can significantly enhance the efficiency of handling date and time parameters. Here's an example based on the documentation:

json
{
  "functions": [
    {
      "name": "bookAppointment",
      "description": "Used to book the appointment.",
      "parameters": {
        "type": "object",
        "properties": {
          "datetime": {
            "type": "string",
            "description": "The date and time of the appointment in ISO format."
          }
        }
      }
    }
  ]
}

[(1)]() This function definition tells the assistant to use the

bookAppointment

function during a conversation. To accurately capture and submit booking dates and times, your system prompt should clearly instruct the assistant on gathering this information from the user and using it to call the

bookAppointment

function at the appropriate moment. Remember to define your

serverUrl

where Vapi can send the function call information, as this will enable the actual booking action on your backend.

json
"serverUrl": "YOUR_SERVER_URL_HERE"

Adjusting the conversational flow within the prompt can significantly improve the accuracy of date and time submissions. Ensure the assistant asks for the date and time explicitly and waits for the user's response before proceeding to call the function. For a more detailed setup and examples, you might want to explore the [Function Calling]() section in the Vapi documentation.

Got it. Tagging @User for additional help.

ccdd0417-3610-4d42-94c9-1eb2098968f6

94743eed-e141-4a04-a3c1-1dc0b6b866ff

i used "tomorrow" when i said it to the bot, it put in a date in 2023, any recommendations for that

otherwise i think we got it

lmk if you need help with something else