Set up AI marketing for new experience launches

Follow these steps

1. 01

   Open AI Employee → New event launch, or Settings → AI replies & campaign limits → Manage house launch defaults.

2. 02

   Enable Let AI Employee check events and prepare engagement campaigns. Decide whether to include eligible experiences already published that are still upcoming.

3. 03

   Choose WhatsApp or Email and Review every batch or Autopilot within saved rules. Choose Past customers only or Relevant house audience only when you authorize that broader eligible audience.

4. 04

   Set maximum contacts per batch, maximum batches per experience, total experience campaign budget and wait between batches. Add accurate message instructions.

5. 05

   Read the authorization checkbox and save the rules. When setting up a newly created experience, Save rules & prepare this event enrolls that experience under the reviewed settings.

6. 06

   Publish an eligible future experience or review the enrolled experience's launch status. Open Review batch & results to inspect its audience, campaign and outcome.

7. 07

   Use Pause launch or Stop future batches if needed. Review Why Polar made each decision for stop/pause/expansion reasons.

Good to know

• The current UI bounds each batch to at most 500 contacts and experience launches to at most 10 batches; lower saved limits still apply.
• Launch defaults are off until authorized. A shared monthly campaign limit can further constrain individual campaigns and launches.
• WhatsApp Autopilot reuses approved templates; new wording needs review. Email Autopilot can use factual reviewed context within the saved rules.
• No discounts are invented. Events with unknown inventory or unsupported multiple occurrences pause for review.
• Editing or republishing the same experience does not create an unlimited set of fresh launches.

If something isn’t working

• Event launch not enrolled? Ensure the experience is published with a future date and launch rules were enabled/saved. Inquiry forms are not experience-launch targets.
• Waiting for audience synchronization? Finish/review the customer-history reconciliation before relying on selection.
• Inventory unknown or full? Review experience capacity; no further batch should be assumed eligible.
• Launch has earlier saved rules? Review its existing authorization/campaigns rather than assuming new defaults overwrite already authorized work.
• Pause cannot recall provider-submitted messages. Stop prevents future batches; existing provider delivery can still complete.