WarrantyFirst <> OneAI: Hold for optimization meeting

Date: 2025-12-11 | Duration: 48.290000915527344 min | Account: warranty-first

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

Summary

The team convened to finalize key data field mappings between One AI’s system and HubSpot, ensuring accurate call scripting and backend integration. They identified missing elements, such as the average repair cost, which Charlie Whiston suggested to use a default value of just under £1,200 until real data is available. The discussion included the confirmation of various cover levels in HubSpot and the specifics of repair limits to streamline calls. The customer call script was refined to emphasize engagement, proposing a two-tiered approach for different levels of customer awareness. Live test calls revealed the need for realistic dummy data to address glitches, and a collaborative workflow session for HubSpot was scheduled. Leadership expressed confidence in the project’s potential to enhance customer outreach and planned to validate the system by calling 100 customers before Christmas.

Key Points

✅ Field Mapping Finalization: Data fields mapped between One AI and HubSpot for accurate call integration; average repair cost set under £1,200. 📞 Two-tiered Script Approach: Short script for unaware contacts; detailed one for those engaged with emails, aligned with ongoing email nurture campaigns. 🔍 Testing Challenges: Live calls revealed repetition glitches; realistic dummy contacts needed for thorough end-to-end testing and quality assurance. 📅 Workflow Scheduling: HubSpot workflow setup meeting scheduled for Monday; focus on trigger refinement for renewal dates and customer engagement. 🚀 Leadership Confidence: Strong belief in AI project’s potential to improve outreach; plan to call 100 customers before Christmas for real-world validation. 🔄 Continuous Optimization: Emphasis on A/B testing and script updates based on live data to enhance conversion and customer experience.

Overview

  • Field Mapping Finalization: Data fields mapped between One AI and HubSpot for accurate call integration; average repair cost set under £1,200.

  • Two-tiered Script Approach: Short script for unaware contacts; detailed one for those engaged with emails, aligned with ongoing email nurture campaigns.

  • Testing Challenges: Live calls revealed repetition glitches; realistic dummy contacts needed for thorough end-to-end testing and quality assurance.

  • Workflow Scheduling: HubSpot workflow setup meeting scheduled for Monday; focus on trigger refinement for renewal dates and customer engagement.

  • Leadership Confidence: Strong belief in AI project’s potential to improve outreach; plan to call 100 customers before Christmas for real-world validation.

  • Continuous Optimization: Emphasis on A/B testing and script updates based on live data to enhance conversion and customer experience.

Action Items

Leo Nelson Create dummy HubSpot contacts based on real customer data for testing integration accuracy and assign Michael Gur as owner (39:35) Provide revised script line for average repair cost phrasing after internal discussion (40:55) Participate in technical session on Monday to configure workflows collaboratively (31:00)

Michael Gur Conduct end-to-end tests on dummy contacts once created to verify data flow and identify call script errors (39:51) Troubleshoot repeating phrase error occurring in AI call simulations (24:25) Prepare and share list of call data fields (duration, transcript, outcomes) for HubSpot property mapping (26:56) Join technical workflow configuration session scheduled for Monday (31:35)

Amit Ben Lead script modifications to include fixed default average repair cost value and remove pricing from AI call phase one (11:40) Coordinate with team to review and test script fixes after data mapping updates (39:55) Join Monday workflow setup and integration session (31:37) Obtain HubSpot user access from WarrantyFirst for integration purposes (31:47)

Daniella Block Organize and schedule Monday’s technical meeting for workflow and integration optimization (32:59) Send email invitations and access details to participants, including Roy Lahav and Amit Ben (31:53) Document agreed script and field mapping changes and distribute to all stakeholders (46:28)

Yochai Levi Participate in Monday technical session to define workflows and integration specifics (31:20) Assist with script and process revisions based on meeting outcomes (46:30)

Roy Lahav Perform AI trial calls during testing phase; report issues such as phrase repetition and other glitches for troubleshooting (22:53) Collaborate on validating real contact data and integration accuracy (39:20)

Charlie Whiston Review script structure to ensure alignment with phased AI call rollouts and client interaction stages (17:00) Provide leadership input for adjusting customer communication approaches (41:10)