Hey folks! Does anybody have a video or tutorial on how to start an AI SMS conversation with the client if your AI outbound call lands in voice mail, isn't answered or fails for any reason?

Let me learn you something fellow assistacrats... So, I see a ton of carrier rejected and people sometimes having a hard time landing as they ramp their calling deployments. I've included a 7 minute loom explaining some resources and the root cause analysis behind these error that you see and how to avoid them. This is only going to get tougher! become an expert. we will help as much as we can with useful warming programs and verification modals but knowing these nitty-gritty things makes you dangerous in the world of AI calling (because most dont care to look into it). Loom: https://www.loom.com/share/401e176582154ecca7c21b03eaea2d78?sid=f8cd1f4d-003c-4e89-9369-03b91afbfd25 Why are my calls failing? When I look at your public logs from the telephony provider (twilio, telnyx, etc), i see error 608 and 603 (read the article here) which indicates the number you are calling from is getting rejected by the contact's service provider from poor number reputation. It is a compounding telehpony-side error, meaning the more you see it, the more it impacts the numbers ability to make calls. What can be done about it? - Register your numbers at https://freecallerregistry.com/fcr/. Use all the verification services available - its FREE. - We recommend SIP trunking. Why? You have more control over business profiles, caller IDs, shaken/stir, etc. Very useful when swapping numbers. - You own them - they are yours and interchangeable with GHL :) - Use a number pool to rotate your numbers. - Warm your numbers (like you would an email) but slowly ramping volume and focusing on the most warm leads you have to get your metrics up (like answered, sentiment, etc). What do the new metrics mean in the number portal? - Telephony Status: The HIYA spam rating status - uncertain is good bc that means that there is no historical or suspected spam for your number. - Verification: Are you verified at https://freecallerregistry.com/fcr/? - Caller ID: what is the contact seeing when you call them?

I thought I would come on here and add some clarity to call dispositioning. This is not necessarily an error but can be a sign of an error for importing or spam detection. If you are getting carrier rejected, this is a failure on the telephony side. Codes dial failed, dial no answer and dial busy are non-optimal outcomes (of course we want a phone call answered) but it doesn't mean its an error. Imported numbers: - This is coming from termination (aka outbound - you can test this theory by calling inbound then trying a call outbound, if inbound works but not outbound, you trunk is misconfigured) - Could be caused by your CPS being too low. You will have to increase your own calls per second via the telephony provider if you are doing higher volume. - If dial failed, check your termination settings. - The number you are using is being marked as spam by carrier -- just the luck of the draw with telephony providers. Try another number and warm it before making calls. Platform numbers: - Check the reputation via 3rd party or register it -- could be marked as spam by carrier -- just the luck of the draw with telephony providers. Try another number and warm it before making calls. - If dial failed make sure your oauth is correct, if oauth is not current we will not be able to get the contacts number - If dial no answer, it could be as simple as you dialed and they did not answer (or have VM) Triage points: - check your termination (its the only thing it could be) if imported, make sure If you are using credentials they are correct and make sure if you are not using credentials to not have that option checked - Check the number for spam ratings and detection, tons of 3rd parties do this for free - Make sure you are calling US only if using platform numbers, we do not offer international calling with platform numbers, international calling is done via imported numbers - Make sure your trunk has geo permissions enabled - Test if its number agnostic, assistant agnostic or recipient agnostic

Hey all. I'm trying to put together an outbound calling AI assistant. It received an inbound call just fine, but during the attempt to outbound (by adding the lead to the Outbound Workflow), I got this error. Have anybody gotten this error? Any insights on how to fix it? Thanks!

Video attached PDF attached