You are filtering too early, and it is costing you prospects. A visible consent checkbox on a contact form is not the test. Plenty of good businesses collect consent properly through a lead form, a quote funnel, a Facebook lead ad (Meta collects consent at form level), or their booking system, and none of that shows on the website you are looking at. Prospect on the signal that they have leads at all: running Google or Meta ads, a lead form of any kind, a sales team. Then establish consent on the coffee date, which is where it belongs anyway. Ask how the list was built, when the leads came in, what they ticked or agreed to, and whether they have ever texted them before. Ads and website forms are usually fine. Referrals and walk-ins are dicey. Bought lists are a hard no. If the answers are shaky, you can still run the campaign on the recent, clearly opted-in slice of the database rather than walking away from the deal.

Don't host the video file in HighLevel at all. Upload it to YouTube (unlisted) or Vimeo, then embed that on your page. It's faster to load, it won't break on mobile, and it sidesteps whatever the media library is choking on. Every case study page we run is done this way. If you must host it directly, two things usually cause the rejection: the file is too big (compress it, 1080p at a sensible bitrate, aim well under a couple of hundred MB), or it's in a format the media library won't take (export as MP4, H.264). Re-export through Handbrake and try again. Quickest test: upload it to YouTube now, drop the embed in a video element, and see if the page renders. If it does, the video was the problem, not your site code.

The "no" almost certainly happened before the missed-calls bit. Two things usually fix this: 1. Stop arguing the point, make him count it. Don't tell him he's losing buyers, ask "roughly how many calls come in after 6pm and at weekends, and what happens to them now?" If he says "not many", fine, you've qualified out honestly. If he pauses, he's just sold himself. You cannot argue someone into a number they haven't said out loud. 2. Lead with the outcome he cares about, not the receptionist. A dealer buys test drives booked and service slots filled. "AI receptionist" sounds like a cost to him. Also, don't close for the sale on a cold call. Close for a short call where you show him a live demo. Sales Wingman is what we demo from now, and its Revenue Rescue calculator does exactly this missed-call maths on screen. Lite is free on a paid HighLevel plan under Dan's link. Worth watching how Dan handles the objections live: https://www.youtube.com/watch?v=UV6qcDOtLx0

Rough rule: 1,000 old leads is the sensible floor for a paid DB reactivation, and 2,000+ is where it comfortably pays for both of you. Below about 500 the maths gets thin, because you are working off the same reply-to-booking rates on a much smaller base and one bad list wipes the result. But size is only half of it. What matters more: 1. Age and source. 5,000 scraped contacts is worse than 800 people who genuinely enquired. 2. Consent. They must have opted in with that business, or you should not be texting them. 3. Deal value. 400 dead mortgage or solar leads at £3k commission each is a great campaign. 4,000 dead £30 leads is not. So run value per booked appointment times a realistic booking rate, and if that does not clear your fee plus about $130 of send cost per 2,000 leads, the list is too small. Small lists are still useful as a first client. Do it cheap, get the case study, then go after the bigger databases with proof.

@Rohan S Yes. Thats what the data processing agreement is for. Thats where they sign that their list has fully consented and they are liable for this. It just gives you a bit of add piece of mind. But the consent is on them

Two ways it happens in practice, and the simpler one is what we teach first. **1. Calendar link (the default in the Prince Charming snapshot)** Once the lead is qualified, the AI sends your Calendar Link custom value. That link is a HighLevel calendar connected two-way to the advisor's Google or Outlook calendar. Availability comes from their real calendar, so anything already blocked never shows as free. The lead picks a slot, it writes straight into the advisor's calendar and fires the Appointment Booked workflow. No human involved. **2. AI books directly** The bot asks for a time, checks free slots via the calendar API, then creates the appointment itself. More natural, more to build and more to break. Start with option 1. Out of hours is the whole point. The calendar only offers slots inside the availability the advisor sets, so a 2am enquiry books a 10am Tuesday slot. Set working hours, buffers, minimum notice and max per day on the calendar itself. Practical bits: use round robin if there are several advisors, connect the advisor's calendar two-way or you will get double bookings, and set a reminder sequence off the Appointment Booked workflow. Walkthrough here: https://www.youtube.com/watch?v=2gC3orMEgto