Klaviyo just bought its way into fully autonomous campaigns
Klaviyo announced on 5 August 2026 that it's acquiring the team and technology behind Agency, a 25-person AI-native customer success startup founded by Elias Torres. Torres joins Klaviyo as Chief Product Officer once the deal closes in the third quarter, reporting to co-CEO Andrew Bialecki, and will run Klaviyo's entire agent product line. The announcement landed the same day as Klaviyo's Q2 results, where the company raised its full-year revenue guidance and leaned hard on the phrase "autonomous B2C CRM" to describe where the platform is headed.
What Klaviyo actually bought
Agency had raised US$32 million from investors including Sequoia, Menlo Ventures and Felicis before Klaviyo moved on it. Torres isn't a stranger to Bialecki, either, he hired Bialecki as one of his first engineers at Performable, the company HubSpot acquired in 2011. That history matters less than the mandate Torres is walking into: he now owns Composer and Customer Agent, the two products Klaviyo has been building to make the platform run with less human input, not more.
What Composer and Customer Agent actually do
Composer is Klaviyo's marketing agent. Give it a prompt, a brief, or a loose idea, a re-engagement series, a product launch, a seasonal promotion, and it builds the audience, drafts the content, and sets up the send using your real customer and purchase data. It currently covers email and SMS, with push and WhatsApp on the way.
Customer Agent sits on the service side. It handles post-sale support: order tracking, returns, the kind of query that used to land in a shared inbox. The two products are designed to talk to each other, Customer Agent's resolved conversations feed back into how Composer targets and personalises the next campaign.
Put together, that's an ESP that doesn't just send what you build, it builds what it thinks you need and handles the resulting service load too.
Why this matters more than a standard feature release
Every ESP has bolted some flavour of AI onto campaign creation over the past two years. What's different here is the acquisition itself. Klaviyo didn't build a chatbot on top of its existing tools, it bought a founder and a team whose entire product was autonomous customer interaction, and gave that founder the product chief seat. That's a company deciding its future is agents acting on a brand's behalf, not agents assisting a marketer who stays in the loop.
For brands already running flows, segments and campaigns in Klaviyo, that shift changes what "reviewing your email program" means. It used to mean checking what a person built. Increasingly it means checking what a system built on the person's behalf, at a speed that outpaces manual review unless someone deliberately slows it down.
The compliance angle Australian brands can't skip
Australia's Privacy Act reform is moving in the same direction as this product, straight at automated decision-making. From 10 December 2026, APP entities have to disclose in their privacy policy when personal information is used in a computer program to make decisions that could significantly affect someone's rights or interests. A support agent deciding how to handle a return, or a marketing agent deciding who gets flagged as high value and targeted accordingly, sits squarely inside that description.
Brands adopting Customer Agent or leaning on Composer's targeting decisions need their privacy policy to actually say so, not just describe email marketing in general terms. This isn't a hypothetical future problem tied to some other company's tech. It's the exact product Klaviyo just put a chief product officer in charge of building out.
What brands need to do
Don't switch on Customer Agent or hand Composer unsupervised control of your sends before checking two things. First, whether your privacy policy discloses automated decision-making in a way that would hold up against the December 2026 requirement, not just a generic AI clause. Second, whether someone on your team is actually reviewing what these tools produce before it reaches customers, rather than treating the output as finished work.
If you're already running Klaviyo, watch how Composer and Customer Agent roll out to your account over the coming months and treat early access as a chance to set review processes before adoption becomes the default, not after. Build the QA step now, while it's still optional.
Not sure how your current setup would hold up? Run the free audit, ten questions on your automations, deliverability, and reporting, with a score and a prioritised list of what to fix first.
Frequently asked
No, both are opt-in features sitting alongside standard campaign and flow building. Nothing about this acquisition forces existing accounts onto AI agents. The direction of travel matters more than the immediate obligation, because Klaviyo is clearly investing its product roadmap here.
Not yet, and Klaviyo hasn't announced separate pricing for Composer or Customer Agent usage. Platforms that build agent products around a core subscription typically introduce usage-based or tiered pricing once adoption is established, so budget for that possibility rather than assuming it stays bundled forever.
It creates a disclosure obligation. Under the current wave of Privacy Act reform, APP entities need to say in their privacy policy when personal information feeds into automated decisions that could significantly affect someone, and from 10 December 2026 that requirement is explicit. A support agent making decisions on returns or order issues using customer data fits that description, so check your privacy policy covers it before you switch it on.
Yes, at least for now. Treat anything Composer produces as a draft from a competent junior marketer, not a finished send. Review the audience, the offer, and the copy against your brand standards before anything goes out, the same as you'd review work from a new hire.