Recipes: ready-made automations

A recipe is a ready-made automation for a shop or a site: who it is for, what it sends and when, already wired across the Monfri services. You pick one, check its few settings and switch it on — Monfri builds the rest.

What a recipe is made of

Behind every recipe there are three pieces, created for you when you launch it:

• an audience in CDP — a segment, such as Cart abandoners, or an event, such as Order Completed;
• a flow in Automation — the steps, the waits between them and the checks (has an e-mail address? has the person ordered meanwhile?);
• e-mail templates in Push — 63 ready e-mails in English and Bulgarian, added to every workspace: E-mail templates.

The e-mails go out from your workspace's sender — your own domain once it is verified, else your Monfri address — under your shop's name, which is your site's domain (for example Myshop.com). Every link carries utm_campaign=recipe-…, so the visits show in your analytics. Three recipes — abandoned cart, abandoned checkout and product abandonment — also send one web push to a shopper who has no e-mail address but subscribed to your notifications: Web push.

Where to find them

• Dashboard → Recipes — the recipes that fit your business. View details shows every step with its timing; Preview all content opens the recipe.
• Recipes (/recipes) — the whole catalogue, one card each.
• The setup guide's last step suggests a few to switch on at once.

A recipe's own page has its settings, its results and the buttons to pause it: Launch, test, pause and stop a recipe.

The card states

Owners and admins of the workspace launch, pause and remove recipes; members see them read-only.

Marketing e-mails and order e-mails

Most recipes send marketing — reminders, offers, newsletters. Five do not: Order confirmation, Shipping confirmation, Order delay reassurance, Post-purchase thank you and Newsletter signup welcome are mail the customer expects. Consent and unsubscribes do not stop them, and the frequency cap never holds them back.

For marketing e-mails:

• a person who unsubscribes from any of your e-mails gets no more of them, from any recipe: Unsubscribes;
• they count against the frequency cap, if you set one;
• with Marketing consent for recipe emails switched on, they go only to people who gave marketing consent. The newsletters always need it.

Most series also stop as soon as the person orders.

Settings for all recipes

In the Hub's Workspace settings: Workspace settings.

• Email language — English or Bulgarian; a recipe can also have its own, on its page.
• Quiet hours for recipe emails — recipe e-mails that fall inside the window wait until it ends, in the workspace's time zone. The order confirmation, the shipping notice and the signup discount never wait. Set the workspace's time zone first — in UTC the window is three hours off Sofia time in summer.
• Maximum one recipe email every … hours per contact — stops several recipes reaching the same person at once (0 = no limit). Only marketing e-mails count; the five order e-mails are never held back.
• Marketing consent for recipe emails — off by default. Switched on, the behavioural recipes reach only contacts who gave marketing consent; on a typical shop that is well under a tenth of the list.
• Postal address for e-mails — shown in the footer of marketing e-mails, as the law requires.

A change here reaches a recipe the next time it is activated: open the recipe and click Save & re-activate.

The catalogue

• Welcome and sign-up
• Abandoned carts and browsing
• Orders and delivery
• Loyalty and repeat purchases
• Winning customers back
• Price drop, back in stock, wishlists and sales
• Newsletters
• The daily log page in Pages

If something doesn't work

See Recipe requirements for what each recipe needs, and When Automation does not work.