Activity
Mon
Wed
Fri
Sun
Jan
Feb
Mar
Apr
May
Jun
Jul
Aug
Sep
Oct
Nov
Dec
What is this?
Less
More
Memberships
131 contributions to Assistable.ai
Oct 6 •
HD Numbers | Call Quality
Who all is experiencing choppy and bad audio quality when using the new "HD" numbers? This has been an issue for us since they rolled out. The other day, I tested a SIP'd number and it was perfect, no audio issues at all. We have changed voices, voice engines, prompting, everything...issue still remains.
0 likes • Oct 13
@Shane Evans https://help.assistable.ai/voice-ai/how-to-import-telnyx-numbers
0 likes • 4d
@Michael Og Here is the updated doc- Importing Telnyx Numbers | Assistable.ai https://share.google/o62UShfm6vtQGhDPl
7d •
Telnyx Inbound
I’ve seen several people post about having issues with inbound not working. What was the fix? I submitted ticket to support days ago. Obviously there is a step or something missing in the setup docs for close to a dozen people to be having this same issue. Not sure why the response to all the posts have been “contact support” instead of just posting the solution. Thanks.
1 like • 6d
Hey Michael thanks for calling this out, and I appreciate your patience here. I just went ahead and updated the documentation and clearly highlighted the exact areas where inbound can fail. In most of the recent cases, the root cause has been the number format in the inbound settings. If inbound isn’t working, please double-check that your number is set in +E.164 format. When this isn’t set correctly, inbound will fail even if everything else looks right. You should now also see this clearly mentioned in the updated docs. If you still face issues after that, feel free to tag me here and I’ll take a closer look right away. Thanks again for helping us improve the experience for everyone. Updated Doc- https://help.assistable.ai/voice-ai/importing-telnyx-numbers
9d •
How to Use Automatic Data Extraction?
Hey lovely community! A few of you were asking about how to reliably extract any required information from users while the AI is actively having a conversation beyond just basic name, email, and phone. While we already have tools for standard fields, the most powerful and reliable approach for advanced, custom, or business-specific data collection is using Automatic Data Extraction (Map Custom Fields) instead of Extraction Tools. Here's the guide on how to do it- https://help.assistable.ai/how-to/how-to-gather-and-extract-important-user-information-using-automatic-data-extraction @Ryan B hope you find this useful. This directly solves the data capture reliability issue you were facing
1 like • 9d
@Brandon Duncan Hey Brandon, Yep, this works for both Voice and Chat. For Name & Phone, while Automatic Extraction can pull them, we usually recommend using the “Update User Details” tool it's more reliable for core identity info. For business-specific data like Budget, MRR, or Needs, Automatic Extraction is the way to go. How it works: - Voice & Chat Support: Runs on a “Per Run” basis for Chat and a “Post-Call” event for Voice, meaning zero latency during live conversations. - Best Practice: Use Automatic Extraction for business-specific conversational data. Use the Update User Details tool for locking in contact name/number.
0 likes • 7d
@Jace Nelson @James Carter it should be fixed, Jorden patched it a while back!
21d •
Is this the best the Ai Assistant can do?
For a client I set up an ai receptionist. But IMO the performance is pretty poor. Bad enough that most customers will be frustrated with it. She can't get the email correct even though it was spelled out a couple times, then she muffs the street name, and reads the address number like it's math class. Is this the best we can expect? Or what can be done here? Also, why does she sometimes run sentences together without pausing? Thanks for any tips! See call attached.
0 likes • 9d
@Bernie White Sure Bernie, I'll create guide on it 👍
0 likes • 9d
@Bernie White @Ryan B Here is the guide to it- https://help.assistable.ai/how-to/how-to-gather-and-extract-important-user-information-using-automatic-data-extraction
Jul 16 •
SOLVED: ⚠️ "Client ID not found" on INBOUND calls with NETGSM
When Netgsm Turkey number is connected to my assistant on an inbound call, AI can't refer with first name although prompted, and can't book an appointment. But when we switch to Twilio number, it all works perfect. @Jorden Williams can you identify the root cause of this weird error so I can have Netgsm fix whatever they need to fix to get it working? Loom is in my most recent support ticket. This is crucial to my business as currently I can't offer inbound assistants until we fix the issue. Thank you for your help!
0 likes • 16d
@Cemre Sancaktar You're very welcome, Cemre. I'm glad that getting the country code field enabled/added on the NETGSM platform was the final piece needed!
1-10 of 131
@prathap-balamurugan-9582
Assistable Skool Group Moderator & Support Team Member | AI Agent Builder | Expert in Assistable AI & GoHighLevel | Helping members through support.
Active 24m ago
Joined Aug 14, 2025
Powered by