Hey everyone, I’m having an issue where Assistable is tagging calls incorrectly when they go to voicemail. Even though the call clearly hits voicemail, Assistable is tagging it as answered / assistant hung up instead of a voicemail or no-answer outcome. I’ve reviewed my prompt and call logic but can’t figure out why voicemail calls are being classified this way. Is there a specific setting, call disposition rule, or voicemail detection method in Assistable that controls how these calls are tagged, or a best practice to make voicemail outcomes tag correctly every time? Any help would be appreciated — happy to share call IDs if needed. @Jorden Williams I also added my own custom tags but they aren’t being added either.

I keep trying to send calls manually from GHL to test, and it tells me the call was sent in execution logs, but the call doesn't actually get made.

Any meaningful upgrade comes with a moment of discomfort. V3 is one of those moments. To support what’s coming next, we had to migrate some core components earlier than planned. While this was the right decision for the long term, we know the timing has caused real frustration. If you’ve experienced call issues, delays, or unexpected behavior, we want to be clear from the start: We see it. We understand the impact. And we’re actively fixing it. Right now, there are three main things we want to acknowledge. First, there is a delay in the AI agent greeting on outbound calls, and this is affecting all outbound traffic. We know how important that first moment of a call is, and we agree that this experience is not where it should be. A fix for this is part of the upcoming patch and is being treated as a top priority. Second, some users are experiencing latency or connection issues. The majority of the platform is operating normally, but we already have a patch in progress that directly addresses these issues and will be rolling out shortly. Third, there is a busy signal issue affecting a small subset of numbers. We currently host over 14,000 phone numbers. Out of those, a few hundred are affected. If you’re one of them, your frustration is valid, even if the issue is isolated. Most of the impacted numbers fall into one of these categories: - Custom Telnyx setups that don’t align with our updated requirements - SIP trunking requests that were never completed - Older numbers still in the final stages of porting from Twilio to Telnyx If you’re affected, there are two paths forward. Option one: wait it out. For many numbers, this will be resolved automatically over the next few days as the patch and cleanup complete. Option two: move faster. You can purchase a new number and let our support team know. If your old number qualifies, we’ll credit your wallet for the entire year for the phone number ($30) for the trade-in. This option is there for anyone who can’t afford downtime.

One of my client was on vacation in Italy and when he called the bot, it sounded way worse on his end (it was fine on my end), does him being in Europe have anything to do with this?

After a phone call is made, there are tags that are automatically added to the contact on GHL Example: contact hangup or answered - none of these tags are part of the "add tag" section on assistable (displayed on image) What is the complete list of possible tags that the AI will add post-call?