Pipeline Success / Homecare
Contacts: jasono | chrisb | david | brunasantos | ecorrons | ncuesta
Recent meetings: 2026-05-04-oneai-pipeline-success-weekly-meeting | 2026-04-06-oneai-pipeline-success-weekly-meeting | 2026-03-23-oneai-pipeline-success-weekly-meeting
Account Summary
Pipeline Success / Homecare operates a high-volume AI voice agent deployment across two verticals: sales pipeline qualification (pipelinesuccess.com) and healthcare staffing / caregiver support (homecare.com). The account has been running weekly syncs since mid-2025 and is deeply embedded technically, with the team pushing heavily on call quality, disposition logic, and contact data accuracy. The relationship is active and demanding, with Jason and Chris as the primary drivers of both QA and escalations.
Use Case
OneAI voice agents handle both inbound and outbound phone calls for lead qualification and caregiver onboarding. Outbound agents (including the “Ellie” and “Raquel” voice models) call contacts to qualify them and transfer verified leads. Inbound agents handle caregiver inquiries, capture caller identity (first/last name, email), support onboarding status checks, and route calls appropriately. The agents operate in a multilingual context (email collection in multiple languages) and integrate with a ticketing system for workflow automation.
Relationship Health
🟡 Stable but technically demanding — the account is engaged and operationally active, but recurring infrastructure issues (flagged phone numbers, call transfer bugs, transcript/disposition bugs) require consistent engineering attention and create friction that falls on Daniella to triage.
Key Contacts
- Jason O’Neill (jason.o@pipelinesuccess.com) — 35 meetings; primary relationship owner, drives QA reviews, escalates systemic issues, requests product features (toll-free numbers, unique phone numbers per agent, revision history)
- Chris Branum (chris.b@pipelinesuccess.com) — 34 meetings; operational QA lead, surfaces call handling and voicemail issues, monitors transfer rates, sends messages that need timely responses from the internal team
- David (david@pipelinesuccess.com) — 34 meetings; consistent attendee, role less prominent in notes
- Bruna Santos (bruna.santos@homecare.com) — 34 meetings; homecare-side stakeholder
- E. Corrons (ecorrons@homecare.com) — 34 meetings; homecare-side stakeholder
- N. Cuesta (ncuesta@homecare.com) — 34 meetings; homecare-side stakeholder
What’s Working
- Inbound call handling has matured significantly: caller identity capture (first/last name, email), inbound number rerouting, and the inbound call API are all deployed and functioning
- Ticket creation workflow was successfully streamlined from 12 touchpoints down to ~5-6 steps with automated subject generation, confirmed stable after a major update in late 2025
- Automatic email collection feature is live and working across inbound/outbound calls in multiple languages
- Knowledge base (.TXT file) update process is confirmed effective for improving inbound agent response quality
Open Challenges
- Flagged/shared phone numbers: The current shared number pool is hurting contact rates and generating flagged calls. Jason is pushing for unique phone numbers per agent with local area codes — a third-party vendor solution is being evaluated but not yet resolved
- Call transfer reliability: Recurring transfer bugs (e.g., Feb 2026 rollback after call ID mapping changes, Feb 23 connectivity issues) erode confidence in the product’s stability
- Voicemail and disposition accuracy: Ongoing issues with voicemail detection (confirmed bug Dec 2025), transcript-script discrepancies, and disposition logic edge cases (e.g., failed transfers reverting to ‘verified’) require continuous attention
- Response latency from internal team: Chris’s messages about call handling and voicemail issues are not being acknowledged quickly enough, putting Daniella in a difficult middle position
Open Action Items
- Daniella: Investigate phone number tracking tools (unique numbers per agent, local area codes, flagged number detection) — due within 1-2 days of 2026-05-04 meeting
- Daniella: Push internal team to respond to Chris’s outstanding messages about call handling and voicemail issues
- Amit: Fix sporadic transcript storage bug (DB issue causing rare message losses) — Jason to resume QA review post-fix
Recent Meeting Highlights
- 2026-05-04: Core focus was phone number quality — Jason made a strong case for unique numbers per agent with local area codes to improve contact rates and reduce flagged calls. Inbound call API is deployed and providing caller identity. Third-party vendor for number detection still under evaluation.
- 2026-04-06: Key product issues including AI transparency concerns with the Ellie model were addressed by end of March. A rare DB bug causing sporadic message/transcript loss is under investigation by Amit; operations otherwise stable.
- 2026-03-23: Flagged phone number monitoring is active but statistics are erratic, complicating automation decisions. Inbound call API confirmed deployed. Chris is providing examples of transcript-script discrepancies for review.
- 2026-03-16: Agreed to treat each inbound call as a new contact. Amit confirmed the system can handle multiple contacts mapped to a single phone number.
Prep Tips for Next Meeting
- Lead with the phone number investigation: Jason raised this as a priority on 2026-05-04. Come with concrete findings on tracking tools and a clear recommendation or options on the unique-number-per-agent approach — this is the top unresolved ask.
- Address Chris’s open messages directly: Confirm with Amit and the internal team what the status is on Chris’s call handling / voicemail questions before the call. Silence on these is a relationship risk.
- Transcript bug status: Know whether Amit has fixed the sporadic transcript storage bug so Jason can resume QA review — they are blocked on this.
- Flagged numbers specifics: If you’ve collected the list of flagged numbers and verified them (action from 2026-03-23), bring the data. Jason responds well to specifics over vague status updates.