OneAI <> Warranty First: Tech working session

Date: 2025-12-15 | Duration: 59.59000015258789 min | Account: warranty-first

External attendees: leo.nelson@warrantyfirst.co.uk, matthew.abdy@freemanclarke.co.uk

Summary

The team discussed a targeted controlled go-live for AI integration during the week of January 5th, with a pre-launch meeting to confirm readiness involving key stakeholders like Leo Nelson, Charlie, and Graham Edgar. They emphasized careful preparation to engage the call center effectively amid holiday closures, avoiding a rushed pilot before Christmas. Testing is planned with a small pilot on 100 contacts, focusing on qualified leads through a phased approach. The trigger strategy includes calls initiated after SMS and email engagement, while the call script is being developed to ensure clarity and legal compliance. The importance of communicating AI’s role as a support tool to the sales team was highlighted to foster acceptance, and operational readiness, including HubSpot updates, was prioritized for a smooth launch.

Key Points

📅 Go-live Date: Targeting controlled go-live week of January 5th with pre-launch meeting to confirm readiness. 🧪 Testing Plan: Initial testing likely postponed to January; small pilot will test with 100 contacts for feedback. 📈 Trigger Strategy: First trigger initiates calls five minutes after SMS; second trigger follows email opens, depending on initial results. 📝 Call Script Development: Script personalized with vehicle registration; legal language adjusted to ensure clarity without using ‘warranty’. 🤝 Team Engagement: Clear communication on AI’s role as a support tool; demos planned to reassure staff and gather feedback. 🔧 Operational Readiness: HubSpot permission updates and monitoring call volumes are priorities to ensure a smooth launch process.

Overview

  • Go-live Date: Targeting controlled go-live week of January 5th with pre-launch meeting to confirm readiness.
  • Testing Plan: Initial testing likely postponed to January; small pilot will test with 100 contacts for feedback.
  • Trigger Strategy: First trigger initiates calls five minutes after SMS; second trigger follows email opens, depending on initial results.
  • Call Script Development: Script personalized with vehicle registration; legal language adjusted to ensure clarity without using “warranty.”
  • Team Engagement: Clear communication on AI’s role as a support tool; demos planned to reassure staff and gather feedback.
  • Operational Readiness: HubSpot permission updates and monitoring call volumes are priorities to ensure a smooth launch process.

Action Items

Leo Nelson Provide feedback on the shortened call script by Tuesday or Wednesday before Christmas (48:05) Include Graham Edgar and relevant sales team members in upcoming demo and go-live preparation meetings (44:40) Arrange internal communication and training with sales team to ensure AI integration is positively received (04:10)

Michael Gur Copy his HubSpot call permissions to Leo Nelson’s account after the meeting (57:40) Manage the setup and testing of separate AI call workflow triggered post SMS, avoiding integration into main workflow until final testing is complete (54:58)

Daniella Block Share the shortened script document with Leo Nelson for review (40:30) Schedule next optimization meeting with Matt and OneAI team before Christmas (48:20) Schedule pre go-live meeting for Monday, 5th January 2024, including Warranty First and OneAI stakeholders (49:40)

Yochai Levi Coordinate initial short test runs targeting calls 5 minutes after SMS to collect qualified leads and gather insights for further trigger refinements (30:20)

Leo Nelson & OneAI Continue discussions to define and implement handling for calls connecting to dealers instead of end customers, improving contact accuracy (36:30)