Marketing automation
EmailPro automations start from something a customer did, such as signing up, abandoning a cart, replying on WhatsApp or having a deal won, and then wait, check conditions and send email, SMS or WhatsApp, or act in the CRM. Each automation has a goal: the moment it is met, the person leaves. Before you switch one on, you see how often it would have run on your own history.
One builder for marketing journeys and CRM workflows, because a customer does not care which department sent the message.
Signups, list joins, tags, a date field such as a birthday, inactivity, purchases, abandoned carts, product views, custom events, WhatsApp replies, social messages and comments, lead scores crossing a threshold, and CRM events.
A step sends an email, a text or an approved WhatsApp template, or chooses between them on a condition, for example a text only to people who did not open the email within two days.
Create a task, move a lead, open a ticket, notify the owner or create a payment link for a person to send. No step can charge a card by itself.
Set the goal, such as a purchase, a reply or a won deal, and anyone who reaches it leaves the automation. The report counts conversions with the step they were on and how long it took.
Replay the trigger over the last 30 days, run the automation on a real contact as a dry run, and see what that person would receive and when.
Each activation and each save of a live automation is a numbered version. People already inside finish the version they started; new entrants take the new one; rollback is one action.
Six automations that pay back quickly, and the trigger that starts each one in the builder.
| Automation | Trigger | What it does |
|---|---|---|
| Welcome series | Signup or list join | A welcome at once, an offer two days later only if they have not bought, a tip after a week |
| Abandoned cart | A cart started and not completed | A reminder after an hour, then a text to people who did not open the email |
| Win-back | Inactivity, for example 90 days without a purchase or an open | One message with a reason to return; no response means leaving the active segment |
| After purchase | A completed order | Confirmation, a how-to guide and a review request two weeks later |
| New lead follow-up | A lead created from a form or an AI agent | Assign an owner, create a call task, and send a WhatsApp template to leads who gave WhatsApp consent |
| Late ticket escalation | A service ticket that breached its target | Notify the owner, add a note to the ticket and create a follow-up task |
Tell your AI assistant what you want, for example a welcome series with an offer after two days, or open the builder and add a trigger, waits, conditions and steps.
Choose the event that means the automation succeeded. People who reach it leave, so nobody is asked whether they are still interested a day after they paid.
See how many times it would have run in the last 30 days and for how many people, then dry-run it on a real contact.
Switch it on. The report shows entries, completions, conversions and revenue, and you can pause, edit into a new version or roll back at any time.
The common failure of marketing automation is not a missing template. It is an automation that fires nine hundred times when its author expected twice a week, an edit that changes the path of forty people already halfway through, or a reminder that reaches someone who bought yesterday. Each of those is prevented here by design rather than by care.
Simulation answers the first: before launch you see, from your own history, how often the trigger would have fired. Versions answer the second: an edit never changes a run in flight, because every person remembers the version they started on. Goals answer the third: the moment the goal is met, the person leaves.
An AI assistant can build an automation from one sentence through the MCP server, but it is saved as a draft and a person activates it. Unsubscribing removes a person from every automation at once, and the send calendar holds marketing messages at night, on Shabbat and on holidays you configure.
Three situations where it will not fit, and we would rather say so here.
This builder automates customers: messages, CRM records and the events around them. Moving data between dozens of unrelated business apps is what integration platforms do; connect them through webhooks and the API instead.
A WhatsApp step sends only approved templates and only to contacts who opted in to WhatsApp. If most of your list never agreed, the step will skip them by design.
Automations run by themselves, but goals and reports only help if someone reads them each month. An automation nobody reviews keeps sending last year's offer.
Clear answers
Open an account, import a list with its consent records and connect one channel. Nothing is sent until a person approves it.
Open an accountExplore the current workspace
The builders, CRM and operational tools now share more of the journey. Start with a draft, review the next action, and follow the recorded result in the same workspace.
Edit in the page itself, switch between desktop, tablet and phone, and review changes before publishing. Pages, versions and professional kits use the shared canvas in Brand My Inbox and EmailPro.
Forms can create CRM inquiries. Joining a mailing list requires a separate consent choice.
Explore this capability: A canvas for websites and landing pages
Work at real reading widths, edit text in the email, reorder blocks and inspect dark-mode and mail-client simulations. Keep the landing page and campaign connected through the supported conversion tools.
A simulation is not an inbox test. Review recipients, exclusions and sender identity before sending.
Explore this capability: Design the email in the email itself
Connect contacts, companies, deals, service requests and projects. Use owners, queues, tasks, deliverables and approvals to see who does what next.
Visibility follows roles and record access. Inquiry forms do not grant marketing consent.
Explore this capability: Customer work beyond a contact list
What each tool does, and what needs a connection
Build event-driven steps, review dependencies and simulation results, and inspect runs and delivery failures. Improvement proposals require review before applying a new version.
Simulation shows configured behaviour; it does not prove a provider will complete a live action.
Track deliverables, review requests, exceptions, dated hours and retainer periods. Compare assignment and deadline scenarios before changing the project.
Scenario results are estimates based on the recorded inputs, not guaranteed profit or capacity.
Give assistants approved company and project context. Review sources, refresh status and access rather than copying customer information into every prompt.
Answers depend on source quality and the permissions of the person asking.
Review the proposed action, scope and cost. Follow the request, plan, approval, tool call and recorded effect; supported MCP tools use the same access rules.
Some actions remain human-only. MCP coverage is documented per tool, not promised for every screen.
Use customer journeys, campaign attribution and recorded outcomes. Search and AI visibility distinguish appearances, citations, referrals and conversions.
Google Analytics needs authorised setup; search imports and manual experiments are not live ranking or citation guarantees.
Use availability, meeting pages and the coaching kits. Link an existing payment request to the appointment and keep the customer record in context.
Google Calendar and payment providers need authorisation. Linking a request does not charge the customer or make payment a booking condition.
Email uses the monthly plan allowance. Israeli SMS uses verified prepaid packages; international SMS and calling use the wallet. SMS counts parts, not just recipients.
An own-provider account is separate. Provider charges and connection requirements still apply.
Connect supported providers, the WordPress lead plugin, Zapier or Make adapters, and signed webhooks. Inspect connection health and failed webhook deliveries.
Installation and authorisation are required. Marketplace publication is not claimed.
Export supported fields, pipelines, modules, lists, segments, templates, forms and automation definitions. Preview import compatibility before writing.
Structural export is not a full backup or a promise that every external platform can import it.
Connect campaigns, creator codes, orders, refunds and gifting with supported store data. Keep client review, project deliverables and retainer work in the same operating context.
Store connections and client-portal access require setup and the relevant entitlement. Attribution is based on recorded data, not guaranteed sales.
Run the supported business-task evaluations and review saved results, failures and model cost. Inspect media review and cleaning status before using uploaded content.
An internal evaluation is not an independent security audit. Media cleaning and external providers depend on the configured runtime.
Check the plan, permissions and connection requirements before activation.