Klaviyo is buying Agency to add returns, order tracking and AI support to its marketing tools

Klaviyo is pulling two of ecommerce’s busiest support requests, “Where is my order?” and “How do I return this?”, into the orbit of its marketing platform.

Klaviyo has agreed to acquire Agency, an AI-powered customer-success startup founded by Elias Torres; financial terms were not disclosed, according to TechCrunch. TechCrunch reported that Torres will become Klaviyo’s chief product officer and that Agency’s 25-person team will join the company.

SaasRise described Agency’s offering as AI agents that handle post-sale support work such as returns and order tracking. Klaviyo already offers AI agents, including Composer for building marketing campaigns and Customer Agent for automating support, and it plans to broaden those capabilities across its customer base of about 200,000 businesses, according to TechCrunch.

Why this deal is operational news, not founder drama

The easy headline is the “full circle” reunion. TechCrunch noted that Torres and Klaviyo CEO Andrew Bialecki share a long history and encountered each other earlier in their careers. The bigger enterprise takeaway is simpler. Martech vendors are starting to bundle service automation as a built-in function, which can turn what were three separate buying processes, marketing automation, customer service software, and returns tech, into a single evaluation.

That matters because order status and returns are not just “experience” issues. They are operational workflows. They depend on shipping scans, carrier data, payment policies, fraud limits, inventory visibility, and reverse-logistics throughput. Once an AI agent begins taking actions in those flows, ownership often expands from marketing ops to shared governance that includes CX ops, ecommerce, and IT.

What Klaviyo says it is building with Agency

Klaviyo says it plans to pair Agency’s technology with its current agent products and roll them out across its installed base. TechCrunch reported that Bialecki positioned the integration as a way to bring the agent products to roughly 200,000 businesses, with the longer-term goal of reaching many more.

SaasRise reported that Agency is three years old and had raised $32 million from Sequoia, Menlo Ventures, and Felicis before the acquisition. For operators, that funding context matters because it suggests Agency was designed as a standalone platform, not a narrow add-on. In practice, that often translates into more integrations, richer workflow configuration, and a team that has already worked through early integration challenges with common ecommerce systems.

TechCrunch and SaasRise highlighted the same starting use case: post-sale support, including returns and order tracking. Those areas are strong candidates for agent automation because customer requests repeat, the underlying knowledge can be organized, and impact can be measured through lower contact rates and faster resolution times.

What to watch in vendor evaluations and rollout plans

For operators, the first issue is not whether the agent can respond. It is what actions it is permitted to take. A “return created” event affects downstream work, inventory disposition, refunds, and possibly fraud controls. If the tool lives inside a marketing platform, teams should verify which system of record authorizes those actions and how edge cases get handed to human staff.

Second, teams will pressure-test data boundaries. Order tracking and returns require data from commerce platforms, OMS, WMS, and carriers. When those feeds pass through a marketing automation vendor, security groups will want a clearer inventory of what personal data is stored, what is cached, and what is used to train or tune models. The day-to-day work is contract terms, retention settings, and audit logs, not model scores.

Third, expect procurement categories to blur. If a marketing platform can reliably deflect a measurable portion of WISMO and returns inquiries, it can alter the ROI case that once supported a separate support-automation product or returns-portal spend. That does not automatically make consolidation the right move, but it forces point solutions to prove either stronger handling of edge cases or better unit economics.

Questions to put in the Klaviyo and Agency integration plan

• Action scope: Will the combined Klaviyo agent be able to initiate returns, trigger refunds, change delivery addresses, or only answer status questions? Ask for a permissions matrix by workflow step.
• System of record: Which platform wins when data conflicts, Klaviyo’s profile, the commerce platform, or the OMS? Require a diagram of data flow and write-back behavior for returns and order events.
• Measurement: Define success as deflection plus customer outcomes. Require baseline and post-pilot metrics for contact rate per order, repeat purchase, and return rate so teams don’t optimize for deflection alone.
• Governance: What audit logs exist for agent actions, and how long are they retained? This is the artifact compliance and customer-ops teams will need during escalations.
• Timeline: TechCrunch reported terms were undisclosed. Ask what features ship pre-close vs post-close and what support model applies during transition.