An agent on every contact
and account.
Set the goal once. Plays decide what every person gets and when, personalize every email, and log the reason for each decision.
Used by MOps teams replacing Marketo, Pardot, and HubSpot.
ClickHouse
- Valuation
- $15B
- Employees
- 500+
- Replaced
- Marketo
Plaid
- Valuation
- $8B
- Employees
- 1,500+
- Replaced
- Marketo
Webflow
- Valuation
- $4B
- Employees
- 1,500+
- Replaced
- Iterable
Veriforce
- Valuation
- $1.2B+
- Employees
- 1,800+
- Replaced
- Pardot & Marketing Cloud
Productboard
- Valuation
- $1.7B
- Employees
- 500+
- Replaced
- Marketo
BuildOps
- Valuation
- $1B
- Employees
- 600+
- Replaced
- HubSpot
ACV Auctions
- Ticker
- NYSE: ACVA
- Employees
- 3,200+
- ARR
- $1B
AMCS
- Valuation
- €2B
- Employees
- 1,300+
- Replaced
- Pardot
Workflows decide by step. Plays decide by person.
On day 12, everyone in the nurture gets the same email. A Play checks what you know about each person first, then decides whether it goes out, when, or what goes instead.
Booked a pricing call for Thursday Chili Piper 
Got the webinar invite this morning Conversion 
Built 3 workflows in the trial Snowflake 
Deal in Negotiation Salesforce No opens in 60 days Conversion 
Just changed jobs ZoomInfo Same email to everyone. It fit one of them.
How a Play works.
You set the goal and the rules. The Play works every contact and account toward it, and logs every decision it makes.
Brief
Get evaluators at open enterprise deals into a technical deep dive with their team. Warm up the rest of the group with ads and 1:1 pages, one email a week at most.
You set the goal
Write the brief in plain language, pick the audience, and choose the emails, pages, and ads the Play can use.
Wake up when a contact
Signals wake it up
Choose the events that start a turn: page visits, form fills, email engagement, Salesforce changes.
Dana is building the case for her team, and 2 pricing visits this week say she's close.
It plans what's next
It reads everything Conversion knows about the person and the account, then plans what they get next and when.
Every decision is logged
Each decision lands in the contact's log with its reason, and any of them can be reversed from there.
What a Play does.
For every contact, a Play picks the day, the message, and the channel, or skips the email entirely.
See it on your dataMoved One definition of every metric to Thursday so Dana doesn't get 2 emails tomorrow. Stack teardown is already going out, and she opens about 1 email a day.
Up next
One Play. The whole buying group.
An account Play plans for the whole buying group at once: who hears what, in what order, and when. Click anything on the board to see the reasoning behind it.
Get Linear through Tom's security review on Friday.
Why this decision
Queued first for Dana. She's the champion and forwards what matters, so the rest of the team hears after she has it.
Moved from Tuesday to Thursday so Dana doesn't get 2 emails in one day.
Built around the data models Wei owns, and timed 2 days after Dana's so they don't land together.
Added to the engineering leaders ad audience, so Owen sees the story on LinkedIn while his team evaluates.
A cost page instead of the product tour. Grace signs off on budget and has never opened a product email.
Skipped because Tom's security review with Marcus is Friday. Marcus was alerted in Slack.
Queued for Friday afternoon, right after the review, with answers to the questions Tom sent Marcus.
Skipped because Dana already forwards it to Shiela.
Added to the finance leaders ad audience instead, so Shiela sees the cost story on LinkedIn without another email.
A Play works inside your rules.
Every limit you run today still applies. You see everything a Play does, and you can undo any of it.
Your workflows keep running
Blasts and workflows run the way they do today. Give an email a window, say whether it can be skipped, and the Play picks the moment inside it.
Communication limits and restrictions are enforced
Frequency caps, consent, and suppression lists apply to every email a Play touches, and an email you mark as required always goes out.
You choose what needs approval
Set each action to Auto, Ask first, or Off. Pin any email to a time, cancel it, or reverse a decision from the contact's log.
Common questions
What marketing ops leaders ask before they let an agent decide what goes out.
A Play is an AI agent that works every contact and account in an audience toward the goal you set. It decides what each person gets and when, personalizes emails and pages, takes actions like ad audience changes and Slack alerts, and records every decision with its reason.
A workflow does the same thing for everyone who reaches a step. A Play decides for one person at a time. It works on top of your workflows: their emails land on the same queue, and for any email you give room to, the Play picks the moment or decides it should not go.
Agents do work for your team, like building a campaign from a Slack brief or checking an email before it goes out. Plays work on your contacts and accounts, deciding what each one receives. Both run on the same context layer.
Both emails land on that person's queue. The Play sees them together and spaces them out, or decides one is not worth sending, inside your communication limits.
Yes. Every contact has a queue that shows every email coming from every blast, workflow, and Play, along with what already went out.
Everything in Conversion's context layer: Salesforce records and opportunities, warehouse tables, product events, website visits, email engagement, and call notes. Each decision shows what it was working from.
No. A Play decides inside your communication limits for every email, whether a blast, a workflow, or the Play itself put it there. Operational blasts and emails, like account notices or event logistics, still go out regardless of any Play and don't count toward your limits.
See a Play work your accounts.
Bring a target account list. We'll show you what a Play would do for every contact on it, and why.