boost keywords not working
# support
p
hi im setting boost keywords for my agent and have tried intensifyers from 1 to 10 and it doesnt seem to work .
v
Hi @Papi, I'm an AI assistant for Vapi. I'll analyze available sources and get back to you shortly.
----------------------------- **While I generate an answer, here are some sources that might be helpful**: * [Inbound Calling]() * [Web Calling]() * [Outbound Calling]() * [Dashboard]() -----------------------------
### Answer It seems like you're dealing with an issue related to boosting keywords in your agent's transcriber settings. One common issue could be the format or integration of the boost values. To properly set the keyword boost, you need to specify the keyword along with its boost factor in the format
"keyword:boost_factor"
. Here's an example of how you might set this in your API call:
Copy code
json
{
  "transcriber": {
    "keywords": ["example_keyword:10"]
  }
}
[(1)]() If you're still facing issues after ensuring the correct format and integration, it might be helpful to review the specific transcriber documentation or the error messages you're receiving to identify any additional requirements or constraints.
p
here is my assitant id : de3c297d-5b83-465c-9c7b-955d80182ae5
v
Got it. Tagging @User for additional help.
p
i have a feeling even though this is exposed in the api it's not implmented have tried everything . 😦
s
Use keywords boost 1 value only which is more than sufficient also it is being used on our homepage. So, there is no issue with it
p
not working tho.
s
Can you send me any latest call_id?
p
ddad2bef-bf7a-4fa0-abf7-f31644cea84a
s
Can you also provide me the timestamp or exact word which was not captured properly?
p
The word was convolinx .
ah it seems the recording is gone . let me test again
ac3a15be-3e3b-436c-816f-9cf7bf426250 0:12
@Sahil
s
can you increase the value:10 to something and then give it a try
i
is this resolved? we have the same issue
k
This should be working, but if you are encountering issues with it recently please provide a call id where the issue occurs and we will take a look at it
3 Views