Skip to main content

Master Project Task List

Document Purpose

This document serves as the authoritative overview for the Voice by aiConnected platform build. It provides Claude Code with complete context about the project’s goals, architecture, infrastructure decisions, and the sequence of work required to deliver a production-ready Voice AI contact center platform. Read this document first before beginning any implementation work.

Project Overview

What We Are Building

Voice by aiConnected is a white-label Voice AI contact center platform that enables businesses to deploy autonomous AI agents capable of handling inbound and outbound phone calls. The platform integrates with existing phone infrastructure (GoToConnect), leverages real-time audio processing (LiveKit), and delivers hyper-realistic conversational AI through a streaming pipeline of Speech-to-Text, Large Language Model, and Text-to-Speech services.

Business Context

  • Target Market: Small to medium-sized businesses needing 24/7 phone coverage, lead response, appointment scheduling, and customer service automation
  • Pricing Model: Fixed credit buckets plus per-minute overages
  • Competitive Advantage: 50-75% lower cost than competitors (Vapi, Retell, Bland AI) through infrastructure ownership and optimized provider selection
  • Parent Company: Oxford Pierpont Corporation (business development and digital marketing)

Core Capabilities

  1. Inbound Call Handling — AI answers calls, converses naturally, resolves inquiries or transfers to humans
  2. Outbound Call Automation — AI initiates calls for lead follow-up, appointment reminders, reactivation campaigns
  3. Human Handoff — Seamless transfer to live agents via blind transfer, warm transfer, or conference
  4. Tool Calling — AI executes business logic (CRM updates, calendar booking, data lookup) via webhooks/n8n
  5. Knowledge Base Integration — AI responses informed by client-specific business context (already built)
  6. Multi-Tenant Architecture — Single platform serves multiple clients with isolated configurations

Architecture Summary

Voice Pipeline

Latency Budget (Target: <1000ms mouth-to-ear)

Infrastructure Topology


Infrastructure Decisions (Finalized)

These decisions have been made and should not be revisited during implementation:

Cost Structure

Per-Minute Breakdown (at 50k min/month scale)

Monthly Infrastructure


Build Phases

Phase 1: Foundation (Documents 1-6)

Goal: Development environment ready, architecture fully documented Deliverables:
  • Architecture diagrams finalized
  • All API contracts documented
  • Local development environment functional
  • Repository structure established

Phase 2: Core Infrastructure (Documents 7-11)

Goal: Database, state management, and service skeleton operational Deliverables:
  • Database migrations created and tested
  • Redis state management implemented
  • Event bus operational
  • Core services running (API gateway, bridge, agent, worker)

Phase 3: Provider Integrations (Documents 12-16)

Goal: All external services connected and functional Deliverables:
  • LiveKit Agents pipeline functional
  • Deepgram streaming STT working
  • Claude streaming responses working
  • Chatterbox deployed on RunPod
  • Tool calling via webhooks operational

Phase 4: Call Features (Documents 17-20)

Goal: Complete call handling capabilities Deliverables:
  • Inbound calls answered by AI
  • Outbound calls initiated by AI
  • Transfers to human agents working
  • Knowledge base context in AI responses

Phase 5: Platform (Documents 21-23)

Goal: Multi-tenant API complete Deliverables:
  • Tenant CRUD operations
  • Usage tracking per tenant
  • Billing hooks implemented
  • API documented and versioned

Phase 6: Operations (Documents 24-27)

Goal: Production deployment with observability Deliverables:
  • Production environment provisioned
  • Deployment automated
  • Monitoring dashboards operational
  • Alerting configured

Phase 7: Hardening (Documents 28-30)

Goal: Secure, tested, resilient system Deliverables:
  • Security audit passed
  • Test suite comprehensive
  • Failure scenarios handled gracefully

Skills (Provider API Reference)

In addition to the 30 build documents, the following skills provide API reference material:

Success Criteria

MVP Definition

The minimum viable product is achieved when:
  1. Inbound Call: A call to a GoToConnect number is answered by the AI, which holds a natural conversation and either resolves the inquiry or transfers to a human
  2. Outbound Call: The platform initiates a call via API trigger, AI converses with the recipient
  3. Human Handoff: AI successfully transfers a call (blind or warm) to a live agent
  4. Tool Execution: AI executes at least one tool call (e.g., CRM update, calendar check) during a conversation
  5. Multi-Tenant: Two separate clients can operate independent AI agents simultaneously
  6. Latency: Mouth-to-ear response time under 1.5 seconds for 90% of interactions

Quality Gates


Constraints & Requirements

Technical Constraints

  • Python preferred for WebRTC bridge (aiortc ecosystem)
  • LiveKit Agents SDK is Python-native
  • PostgreSQL for relational data (existing expertise)
  • Redis for ephemeral state (call sessions)
  • Docker/Dokploy for container orchestration

Business Constraints

  • Timeline: MVP within 6-10 weeks
  • Budget: Minimize upfront costs; scale with usage
  • Team: Development via Claude Code with human oversight
  • Existing Systems: Must integrate with existing Knowledge Base and Admin Dashboard

Non-Goals (Out of Scope for MVP)

  • Custom voice cloning per client (use pre-set voices initially)
  • Multi-language support (English only for MVP)
  • SMS/chat channels (voice only)
  • Compliance certifications (SOC 2, HIPAA) — plan for later
  • Mobile app
  • Analytics dashboard beyond basic usage metrics

Document Dependency Map


How to Use This Document

For Claude Code

  1. Read this document completely before starting any implementation
  2. Follow the phase order — each phase builds on the previous
  3. Consult skills for API-specific implementation details
  4. Reference individual documents for detailed specifications
  5. Check deliverables at the end of each phase before proceeding

For Human Oversight

  1. Review completed phases before approving progression
  2. Test deliverables against success criteria
  3. Provide credentials and access as needed per phase
  4. Clarify requirements when documents reference “TBD” items

Open Questions (To Be Resolved)


Version History


Next Steps

  1. Human reviews and approves this Master Project Task List
  2. Human provides access credentials for open questions
  3. Claude Code proceeds to Document #1: System Architecture Overview
  4. Build proceeds phase by phase with human checkpoints

This document is the single source of truth for the Voice by aiConnected project. All implementation decisions should align with the specifications herein.

Pre-Build Checklist

✅ Infrastructure (Covered)

  • GoToConnect (telephony)
  • LiveKit Cloud (real-time audio)
  • RunPod A5000 (Chatterbox TTS)
  • Deepgram (STT)
  • Anthropic Claude (LLM)
  • DigitalOcean/Dokploy (platform)

⚠️ Technical (Needs Planning)


⚠️ Business Logic (Needs Planning)


⚠️ Compliance/Legal (Critical)


⚠️ Failure Modes (Needs Planning)