Vox Custom Phone Agent

Problem Addressed

Natural-language phone requests often miss the structured fields needed for an outbound call: the destination number, the call goal, the bot role, the voice, and sometimes unsafe intent. Vox Custom Phone Agent targets Agent or Claw environments and turns these prompts into a TeddyMobile Vox botType=custom outbound task, asking targeted follow-up questions before initiating a request.

How It Works

The core flow starts by confirming the usage mode, distinguishing promotion trial from formal account usage. It then extracts callee, goal, role, voiceType, and the required businessContext when the prompt is too generic. Once the fields are complete, the skill generates a Vox extra.agent_profile, validates the phone number, and calls the appropriate endpoint: the credential-free /vox/v2/outbound endpoint for trial mode, or the HMAC-authenticated /vox/v1/outbound endpoint for formal mode. It also handles voice selection, follow-up order, risk interception, and AI identity handling: if the callee directly asks whether the caller is AI, the bot should answer truthfully.

Boundaries and Caveats

The skill focuses on generating and starting an outbound task, then returning Vox request status and a requestId. It does not perform real-time SSE conversation control, receive live call transcripts, support batch outbound calls in the MVP, or run dry-run previews. Requests involving impersonation of institutions, requests for verification codes, passwords, or bank cards, threats, harassment, transfer inducement, or medical, legal, and financial promises beyond basic notification are blocked or rewritten into a compliant form.