You Can Now Send 1:1 Personalized Emails from Inflection

Merge fields were always a compromise. {{first_name}} in a subject line isn't personalization, it's a word swap on top of one email everyone gets. Real 1:1 personalization — different copy, written for each person, sent from a real system — has meant exporting contact IDs, building a one-off campaign, and waiting for a segment to catch up. That's not personalization at scale. That's a workaround.

Inflection's new personalized emails flowstep fixes this. One asset. One journey step. Your normal deliverability and reporting. Except now each contact can get a different email, written just for them.

Every personalized email has two parts:

- A default email — the fallback everyone gets, using your normal Visual or HTML editor.

- A store of per-contact versions — full custom subject, preheader, and HTML, pushed in over the API or by an AI agent through MCP.

At send time, Inflection checks each contact for a version. If one exists, they get it. If not, they get the default. Nobody gets a blank email, and nobody has to build a second campaign to make it happen.

That resolution happens inside a single Send email step in a journey. Reporting, deliverability, and sender configuration all run through the one asset, the same way they would for any other email.

Emails can be personalized by AI using our MCP or by 3rd parties like Clay using our API. You can see exactly what any contact will get before it goes out — a live preview, right from their row in the versions table. And every version created, updated, or rejected shows up in an activity log, so you're not guessing what an agent pushed in overnight.

Inflection is B2B marketing automation built for the new way. You can now personalize at scale, to send the right message at the right time.