An agent on every contact.
Orchestrator is a long-horizon AI agent that sits across every contact and builds the ideal customer journey for each one. It chooses the next best action from the emails, ad audiences, and campaigns you give it.
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
Profound
- Valuation
- $1.8B
- Employees
- 400+
Ivanti
- Valuation
- $2B
- Employees
- 3,000+
Lattice
- Valuation
- $3B
- Employees
- 770+
ClickUp
- Valuation
- $4B
- Employees
- 1,200+
ACV Auctions
- Ticker
- NYSE: ACVA
- Employees
- 3,200+
- ARR
- $1B
Productboard
- Valuation
- $1.7B
- Employees
- 500+
- Replaced
- Marketo
Temporal
- Valuation
- $12B
- Employees
- 600+
- Replaced
- Marketo
Runway
- Valuation
- $5.3B
- Employees
- 250+
How Orchestrator works.
Historically, marketing operations teams have reached customers through a maze of workflows, triggers, and complicated logic. Orchestrator evaluates everything scheduled for a contact across your workflows and campaigns, and automatically builds the ideal journey for each one.
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.
Create a clear goal
Write the goal in plain language, like getting evaluators into a technical deep dive or trial users to a first workflow, and pick the audience it applies to.
Orchestrator can
Define the actions it can take
Choose what Orchestrator is allowed to do for a contact: reschedule or hold emails, change copy, add to ad audiences, enroll in campaigns, and alert owners.
Dana is building the case for her team, and 2 pricing visits this week say she's close.
Adjusts the journey based on what matters
Orchestrator reads everything Conversion knows about the person and the account. A pricing visit, a booked demo, or a deal changing stage changes what they get next and when.
Complete auditability and traceability
Every decision is recorded in the contact's log with its reason and can be reversed there. The Upcoming page shows the same for the whole audience: what's going out, and what was moved or held.
What Orchestrator does.
For every contact, Orchestrator weighs every action available and chooses the next best one to reach your goal.
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
Orchestrate the whole buying group together.
On an account, Orchestrator understands the full context across every contact and brings it into each decision.
Get Linear through Tom's security review on Friday.
Reasoning
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.
Built with guardrails and complete auditability.
Create clear guardrails for what Orchestrator can do, and keep a complete record of every decision it makes.
Runs on your blasts and workflows
Every blast and workflow email lands on the contact's queue. Set a delivery window and mark an email required or skippable, and Orchestrator schedules it inside those settings.
Communication limits are enforced
Frequency caps, consent status, and suppression lists are checked on every email before it goes out. An email marked required is always delivered.
Approval settings for every action
Set each action to Auto, Ask first, or Off. Pin an email to a time, cancel it, or reverse a decision from the contact's log.
Common questions
How Orchestrator makes decisions, what it can change, and how it runs alongside your existing workflows.
Orchestrator is a long-horizon AI agent that works across a group of contacts to optimize toward a specific goal. Using the list of actions your marketing ops team provides, it can change messaging, reschedule or swap the emails a person will receive, and build a customized journey for every contact, all in real time.
A workflow runs fixed logic: everyone who reaches a step gets the same action. Orchestrator evaluates each contact against your goal and chooses the next best action from the ones you allow. It runs on top of your workflows: their emails land on the contact's queue, and Orchestrator schedules, swaps, or holds each one inside the windows you set.
Agents do work for your team, like building a campaign from a Slack brief or checking an email before it goes out. Orchestrator works on your contacts, deciding what each one receives. Both run on the same context layer.
Both emails land on that person's queue. Orchestrator evaluates them together and spaces them out or holds one back, inside your communication limits.
Yes. Every contact has a queue that shows every email coming from blasts, workflows, and Orchestrator, along with what already went out. The Upcoming page shows the same for the whole audience, including what Orchestrator moved or skipped and why.
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. Orchestrator decides inside your communication limits for every email, whether a blast, a workflow, or Orchestrator itself put it there. Operational blasts and emails, like account notices or event logistics, still go out regardless of Orchestrator and don't count toward your limits.
See Orchestrator work your accounts.
Bring a target account list. We'll show you what Orchestrator would do for every contact on it, and why.
