@ImFeelingSick
It sounds like there may be an issue with the state management in your VAPI application. To ensure that the system waits for the current caller to provide their account number before sending it to the Make webhook, you should implement a clear sequence of events that includes collecting the account number as part of the current call flow.
Here's a general approach to resolve this issue:
1. **Reset State**: At the beginning of each call, make sure to reset or clear any previous state, including the account number from the previous call. This ensures that the system does not use stale data.
2. **Prompt for Account Number**: When the caller requests to create a ticket, the system should prompt the caller to provide their account number.
3. **Collect Account Number**: Use a mechanism to collect the account number from the caller. This could be through voice recognition or DTMF tones (keypad input).
4. **Validate Input**: Once the account number is collected, validate the input to ensure it's in the correct format and is a valid account number.
5. **Send to Webhook**: Only after successful validation should the system send the account number to the Make webhook for further processing.
6. **Confirmation**: After the webhook processing, provide confirmation to the caller that their ticket has been created.
If you're using a stateful system, ensure that the state is updated at each step to reflect the current progress of the call. This will prevent the system from sending the account number prematurely.
If you're still experiencing issues, please provide more details about your current setup, including the logic flow and any code snippets, so that I can assist you more effectively. If this is not something you can resolve on your own, you may need to ask support for more info on this.