AgentCall Phone Numbers for AI Agents

Problem: AI agents need a real phone channel

Many automation flows stop at chat or internal APIs and cannot handle live inbound calls, outbound confirmations, SMS reach, or voice reception. agentcall gives an agent an AgentCall API surface for phone numbers, SMS, voice calls, and AI voice calls. It is useful when a workflow needs a real phone number path for intake, appointments, reminders, follow-ups, or customer support instead of text-only interaction.

How it works: operate on numbers and call state

The skill centers on resources such as /v1/numbers, /v1/sms, and /v1/calls. It can list numbers, read details, rename a number, or update inbound AI voice and language without replacing the whole inbound config. It can also provision or release numbers, with release marked as irreversible. For AI voice, it can set a system prompt, recording flag, notification destinations, maximum duration, language, or a contextWebhook for live context. Outbound AI calls dial a real number and are billed per minute, so destination, prompt, and duration should be explicit.

Boundaries: cost, geography, and confirmation

The reference stresses real-world side effects: SMS, outbound calls, and AI calls contact actual recipients; provisioning, BYOK switches, and premium voice can create recurring or per-minute costs; releasing a number cannot be undone. AI voice is limited to US and Canada numbers, and Free plan limits can cause hang-ups or upgrade requirements. Before acting, confirm the target number, recipient, recording setting, billing mode, and expected cost to avoid unauthorized spend or unwanted contact.