@Assistable Team @Assistable Ai Is anyone else experiencing issues with the multi-calendar feature today? I set this up for a client yesterday and it worked perfectly with zero issues. Today, no matter what I try, it’s not working. Also, just to note — I’ve used this in my own system and set it up for other clients in the past with zero issues. I’m guessing this might be related to the new OpenAI 5.0 release, since I’ve never had issues with it before and the timing lines up exactly with the update. Here’s what I’ve already done: - Hard oath reset ✅ - Created a new calendar and deleted the old one ✅ - Verified calendar is active and slots display on the permanent link ✅ - Deleted and Re-synced calendars in Assistable ✅ - Created a new AI assistant from scratch ✅ - Deleted my contact and started fresh ✅ - Switched to GPT 40 ✅ The main calendar works perfectly fine — no issues there. The problem only happens when setting up a multi-calendar using the calendar ID and prompt. I even tested it on my personal account (which worked fine in the past) and it’s also not functioning now. I normally don’t reach out unless my team and I have exhausted every troubleshooting step possible. Let me know your thoughts or if there’s something else I should try. Thanks.

This is actually my first attempt at creating a bilingual, Spanish-speaking AI, and honestly, I think it sounds great. That said, I believe there’s still room for improvement in certain areas, especially towards the end when mentioning time. I was just testing things out since I’m currently helping someone with two clients from Spain. Also, I know the AI introduces itself as Emma and refers to itself as female even though its a male voice. I initially tested it with a female voice and later switched to a male one, just didn’t bother changing the name and stuff. lol

@Jorden Williams just welcomed a beautiful baby son into the world. Mom and baby are doing great. He’s taking time offline to be with his family, and we fully support that. If you need anything while he’s out: 👉 help.assistable.ai 💬 Pumble channel (if you haven’t it) Or tag @Assistable Ai, @Aidan Gage or myself. Please respect his space during this time. Do not expect any response from him. Thanks everyone.

The bot handles conversations well overall, but we’re really struggling with objection handling. For example, if someone replies with something like “I don’t feel like hopping on a call,” the bot usually just moves on or ends the conversation. (It often replies with: “Oh no problem – just come back if you feel like booking a call.”) It doesn’t really acknowledge or navigate the objection in a natural or effective way. We’d love for it to dig deeper and handle objections more assertively, in order to improve our call booking rate – ideally by exploring what’s holding the lead back or offering alternative next steps. Has anyone found a solid way to deal with this? Would really appreciate any examples, logic flows, or workaround tips you've found helpful. Thanks in advance! 🙏

We have some silver linings from the outages yesterday -- we were still able to take inbound calls and process calls with orbs. (I think outbound was fine too, but how would you have triggered them without GHL) So, even when the world was down; we were still taking calls. So, I just need to sync the calls from yesterday to GHL and our dashboard from the backup DB. I will look to do this tonight Also, im combing through everything today to ensure all is operational. Another thing, our front end and front-end DB was still up. I think yesterday makes a strong care for an in-house lite CRM for times like that. Fun stuff, happy friday all