AI model for outbound automation

Claude Sonnet 5.5 runs your outbound at volume.

Opus gets the launch-day headlines. Sonnet is the model that actually runs your outbound — $2 per million input tokens, $10 output, a 1M-token context window, and "fast" latency. At that price-to-intelligence ratio, it's the default tier for production automation.

Shipped Sept 28, 2026 · Knowledge cutoff June 2026

Pricing$2 / $10 per M tokens
Context1M tokens · 128K out
SpeedFast latency
ThinkingAdaptive · default high
Batch API50% cheaper
Cache reads10% of input price
Where it sits

The sweet spot in the lineup.

At $2/$10, Sonnet 5.5 is half the cost of Opus 5.5 and a fraction of Fable — with far more intelligence and a 5× larger context than Haiku. For the tens of thousands of small AI calls outbound actually runs on, this is the tier the math works at.

Haiku 4.5
Cheapest
$1 / $5
per M in / out
Default for outbound
Sonnet 5.5
Speed + intelligence
$2 / $10
per M in / out
Opus 5.5
Deepest reasoning
$4 / $20
per M in / out
Fable 5.1
Premium tier
$10 / $50
per M in / out

Base API pricing per million tokens. Batch runs 50% cheaper; prompt-cache reads cost 10% of base input — both compound once you process thousands of leads a day.

Why this matters for outbound

At volume, price per token is your margin.

Outbound isn't one big AI call. It's tens of thousands of small ones: a personalization line per prospect, an enrichment judgment per Clay row, a reply classified, a transcript summarized, a next step decided. At that volume, the model's price per token is your margin.

The Opus tier is overkill for most of that work, and its price shows it. Haiku is cheap but you feel the intelligence gap on anything requiring real reasoning about a prospect. Sonnet 5.5 is the tier built for the middle: enough judgment to write and decide well, fast enough to keep a campaign moving, cheap enough to run on every record instead of a sample.

Our read: this is the default model for production outbound automation. Reserve Opus 5.5 for the few steps that genuinely need deeper reasoning, and use Sonnet 5.5 for everything that runs on every lead. The right build usually mixes both tiers rather than paying Opus rates for work Sonnet handles fine.

Migrating from Sonnet 5? Test first.

Forced tool use (tool_choice set to any or tool) now returns a 400, the old disabled-thinking mode was replaced with a between-tools mode at high effort or below, and the earlier computer_20251124 tool isn't accepted. Nothing dramatic — but run a sample batch before you flip production traffic.

How we'd use it

Four plays we'd wire up this week.

PLAY 01

Email personalization at scale

A first line or custom P.S. per prospect doesn't need Opus-level reasoning — it needs a model that reads the research and writes something human, across thousands of rows, without blowing the budget. At $2/$10 with batch pricing, per-lead personalization is economical at real volume. Core to how we build cold email infrastructure that doesn't read like a template.

PLAY 02

Claygent & enrichment prompts

Enrichment is where token costs quietly pile up — a model call on every row of a large table. Sonnet 5.5's 1M context lets you feed a full company page, a job posting, and prior notes into one judgment, and its speed keeps a 50,000-row table from taking all night. The enrichment brain behind serious list building. (See our take on Claygent Skills.)

PLAY 03

The brain behind AI call agents

Voice agents live and die on latency — a model that thinks for three seconds before answering kills a call. Sonnet 5.5's "fast" tier plus adaptive thinking is the profile you want: quick enough to hold a natural conversation, smart enough to handle an objection. A strong fit for the LLM layer inside the AI calling systems we run on Bland and Retell.

PLAY 04

Reply triage & post-call routing

After the send and the call comes the sorting: is this reply a yes, a not-now, or an unsubscribe? Did that call book a meeting or need a human? Classification and summarization at inbox volume is exactly the work Sonnet 5.5 is priced for. Route interested replies to a rep, auto-handle the rest, and feed clean outcomes back into the CRM.

The through-line

Right model, right step, right cost.

Run it on every record

Cheap enough to personalize, enrich, and classify on every lead — not a sample. That's the difference between a demo and a campaign.

Mix tiers on purpose

Sonnet 5.5 for the volume work, Opus 5.5 for the few steps that need deeper reasoning. Paying Opus rates for Sonnet-grade work is the quiet budget leak.

Batch and cache

Batch requests run 50% cheaper and cache reads cost a tenth of input. A pipeline built to use both pays far less than the sticker rate.

Questions teams actually ask

The fine print, up front.

Is Sonnet 5.5 good enough for cold email personalization, or do I need Opus?
For personalization and most outbound copy, Sonnet 5.5 is the right tool. It has enough judgment to write from research and sound human, and at $2/$10 you can run it on every prospect. Save Opus 5.5 for the handful of steps that need deeper multi-step reasoning.
How much does Claude Sonnet 5.5 cost to run at scale?
Base pricing is $2 per million input tokens and $10 per million output tokens. Batch API requests are 50% off and prompt cache reads cost 10% of the base input price, so a well-built pipeline that batches and caches pays far less than the sticker rate on high-volume runs.
Should I switch my existing Sonnet 5 automations to Sonnet 5.5?
Most likely, but test first. Watch the migration changes: forced tool_choice values any and tool now return a 400, disabled-thinking mode changed, and the older computer-use tool isn't accepted. Run a sample batch, confirm output quality and tool behavior, then move production traffic.

Want an outbound engine built on the current model lineup?

We build and run outbound systems for B2B teams — cold email infrastructure, AI calling on Bland and Retell, and Clay-based list building. Picking the right model for each step, and wiring it so the cost math works at volume, is the everyday job.