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

### Answer It seems like you're encountering an issue where the parameters sent to your custom function are not capturing the full user query. This could be related to how the assistant interprets the user's intent and extracts parameters based on the conversation flow or specific triggers. To address this issue, ensure that your custom function's configuration is set to accurately capture and send the entire user input as parameters. This might involve reviewing the assistant's instruction or the system prompt configured for your assistant to ensure it's designed to capture the complete user input. Also, verify the custom function's parameters to ensure they're correctly defined to capture the required input. If your setup involves complex logic or conditional flows, consider simplifying the prompts or breaking down the task into more straightforward steps that the assistant can more easily manage. Additionally, revisiting the documentation on [Custom Functions]() and how to [define and use them]() might provide further insights or configurations you might have missed [(1)]() . Unfortunately, specific details or examples on addressing partial parameter capture directly from user input in custom functions beyond these suggestions are not available in the provided information sources. If the issue persists, it could be beneficial to review the conversation design or consider reaching out for more tailored support through the Vapi community or forums, where you might find others who have encountered and resolved similar challenges.