OneAI - Pipeline success - weekly meeting

Date: 2025-10-27 | Duration: 49.34000015258789 min | Account: pipeline-success

External attendees: bruna.santos@homecare.com, chris.b@pipelinesuccess.com, david@pipelinesuccess.com, ecorrons@homecare.com, jason.o@pipelinesuccess.com, ncuesta@homecare.com

Summary

The team convened to finalize preparations for testing the Pipeline Success API integration, emphasizing the importance of effectively mapping and storing contact IDs for consistent user data. Nahuel Cuesta Luengo clarified that the API flow remains unchanged, while Amit Ben highlighted the necessity for OneAI to retain the Pipeline Success contact ID to prevent data loss. Improvements in dialogue flow were discussed, including the removal of explicit acknowledgments for more natural interactions. The inbound home care agent flow was streamlined to efficiently manage user inquiries with automated ticket creation linked to Zendesk. However, challenges arose concerning 401 authentication errors during ticket creation, necessitating adjustments in API request format. A phased testing strategy was agreed upon, starting with text-based tests to validate logic before transitioning to voice tests.

Key Points

✅ API Integration Ready: Pipeline Success API is ready for testing, focusing on mapping and storing contact IDs for consistency. 💬 Improved Dialogue Flow: Removing explicit acknowledgments will create more natural interactions, enhancing user engagement. 🏠 Inbound Flow Simplified: Home care agent flow now efficiently handles user concerns with automatic ticket creation and validation prompts. ⚠️ Ticket Creation Issues: Facing 401 authentication errors; adjustments needed in API request format and token placement for Zendesk. 🛠️ Phased Testing Strategy: Begin with text-based tests for quick validation, followed by voice tests to ensure complete functionality. 🔄 Flexibility in Updates: Easy updates to ticket choices and details based on user feedback will optimize the flow continuously.

Overview

• API Integration Ready: Pipeline Success API is ready for testing, focusing on mapping and storing contact IDs for consistency.
• Improved Dialogue Flow: Removing explicit acknowledgments will create more natural interactions, enhancing user engagement.
• Inbound Flow Simplified: Home care agent flow now efficiently handles user concerns with automatic ticket creation and validation prompts.
• Ticket Creation Issues: Facing 401 authentication errors; adjustments needed in API request format and token placement for Zendesk.
• Phased Testing Strategy: Begin with text-based tests for quick validation, followed by voice tests to ensure complete functionality.
• Flexibility in Updates: Easy updates to ticket choices and details based on user feedback will optimize the flow continuously.

Action Items

Jason O’Neill Provide curl command with details to finalize Zendesk API token and body structure for ticket creation (46:08) Work with team to address Zendesk API authentication and upload necessary credentials (41:36) Post testing results and findings after review of inbound and ticket creation flows throughout the week (48:21) Adjust script wording to accommodate absence of data such as zip code to improve question phrasing (16:47)

Nahuel Cuesta Luengo Test Pipeline Success inbound API calls offline and report any issues for troubleshooting (20:44)

Daniella Block Request addition of permanent memory for Pipeline Success contact ID to AI for conversation continuity (22:46)

Amit Ben Create a task to add Pipeline Success contact ID to permanent memory for AI (22:46) Share documentation with team explaining all ticket creation and flow details to ensure alignment and completeness (46:14) Continue refining ticket flow subjects and descriptions for clarity and testing (37:49) Assist team by reviewing and correcting JSON body format for Zendesk ticket creation API call (39:05) Implement silence idle message improvements releasing this week to better handle callers asking AI to hold (12:40)