Human callers.
Accessed by API.

Give your apps and agents a real human caller. Request a call through REST, MCP, or your favorite AI chat interface. A real person handles the conversation, and your apps and agents get the structured answers they need to move forward.

No hiring, no training, no managing staff. Just the power of a real human caller programmatically.

request.httpAPI + MCP PREVIEW
// POST /api/v1/call-requests · request body

{
  "mode": "sandbox",
  "template": "appointment_confirmation",
  "company": {
    "name": "Northstar Home",
    "context": "Heating and cooling services. Only confirm the scheduled visit; do not change prices or make commitments."
  },
  "recipient": {
    "name": "Maya Reynolds",
    "phone": "+12025550123"
  },
  "appointment": {
    "service": "Annual heating and cooling tune-up",
    "date": "2026-10-15",
    "window": "10 AM–12 PM",
    "timezone": "America/New_York"
  }
}
Human-executedMachine-readable results

01 / REQUESTStart wherever you work.

Your application sends a REST API request.

02 / HUMAN CALLA person talks. Your software listens.

Human caller

For Northstar Home · heating & cooling services

Confirm an annual heating & cooling tune-up

Calling Maya Reynolds · October 15, 2026 · 10 AM–12 PM Eastern

  • Confirm visit date and time
  • Get access instructions
  • Ask if pets will be home
Ready to call
Conversation

The human caller is reviewing the request.

Suggested wording · say next

Hello Maya Reynolds, I’m calling on behalf of Northstar Home to confirm your Annual heating and cooling tune-up. May we record this call?

Draft answer values0 of 4 shown

Animated preview of result.answers.*.value. The API includes evidence and returns answers after caller review.

recording_consent
null
appointment_status
null
access_instructions
null
pets_at_home
null
Received via REST API · req_example

03 / WHAT HAPPENS NEXTThe answers keep your business moving.

  • Your records update

    Answers saved to your app database or CRM.

  • Your agent continues

    Structured results unlock the next step.

  • Your workflow moves forward

    A follow-up, notification, or task starts.

  • Your call is documented

    Get the full recording, transcript, and results.

When to choose a human

When the call needs a human,
request one via API.

One clear brief. One atomized call request.
The result goes back to your apps & agents.

No consent for an AI-voice call?

Consent requirements extend beyond sales. Under TCPA rules, AI-voice calls to mobile numbers generally require prior express consent—even for informational calls—unless an exemption applies. Covered telemarketing generally requires written consent.

AI-generated voices fall under TCPA artificial-voice rules. Violations can lead to $500 in statutory damages per call, potentially rising to $1,500 for willful or knowing violations.

Why a human?

A live, manually dialed call may be an option after the business verifies eligibility, Do Not Call restrictions, opt-outs, calling hours, and state laws.

Live calls still require an eligible contact. Political and charitable outreach can have additional rules.

See the technical flowAPI, MCP, company knowledge, and result delivery

Ship the request.
Skip the staffing project.

Put the objective, context, and required fields in one API request. Let the call’s outcome flow straight back into your apps and agents.