Call Forward is a bit trigger-happy
# support
v
The call forward function seems to call halfway through a generated answer. For example we'll tell the LLM (GPT-4o) to transfer after providing some basic steps and clarification. It will start generating an answer and then randomly say "Forwarding your call", is there a way to fine-tune control over the function? We've tried like 100 variations of prompts to get it to wait until the whole answer is complete and be more smooth when transitioning to a transfer but it seems really trigger-happy and forwards the call halfway through answers usually.
v
@Vauld I understand the issue you're facing with the call forwarding function activating prematurely. To ensure a smoother transition, we can look into adjusting the conditions that trigger the call forwarding to make sure it only happens after the completion of the answer. Could you provide me with more details on the conditions or triggers you're currently using for the call forwarding? This will help me assist you better in fine-tuning the control over the function.
You can continue this conversation by mentioning me in the message.
v
NOTE: if the caller persists and requests to speak to a person/maintenance MULTIPLE times then you may transfer their call. Otherwise, follow the standard procedure. You must follow the above guidelines, do not mention anything outside the provided guidelines, do not veer off the provided steps.
Our prompt is gigantic but that's the part specific to getting in touch with the person on the forward-line
@Vapi
v
@Vauld Thank you for providing the specific guideline regarding call transfers. It seems that the call forwarding function should only be triggered when the caller explicitly requests to speak to a person or maintenance multiple times. To ensure the function waits until the whole answer is complete, we can implement a check that counts the number of times a caller makes the request before activating the call forward. If you're able to modify the logic or the script that handles the call forwarding, you could add a counter that increments each time the caller makes the request. The call would then only be forwarded after the counter exceeds a certain threshold, which you've indicated should be multiple requests. If you need assistance with writing or adjusting the script, please provide me with the current script or logic you're using, and I can help you with the necessary modifications.
v
Well that's the issue is that the entire script for call forwarding is handled on the Vapi back-end, we're just using the out of the box function.
@Vapi
v
@Vauld I see, if the call forwarding script is handled entirely on the VAPI backend and you're using the out-of-the-box function, it sounds like you might need to reach out to the VAPI support team to request a customization or an update to the function to better suit your needs. Since the function is not behaving as expected and you've tried various prompts without success, the next step would be to communicate with the VAPI support team to explain the issue and see if they can provide a solution that allows for more granular control over the call forwarding trigger. Would you like me to guide you on how to reach out to VAPI support or assist you with any other information that might help in resolving this issue?
v
Yes @Vapi
v
@Vauld Great! To reach out to VAPI support, you'll want to follow these steps: 1. **Gather Information**: Before contacting support, make sure you have all relevant information on hand. This includes your account details, a clear description of the issue, any error messages you've received, and examples of when the call forwarding function triggered prematurely. 2. **Contact Support**: Use the contact method provided by VAPI, which could be through their support portal, email, or a dedicated support phone number. 3. **Explain the Issue**: Clearly explain the problem you're facing with the call forwarding function. Mention that you've tried various prompts and that the function is still triggering too early, interrupting the generated answers. 4. **Request Assistance**: Ask for guidance on how to adjust the call forwarding trigger to wait until the entire answer is complete or how to implement a counter for multiple requests as per your guidelines. 5. **Follow Up**: If you don't receive a response within a reasonable time frame, or if the initial response doesn't resolve your issue, don't hesitate to follow up for further assistance. Remember to be as detailed as possible when describing the issue to ensure that the support team can provide the most effective assistance. If you have any other questions or need further help with this process, please let me know!
v
@Shubham Bajaj
s
@Vauld please share the call id.
v
@Shubham Bajaj 89bf9deb-7c76-4868-861d-c5c2f795a1d1
It starts generating then cuts it off
Anything in the prompt I can do to ensure it finishes its sentence before it decides to call the transfercall function?
Or this one, it has a much simpler prompt but same problem: 02e123f8-78af-4332-acd0-19b8a6355d76
s
Sorry for the delay, are you still facing this issue? @Vauld
v
Hey @Sahil Yes, it's still cutting off halfway through the generated response and transferring the call
It's not everytime, but it does it frequently enough that it's causing problems
s
Sent you calendly link we can discuss over there