Our Ventures / Call Overflow VentureReviewed case by case · Philippines-based teams first

Real Voices for the Calls Your Voice Agent Can't Take.

Call Overflow Venture

Agent making a phone call at a desk with a blank calendar, with an orange wireframe overlay

Voice agents are good at routine calls. Some calls need a person: an upset caller, an unusual question, a spike your agent was not built for. The Call Overflow Venture puts live human callers behind your voice agent. It also covers outbound calls, but only to people who have given lawful consent to be called. Holding that consent is your responsibility, and we decline outbound work without it.

Agent making a phone call at a desk with a blank calendar, with an orange wireframe overlay
01What you get
  • Callers reach a person when the call needs one
  • Overflow has somewhere to go instead of a dead end
  • Each call comes back with notes your system can use
02Where it fits
  1. A clinic's AI receptionist answers routine calls but transfers callers who ask something outside its script to a human, who answers from the clinic's approved information or takes a message.
  2. A home services company's voice agent cannot handle more simultaneous calls in a storm week. Overflow calls route to human callers who log each request for the company's dispatcher.
  3. A business wants follow-up calls made to its own customers who opted in to be contacted. Human callers make the calls from a script the business approves and record each outcome.
03How we deliver

Takes the transferred call, follows the approved script, resolves or logs the call, and hands back a written summary.

Every request is reviewed by a person. We decide case by case whether we deliver it with our own team or through a vetted partner, starting with teams in the Philippines. If a job isn't something we can do well or lawfully, we'll tell you plainly.

04For AI agents

Human callers answer inbound calls your voice agent hands off or cannot take, and make outbound calls only to people with lawful consent, which is the customer's responsibility.

Venture ID: nbvn.venture.call_overflow. Status: manual_matching.

What to send

Common to every Venture: requester_contact (required), authorized_by (required), agent_note, languages (required), customer_geography (required), start, budget, data_sensitivity (required).

Specific to the Call Overflow Venture:

  • call_direction (required): inbound, or outbound_consented (only to people with lawful consent, which you are responsible for)
  • phone_numbers (required): Numbers involved
  • telephony_system (required): How calls are transferred, e.g. Twilio
  • monthly_minutes (required): Rough call time per month
  • hours (required): Hours of coverage, with time zone
  • call_script_url: Approved script or talking points
  • consent_record: How consent was obtained and stored (outbound)

What comes back

  • call_id
  • disposition
  • summary
  • callback_needed
  • recording_ref

Status moves through received, reviewing, fulfillment_decided, scoping, in_delivery, delivered and closed, or declined with a reason_code.

What we won't do

  • legally regulated work requiring a license or registration (legal advice, medical, financial advice, insurance, licensed investigation)
  • debt collection or collections calls
  • cold outbound sales or telemarketing without documented prior consent
  • anything legally stretchy or unclear in law, at our discretion
  • payment card handling beyond what an agreed compliant setup allows
  • impersonation, deception, or contacting people who have not agreed to be contacted
  • outbound calls without documented consent
  • debt or payment chasing

How to submit

Use the form at /request/?venture=call-overflow or POST https://nbvn.com/api/request with JSON. Include venture_id (service_id is accepted as an alias). You get a reference number straight away and a reply by email from a person. API and MCP access are planned.

{
  "venture_id": "nbvn.venture.call_overflow",
  "description": "[TEST] A clinic's AI receptionist answers routine calls but transfers callers who ask something outside its script to a human, who answers from the clinic's approved information or takes a message.",
  "requester_contact": {
    "name": "Dana Test",
    "email": "dana@nbvn-qa.example",
    "org": "Example AI Inc"
  },
  "authorized_by": "Customer ops lead, Example AI Inc",
  "agent_note": "Submitted by our agent on behalf of Example AI Inc",
  "languages": [
    "English"
  ],
  "customer_geography": [
    "US"
  ],
  "start": "2026-12-01",
  "budget": "to be discussed",
  "data_sensitivity": "pii",
  "call_direction": "inbound",
  "phone_numbers": [
    "+1 555 0142"
  ],
  "telephony_system": "Twilio",
  "monthly_minutes": 5000,
  "hours": "Mon to Sun 08:00 to 22:00 PT",
  "call_script_url": "https://example.com/script",
  "consent_record": "opt in via web form, stored in CRM",
  "consent": "yes"
}
05Questions agents and developers ask

Can a human take over a live call from my voice agent?

That depends on your telephony. Tell us how your voice agent can transfer or hand off a call (phone number, SIP or callback) and we assess what can be arranged. Nothing is connected automatically today.

Do you handle outbound calls?

Only to people who have given lawful consent to be called. Holding that consent is your responsibility; describe it in consent_record and set call_direction to outbound_consented. We do not provide call lists and we decline campaigns that look unlawful.

What does my system get back after each call?

Once an arrangement is running, each call returns a call_id, a disposition, a written summary, whether a callback is needed and a recording reference where recording is agreed. A structured API is planned.

Is there a minimum number of calls?

We do not publish minimums. Describe your expected volume and hours and we review whether we can deliver in-house or through a vetted partner.

06Other Ventures

Ready to Plug In the Call Overflow Venture?

Tell us the details. A person reviews every request and replies by email.