IonBin
All pages
Search

Answer the phone with an intake agent, then warm-transfer to a person

SupportChecked 2026-10-18

Skip the repeat questions so people start every call already knowing who is calling and why.

  1. 01You
  2. 02Your AI platform
  3. 03Fish Audio
  4. 04Fish Audio
  5. 05Fish Audio
  6. 06You
Recipe context

A Fish Audio voice agent picks up your business line, says it is an AI, looks up the caller in your own system, asks a few intake questions and then briefs you on a private line before connecting the call. It collects context and hands off; it does not try to solve the problem.

Independent review. Unpaid; no partnership with the tools on this page. Based on public documentation and research. Trademarks identify their owners’ products. Disclosure.

Editorial shortlist

Compare your options.

For preparing intake dialogue and escalation rules.

Script tools do not replace Fish Audio; test transfer and caller disclosure separately. Choose one for drafting from approved material; switching may need setup changes.

Used by Ion · separate from rank.

Unpaid picks. No partnership with Claude, ChatGPT, Gemini (Google).

  1. 1 · Primary / high

    Claude

    Used by Ion — Used by Ion for its own work. This is separate from recommendation rank and is not a claim that every feature was tested.

    Why it fits: Document and project context supports iterative drafting against supplied evidence.

    Tradeoff: The assistant cannot establish that an internal practice is current or actually followed.

    Choose it for reconciling source text and reviewer feedback.

    Evidence for Claude

    The linked IonBin review records capabilities, access limits and source links. Review date: 2026-10-18. Primary product reference ↗

  2. 2 · Secondary / medium

    ChatGPT

    Why it fits: File-based drafting can combine supporting tables with the written brief.

    Tradeoff: Account-specific upload limits and missing source exceptions need checking.

    Prefer it when mixed documents and data extracts need discussion in one session.

    Evidence for ChatGPT

    The linked IonBin review records capabilities, access limits and source links. Review date: 2026-10-18. Primary product reference ↗

  3. 3 · Third / lower

    Gemini (Google)

    Why it fits: File analysis offers a drafting route for a team already using Google's assistant.

    Tradeoff: Account and region availability differ; do not assume access to live team files.

    Prefer it when reviewers already use Gemini and can supply the same approved evidence.

    Evidence for Gemini (Google)

    The linked IonBin review records capabilities, access limits and source links. Review date: 2026-10-18. Primary product reference ↗

How this shortlist was chosen

Editorial judgment, not a personal-use endorsement or performance score. These are alternatives for the named role, not three required stack components. Vendors did not pay for, request or approve these positions.

Source reconciliation comes before extra automation. A lower-ranked option may fit your constraints better; compare the conditions stated on each card before choosing.

Setup and portability: Keep the approved source pack and accepted output outside chat. Upload access is not publication permission.

Reviewed 2026-10-21. This page applies a shared comparison for “drafting from approved material” to the stated task and constraints. It is documentation-based editorial guidance, not three new hands-on tests. We weigh value for the job, distinct capabilities, replacement limits, technical effort and interoperability. Check current plan terms before adopting or switching.

See our review method, MCP connections and portability and switching costs.

Connects through: Built-in integration · API

Not advice

IonBin provides general information and software comparisons, not tax, legal, accounting or financial advice. Tax and legal rules vary by situation and jurisdiction; consult a qualified professional (CPA, enrolled agent or attorney) before acting.

AI tools can make mistakes. Verify every figure against the original documents and official IRS or state guidance before filing or signing.

Redact Social Security numbers, account numbers and EINs before uploading documents to any AI assistant, and check its data-retention settings. Upload originals only to the filing or signing software.

Requirements vary by state. File through official sources such as the USPTO trademark search and your state’s Secretary of State site.

Steps

  1. You

    Write the AI disclosure line, three to five intake questions and what may be recorded

    Human stepConfirmed
  2. Your AI platform

    Drafts the agent prompt and a spec for a small caller-lookup endpoint

    AI platformConfirmed
  3. Fish Audio

    Answers calls on a number bound to the agent (a managed Twilio-backed US or Canada local number, or your own over SIP)

    Built-in integrationConfirmedSource ↗
  4. Fish Audio

    Looks up the caller and saves notes through webhook tools that call your own endpoint

    You host and secure the lookup. {{system.caller_number}} is not proof of identity; minimize returned data.

    APIConfirmedSource ↗
  5. Fish Audio

    Warm transfer: holds the caller, rings you on a private call, briefs you, then merges once you accept

    Use warm_connect "confirm" so the calls merge only after you agree.

    Built-in integrationConfirmedSource ↗
  6. You

    Handle the caller's actual issue, then review transcripts and transfer outcomes weekly

    Human stepConfirmed

