I am trying to monitor conversations for instances where the assistant says, "I'm having trouble with" usually in reference to accessing the calendar. I want to be able to detect the word "trouble" coming from the assistant and then send a slack notification to our team. Is there a way do do this?

Here is something we have been working on for voice. I had it working in chat but finial figured it out for voice. Now its time to take it to market. Updated Video: https://www.loom.com/share/ee61251a4e304edd9eaea5a50a513263?sid=185af94e-cca3-4e4e-9629-7d271254e9a3

Name: calculate_distance Description: Use this tool to calculate the distance between your address and the user's address. URL: https://8bndej.buildship.run/calculate-distance Parameters (2 parameters): Name (lowercase): origin Description: Your address which is (PUT IN YOUR OFFICE ADDRESS HERE). Name (lowercase): destination Description: The user's full address.

So, took some time to patch some stuff to get you more insight, check it out here to get more visibility into your deployment and further insights- Voice mins insights - Added call time in ms, seconds and minutes (2 decimal places) - call end resons, and recording all in the same interface to check call timeframes and what happened Mins - To save voice mins, turn off voicemail - sometimes, from call reviews, we notice the time to listen to and leave a voicemail can be 18 - 60 seconds. May not sound like a lot but if you are making 1000s of calls that adds up End reason - Earlier I had noted that error doesn't always mean error, this patch should give you more insights like and error meaning a call was made but there was no answer / voicemail (couldve been full), you can see those reasons there Outbound not working triage guide - If you aren't able to outbound calls, check voice mins - check the wf action to see if it has an assistant id, check your assistant has a phone number, check call logs - could be: - the contact you called doesn't have a number / bad number (will show in call logs) - significantly negative mins - system rejects call, can be seen in the returned_an_error from the WF action, will not show in call logs because no call was made, tag will also be added to the contact ^^ couple triage steps but ill add a guide and more visibility into that stuff in patches and in new update

So, I wake up - (fell asleep at my desk) to the world on fire. The first thing I do is throw money at every single service that we have, after looking at logs - GHL is taking over 2 minutes for some calls to get us back data... its timing out. Not sure if this is for all GHL endpoints but this one stood out Since blame always tends to get thrown our way, I figured we can share frustration as we wait over 3 minutes together for GHL to Get Contact - tried this on 3 different services, postman, buildship, requests and more. Im building an internal contact structure so that we can bypass gohighlevel entirely when processing calls / messages and treat it more as an integration so we dont have to worry about things like this... -- on it now, put in tickets with ghl if you have time - im oging to do the same pls send redbull