Skip to main content
New Introducing Orchestrator Learn more
Introducing Orchestrator

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.

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

Paragraph
Describe what Orchestrator should do for one contact at a time...

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.

Enrolled audience Open enterprise pipeline
Can use Email1:1 pagesAd audiencesCampaigns

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

Reschedule emails Move an email to a better day or time.
Change email copy Rewrite copy for the person reading it.
Hold back emails Skip an email that doesn't fit right now.
Add to ad audiences LinkedIn, Google, and Meta audiences.
Enroll in campaigns Add to a campaign and set the status.

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 Whitfield Director of Analytics · Linear
Plan Reading… Updated just now

Dana is building the case for her team, and 2 pricing visits this week say she's close.

Add to Mid-funnel ads Today Keeps the buying group warm while Dana builds the case.
Build a 1:1 page for Linear Wed Around the metrics Dana asked about on the call.
Teardown invite Tentative Mon 10:00 AM Only if Dana opens the page first.

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.

Decisions from today 14 decisions 15 decisions
Added to Mid-funnel ads 9:42 AM Audience · Evaluation to deep dive 2 pricing visits this week.
Added to Q4 Evaluation campaign 9:12 AM Campaign · Evaluation to deep dive Linear's deal moved to evaluation in Salesforce.
Built a 1:1 page for Linear 8:31 AM Asset · Evaluation to deep dive Around the data models Wei owns.
Rescheduled Metrics guide 8:04 AM Rescheduled · Evaluation to deep dive Dana already gets the webinar recap on Tuesday.

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 data
Dana Whitfield Director of Analytics · Linear
Queue Decisions Variants Memory
Woke up · Website Visited /pricing twice this week 2m ago
Decisions from today
Rescheduled the metrics guide to Thursday Rescheduled · Enterprise Pipeline 9:42 AM

Moved 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

Stack teardown Tomorrow
One definition of every metric Rescheduled Thu 10:30
Accounts

Orchestrate the whole buying group together.

On an account, Orchestrator understands the full context across every contact and brings it into each decision.

Linear Evaluation
Buying group Decisions Variants Activity
Person Mon 22 Tue 23 Wed 24 Thu 25 Fri 26
Dana Whitfield Director of Analytics
Wei Zhang Analytics Engineer
Owen Brooks VP Engineering
Grace Larsen CFO
Tom Iverson Head of Security
Shiela Chen Director of Finance
Account plan Updated 5m ago

Get Linear through Tom's security review on Friday.

Stack teardown Tue Dana first. She forwards it on.
Cost page Wed Grace, instead of the product tour.
1:1 page Thu Wei, 2 days after Dana.
Security overview Fri Tom, right after the review.

Reasoning

Stack teardown · Dana Tue

Queued first for Dana. She's the champion and forwards what matters, so the rest of the team hears after she has it.

Metrics guide · Dana Thu

Moved from Tuesday to Thursday so Dana doesn't get 2 emails in one day.

1:1 page · Wei Thu

Built around the data models Wei owns, and timed 2 days after Dana's so they don't land together.

Exec ads · Owen Wed

Added to the engineering leaders ad audience, so Owen sees the story on LinkedIn while his team evaluates.

Cost page · Grace Wed

A cost page instead of the product tour. Grace signs off on budget and has never opened a product email.

Product tour · Tom Mon

Skipped because Tom's security review with Marcus is Friday. Marcus was alerted in Slack.

Security overview · Tom Fri

Queued for Friday afternoon, right after the review, with answers to the questions Tom sent Marcus.

Metrics guide · Shiela Tue

Skipped because Dana already forwards it to Shiela.

Finance ads · Shiela Wed

Added to the finance leaders ad audience instead, so Shiela sees the cost story on LinkedIn without another email.

Control

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.

FAQ

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.