Confirmed = vendor-documented, not Ion-tested. Human and AI-platform steps are proposed roles.

Human approval

A person handles every caller's actual issue. The agent only identifies the caller, asks the intake questions and briefs you.

Watch out for

Tell callers they are talking to an AI and that notes are kept. Recording continues after a warm transfer merges, and consent rules for recording differ by place. This is general information, not legal advice.

Starter prompt

Design an AI-disclosed intake agent with these questions: <list>. Treat caller ID only as a lookup hint. Specify authenticated, minimal-data lookup and notes endpoints; never disclose private account information without identity verification. Use warm transfer with human confirmation, and define failed-lookup, voicemail and unavailable-person fallbacks. Do not promise refunds or fixes.

Written for this workflow. Paste it into your AI platform and adjust it to your situation.

Tools in this workflow

ToolRoleOfficial site
Fish AudioBuilt-in integration, API fish.audio ↗
ClaudeAI platform claude.ai ↗

Which AI platforms can run it

PlatformStatusWhy
Claude (incl. Claude Code) To verify Fish Audio: verify the API caller, network access and credentials; platform code execution alone does not establish this connection
OpenAI Codex To verify Fish Audio: verify the API caller, network access and credentials; platform code execution alone does not establish this connection
Google Antigravity To verify Fish Audio: verify the API caller, network access and credentials; platform code execution alone does not establish this connection
ChatGPT To verify Fish Audio: verify the API caller, network access and credentials; platform code execution alone does not establish this connection
Gemini To verify Fish Audio: verify the API caller, network access and credentials; platform code execution alone does not establish this connection
Perplexity To verify Fish Audio: verify the API caller, network access and credentials; platform code execution alone does not establish this connection
What the platform statuses mean

Confirmed: documented access meets the recorded requirements. Inferred: a reviewed note describes a plausible, untested pairing. To verify: a connection or step is unresolved. MCP and API pairings need route-specific evidence; a plugin, CLI or API alone does not prove compatible access, credentials or permissions. These are documentation assessments, not IonBin runtime tests.

This is general information, not legal advice. Call-recording and AI-disclosure rules differ by place, so check the rules where you and your callers are before you record.

What we checked (2026-10-18)

  • Phone numbers. Fish Audio sells managed local numbers for the US and Canada through its API, with Twilio as the provider, and binds each number to one agent. You can also import a number you already own over SIP.
  • Caller lookup. Webhook tools let the agent call your HTTP endpoint mid-call, and the caller’s number is available as a system variable. You supply the lookup endpoint. Its responses enter the agent conversation, so this is not a promise that Fish Audio never processes or retains customer data. Caller ID is a lookup hint, not identity verification; return only the information an unauthenticated caller may receive.
  • Warm transfer. In warm mode the caller hears hold music while the platform rings your person on a private call and the agent briefs them. With the confirm setting the calls merge only after the person agrees. Recording continues after the merge; the transcript covers only the agent’s part.
  • Cost. The dedicated Agents pricing page lists $0.06 per conversation minute, with basic-model token charges currently included as a promotion. Managed phone calls add $0.01 per minute; warm-transferred time is $0.025 per minute after merging, and managed numbers are $1.20 per month. Other models and some destinations cost more. Imported SIP uses different charges; check the published rates and your carrier.
  • Alternative. To build the voice agent yourself instead, Twilio’s Conversation Relay connects a phone call to your app over a WebSocket and handles speech recognition and text to speech.
  • Failure handling. Test no answer, voicemail, declined transfer, missing caller ID and failed lookup. Enable the documented human-answer detection where appropriate; it is not a guarantee that every voicemail greeting will be detected.

Set it up

  1. Write the disclosure line and the intake questions before anything else.
  2. Stand up a read-only lookup endpoint and a separate notes endpoint, and authenticate each request and limit returned fields. Blocking tools pause the conversation; background tools can let it continue. Log and test failures for either mode.
  3. Bind a test number to a draft agent, call it yourself and check the briefing.
  4. Publish the agent, move the number over, and review transfer outcomes weekly.

Credit: the idea comes from an Instagram reel on AI phone intake by creator Angus Sewell. IonBin reviewed the documented components; live calls and this complete workflow have not been tested; the credit is not an endorsement.

Verification limits and implementation checks

The page is documentation-reviewed; the complete workflow has not been run by IonBin.

  • Test calls, authentication, retention settings and local recording requirements before deployment.

Sources

No affiliate links on this page. No paid placements in workflows. How IonBin makes money.