Gloves off post: I’m going to start by saying I’ve been a fan of Assistable since day one and I’ve been here for 2 years. However this video does not make up for the last 3 months of issues. I’ve lost over 10k MRR and would have lost all of my inbound clients as well had I not moved them over to another provider. I urge you to consider leaving this comment up because your first instinct will be to delete it. You have to fix your redundancy issues with your platform. This isn’t fun and giggles. Live real businesses depend on this product and if it didn’t come from my own personal free months or discounted rates, I would have lost my entire business because of the mismanagement of this software. If something is broken you have to have fail safes in place. You don’t, as much as you think you do, you don’t. We are just going to sit back and feel fine with the fact that out of the blue the Ai randomly decided to switch to crappy robotic voices, hallucinate like nobody’s business and stop selling hello when an inbound call comes in? This is so incredibly unprofessional. And you’re still having issues with call recording links coming through? Jordan you need a kill switch, when the Ai fails. You do the right thing, and flip the Ai over to a phone number that the client provides that will send them the call. And you do this every single time you have a non working platform. You NOTIFY your clients (US!) that things are broken. These are basic MUST have things to get done to survive anything for the future. Your support team is not trained enough and I have a ticket with them going almost every single day and it leads back to deferring it back to you and we never get responses back when it’s sent to Jordan. I know you’re busy, you’ve got your baby. I’ve got a baby. And I know your goal is to take you out of the puzzle and let operations run themselves. It’s smart but your team is not equipped. Your money must be reinvested into your business for redundancy and uptime that you promise us. I’m sorry man, compensation of a phone number for a year doesn’t cut it. I’ve had to buy 3 different phone numbers for all my clients and still can’t get things to fix.

@Anthony Castiglia sorry to hear this! It would help to know when things will actually be fixed, hopefully we get some sort of communication soon.

@Alexa Briggs I haven’t heard anything. Today we created brand new agents and imported over the workflows and that seemed to help, so it’s almost like starting fresh with the same prompts and it seemed to help a bit but still getting really discouraged on the lack of communication regarding this issue and implementation to fix the issue.

Same thing happened to me, casually lost like $600 in the matter of like 40 minutes. Someone already advised the captcha is important. We blocked all foreign numbers. We will only be working with US clients anyway. We’ve seen they have tried to do it again but thankfully they are getting blocked before it happens. Why they do it. So there are companies that make money on the exchange rate. So part of what we pay with our Ai minutes goes to an exchange company. They make their money by international calls, we are talking fractions of pennies. So by forcing it they make their money from volume of calls on wasted minutes. I recommend you update your prompt to to recognize that call to disconnect it. We recorded their very smart recording and called our Ai and were able to also come up with a prompt to identify it and immediately disconnect the call. So we fake spammed our Ai with the same recording and now it’s trained to disconnect. Hopefully this helps!

@Jan Schevenels how did they solve it/what did they do?

What sort of data? You can build within the Knowledge Base, as well as some stuff we have custom built with Make or Buildship,

@Melanie Cibura your best bet is to build it with Make. I’ve found custom object within GHL using Assistable can be unreliable with giving correct information, especially if it’s on a phone call.