For AI agents: a documentation index is available at the root level at /llms.txt and /llms-full.txt. Append /llms.txt to any URL for a page-level index, or .md for the markdown version of any page.
  • Introduction
    • Overview
    • Installation
    • Developer Onboarding
    • Quick Start
  • Concepts
    • Architecture
    • Call States and Lifecycle
    • Call Commands
    • Audio Streaming
    • Event Handling
  • Integrations
    • Google GenAI SDK (Gemini Live)
    • Google ADK (Agent Development Kit)
  • Use Cases
    • After-hours Voicemail
    • Appointment Booking
    • Call Monitoring and Coaching
    • Database Lookup
    • Human Escalation
    • Interactive Notifications
  • Reference
    • API Reference
    • Error Handling
    • Advanced Topics
LogoLogo
On this page
  • Minimum information to collect
  • Related Docs
Introduction

Developer Onboarding Form

||View as Markdown|
Was this page helpful?
Previous

Installation

Next

Quick Start

Built with

Use this intake form before your first telco-connected SDK deployment. It is designed for implementation teams that need to align phone numbers, carrier details, WebSocket endpoints, security controls, launch scope, and operational contacts before AgenTao provisions or reviews the integration.

Fill in the fields below, then share the completed form with your AgenTao onboarding contact or attach it to your internal launch ticket.

For company review in plain text, use the companion Markdown template at developer-onboarding-review-template.md.

Builder intake

Prepare the details that unblock technical review

The fastest onboarding path is to gather business ownership, target numbers, telco routing, WSS endpoints, firewall requirements, and launch risk items in one place. This form keeps that handoff consistent across sandbox and production environments.

Best for: Voice AI teams, contact center builders, telephony platform teams, and solution engineers integrating the SDK with a carrier or BYO-telco setup.

Expected inputs: E.164 phone numbers, environment details, WSS URLs, firewall policy, use case scope, concurrency estimates, and production ownership.

1. Program ownership
2. Environment and launch scope
Use case options
3. Phone numbers and telco configuration
4. SDK connectivity and WSS endpoints
5. Firewall and network controls
6. AI, media, and compliance
7. Validation and launch readiness

Minimum information to collect

If you only need a lightweight intake before the full review, collect these first:

  • Project owner and escalation contact
  • Launch environment and target go-live date
  • Telco or carrier name
  • Phone numbers in E.164 format
  • Primary wss:// endpoint
  • Firewall or proxy constraints
  • Use case summary and target call volume
  • Compliance, recording, and fallback expectations

Related Docs

  • Installation
  • Quick Start
  • Architecture
  • Audio Streaming