Docs
OverviewPlatformPlatform APIA2P Messaging API
AI & MCP
Open dashboard
OverviewPlatformPlatform APIA2P Messaging API
AI & MCP
Getting started
  • Overview
  • Start guide
  • Project status
  • Concepts
AI
  • Iris
  • AI writing
  • Connect your AI (MCP)
Channels
    • Countries & coverage
    • Senders & registration
    • Essentials
    • Countries & availability
    • What is RCS
    • Senders & verification
    • Agent profile
    • Best practices
    • Acceptable use
    • SMS fallback
  • WhatsAppSoon
  • Compliance
  • Countries
    • Austria
    • Brazil
    • Canada
    • Colombia
    • France
    • Germany
    • India
    • Indonesia
    • Mexico
    • Netherlands
    • Peru
    • Singapore
    • Spain
      • Authorise the alias
      • Register directly
      • Without a certificate
      • Rejected alias
    • Ukraine
    • United Kingdom
    • United States
    • Other countries
Marketing
  • Campaigns
    • Creating a campaign
    • Targeting
    • Test sends
    • Delivery
    • Compliance
    • Managing campaigns
    • Campaign analytics
  • Flows
    • Building a flow
    • Templates
    • Triggers & entry
    • Sending messages
    • Waits
    • Branches
    • Contact updates
    • Goals & exits
    • Versions & publishing
    • Managing flows
    • Monitoring
    • Analytics
    • Limits
  • Sequences (legacy)
    • Managing sequences
    • Sequence analytics
Data
  • Audience
    • Contacts
    • Audience table
    • Segments
    • Attributes & events
  • Integrations & data sources
    • Managing sources
    • CSV import
    • API & webhooks
    • Event best practices
    • Integrations
      • Shopify
      • Klaviyo
      • WooCommerce
      • PrestaShop
      • Magento
      • HighLevel
      • Hotmart
      • ActiveCampaign
      • Zoom
      • Facebook Leads
      • Google Sheets
      • Google Contacts
      • MailChimp
      • MailerLite
      • Intercom
      • Make
      • Zapier
      • Activepieces
      • n8n
      • Pabbly Connect
      • OptiMonk
      • Paperform
      • StockAgile
      • Typeform
  • Consent
    • How consent works
    • Subscription attributes
    • Shared consent
    • Opt-outs
    • Manage via API
Analytics
  • Audience
  • Messages
  • Sales
  • Reports
Settings
  • Project settings
    • Brand profile
    • Senders
    • Short links
    • Unsubscribe links
    • Test numbers
    • Attribution
    • Project memory
  • Developers & Apps
    • API tokens
    • Third-party apps
    • Data access
    • Connected apps
  • Organization
    • General
    • Legal profiles
    • Team
    • Localization
  • Billing
    • Plans
    • Cost calculator
    • Balance
    • Invoices
    • Pricing
    • Account
    • Theme
    • Security
    • Notifications
    • Language & currency
DashboardSupportinstasent.com

Marketing · Flows

Flow templates

How the template gallery suggests ready-made flows for the events your project receives, and what each template sets up for you.

On this page▾
  • Where to find templates
  • Find the right template
  • Will it run? The readiness badge
  • Recommended and Used
  • What a card shows
  • The templates
  • What every template has in common
  • Welcome
  • Browsing
  • Abandoned checkout
  • Orders
  • Shipping
  • Loyalty
  • Win-back
  • Billing
  • Use a template
  • Choose the source
  • Sources that import their events every so often
  • Values the template asks for
  • Before you can publish
  • What to check before publishing
  • RCS send mode
  • Sample image on the first card
  • Message language
  • Billing
  • Related

A template is a complete flow that someone has already thought through for you: the event that starts it, the wait before the message, the text, who it can reach, how often the same contact can go through it and, where it makes sense, the purchase that stops it. Instead of a fixed catalogue, the gallery starts from the events your project actually receives: it offers the templates those events can start, tells you on every card whether the flow would run today, and recommends the best fits you haven't used yet.

Using a template is safe to try. It creates a new flow with a draft that opens in the editor; nothing is published, nobody enters and no message is sent until you review it, publish it and its entry is on. From that point it is an ordinary flow: you can change any step, add new ones or delete what you don't need, as described in Building a flow.

Where to find templates

The gallery is a panel titled Start from a template, with the subtitle Ready-made flows for the events your project receives. Using one only creates a draft. You reach it from several places in Marketing › Flows:

  • The View flows library button at the top of the flows list, next to Create flow. It appears when your project has at least one template to offer.
  • Create flow › From a template. Create flow opens a screen with the ways to start a flow, and From a template opens the gallery. The option carries a badge, such as 2 for you, that counts the templates marked Works now. If your project has no templates to offer, the option is not there. The same screen lists Recommended flows below the options: selecting a card opens that template's sheet directly. How the rest of the screen works is in Building a flow.
  • The empty list. While your project has no flows, the flows list shows that same screen, with From a template and the Recommended flows.
  • The Recommended flows block, at the end of a list that already has flows, below the table. It shows the templates that fit the events your project receives and that you haven't used yet; selecting a card opens that template's sheet, where Use template creates the flow. You can fold the block with the arrow next to its title, and it stays folded for that project in that browser. It isn't shown on narrow screens.

The project home suggests the same templates the gallery marks Recommended, each as a suggestion of its own that opens the gallery on that template; see Project status.

You need permission to edit automations to see the View flows library button and to use a template.

Find the right template

The gallery lists the templates that make sense for your project: those whose starting event your project receives or a connected source can send, and those suited to your type of business. Templates that would work today come first, then those that could work once their event arrives, then the rest; within each group, the ones you haven't used come before the ones you have.

To narrow the list:

  • Search templates looks in the title, the description, the starting event and the source names.
  • Data source (All data sources by default) keeps the templates related to one of your own sources: those that sent a template's event, including your API source, and your connected integrations.
  • Category filters by theme (Welcome, Browsing, Abandoned checkout, Orders, Shipping, Loyalty, Win-back, Billing, plus Ecommerce, which every commerce template carries), with the number of templates in each.
  • Hide used removes the templates you have already used.
  • Clear filters, the cross that appears once a filter is on, resets them all. The send mode isn't a filter and stays as it is.
  • Send mode appears only when your project has an active RCS sender; see RCS send mode.

In the filters column, Events you received in the last N days lists the starting events your project has received, most frequent first, with how many arrived. The number of days is your plan's window and the panel shows it. Select one or more events to keep only the templates that can start on them.

If the filters leave nothing, the gallery says No template matches these filters and offers View all templates. If your project has no templates at all, it says No templates for this project yet. They appear as your data sources send events.

Each card names its starting event and how many arrived in your plan's window.

Will it run? The readiness badge

A flow only starts when its event arrives. Each card already says how many of its starting events arrived in your plan's window (+10k past 10,000). Open a template to see how that event is doing in your project: its sheet shows a badge next to a short line with the detail.

BadgeWhat it meansDetail in the sheet
Works nowThe event that starts the template has arrived from one of your sources in the last 30 days (the last 15 days on projects with 20,000 contacts or more). A flow made from it would start running as soon as you publish it.How many arrived in the plan's window and when the last one came in.
No data yetOne of your connected integrations can send that event, but none has arrived so far.[source] can send [event], but none has arrived yet.
No recent activityThe event arrived earlier in the window, but not in the last 30 days. Check that the source is still connected and sending.The last [event] arrived on [date].
Won't triggerNone of your connected sources sends the event, so the flow would never start, however good its messages are. The first step is to connect a source that sends it.No connected data source sends [events], so it would never start.

Only connected integrations declare in advance which events they can send. If your events come through the API, a template can show Won't trigger until the first event of that type arrives, and then it moves straight to Works now.

A template whose starting event does arrive can still show No data yet when the source it would listen to doesn't send the event that stops it, such as the orders that end Abandoned checkout. Until that event comes from the same source, the template isn't marked Recommended.

Recommended and Used

  • Recommended marks up to three templates: the best fits among those whose event your project already receives and that you haven't used yet. The fit weighs the events you receive above anything else, and also your type of business, the event you count as a sale and the flows you already have. The Recommended flows blocks on the flows list and on the Create flow screen don't repeat the label on each card.
  • Used means a flow created from that template exists, whether it is published, paused or still a draft. An archived flow doesn't count, so after you archive one the template can be recommended again.

What a card shows

Besides the title, the description and the badges, each card summarises what the flow does:

  • The steps, in order: a fixed wait shows its length, a Smart delay shows as Best time or Best time after its minimum wait, and each message shows its channel as a badge (SMS, or an RCS badge next to the SMS one in RCS mode). If a template branches, the line stops at the split with Splits into and the number of branches, and adds the total number of messages it can send and the longest a contact can stay in it.
  • Stops on, followed by the events that end the flow early, such as an order.
  • The sources that sent its event, as icons. Hovering one tells you how many it sent, and the source the new flow will listen to says The flow will listen only to followed by its name.
  • Written for RCS, in RCS mode, on a template that has its own RCS version; see RCS send mode.

A flow made from a template always listens to one source, also for the events Instasent records itself, such as a new contact. When several of your sources send the event, the template picks the one best placed to send it (for orders, the shop that owns them; a source that has sent the event recently over one that hasn't) and the flow listens only to that one. That way, the same order relayed by a second tool doesn't start the flow twice. You can pick another source in the template's sheet before creating the flow (see Choose the source), or change it later in the trigger; see The trigger: who enters and when.

The templates

The catalogue grows over time, and the gallery only shows the templates that fit your project, so you may see fewer than this page describes. They are grouped by the moment of the customer's journey they cover, the same groups the gallery's Category filter offers.

Each message goes out under one of two consent policies. The messages that confirm something the customer has just done, or remind them of something they owe, use Basic: Thank you for your order, Shipping notification, Order delivered, Order canceled, Order refunded, SMS sign-up confirmation, Failed subscription payment and Unpaid invoice reminder. Every other template is marketing and uses No opt-out. If you add an offer to a Basic message, it becomes marketing, so change its policy too. Who each policy reaches is explained in Compliance policies, and how it works on a flow message in Sending messages.

What every template has in common

  • Only contacts with a mobile phone number can enter. The trigger's audience is limited to them, so nobody enters a flow that could never message them.
  • Marketing messages wait in a Smart delay, except the ones that answer what the contact has just done or left unfinished. The Smart delay waits for each contact's best moment inside its window and has Follow marketing time-of-day laws on. A message that reacts to the contact's own action waits a short Fixed delay instead, so it arrives while that action is still fresh: Lead follow-up, Back in stock, Abandoned cart, the first message of Abandoned checkout and of Abandoned checkout with follow-up (and the help message the latter sends after a click), and Failed subscription payment. Confirmations go out right away, except Unpaid invoice reminder, which waits in a Smart delay inside the allowed hours. If no allowed moment fits inside a Smart delay's window, the contact leaves the wait through Unable to wait, which the template leaves empty, so that contact finishes the flow without the message. How each wait works is in Waits.
  • One message per contact, except Abandoned checkout, Abandoned checkout with follow-up and Second purchase offer, which send up to two, and Ask for a review in RCS mode, which can answer the star the contact taps with a second message. When a template branches, each branch can carry its own message, as in Win back customers, but a contact only goes down one of them.
  • Stop the run if the message can't be sent is on, so a contact whose message can't go out doesn't carry on through the flow.
  • One run at a time per contact. Simultaneous runs per contact is set to 1. If the starting event arrives again while the contact is still inside, that second entry is rejected and shows up in the flow's Didn't enter list; see Monitoring a flow.
  • Default entry limits unless the template says otherwise: no cap on how many times a contact can enter, with at least 5 minutes between two entries of the same contact. These settings are explained in The trigger: who enters and when.
  • A sender is pre-selected on every message when one can be chosen, and the texts are in your project's language (see What to check before publishing).

Templates without an exit event have no goal, so their analytics show no goal rate. If a sale is what success means for you (a welcome that leads to a first order, for example), add it in Goal & exit; see Goals and exits.

Welcome

Welcome new contacts
  • Trigger: Customer created / updated, with a condition that keeps only contacts who are new. It listens to one source, the one the sheet shows under Listens to, so it welcomes the contacts that source creates. When several of your sources create contacts, you can pick another one there. To welcome contacts from every source, set Data source to Any data source in the trigger once the flow is created. Contacts loaded through a CSV import don't start a flow; see Limits and safeguards.
  • Smart delay: As early as 5 minutes, As late as 8 hours, ranking strategy Recommended, timing preference Soon.
  • Message: welcomes the contact by first name and thanks them for joining. Policy No opt-out.
  • Goal & exit: none.
  • Limits: Once only, so each contact is welcomed once and never enters again, even if their data changes later.
Welcome without a purchase
  • Trigger: Customer created / updated, new contacts only, from the source the sheet shows under Listens to, as in Welcome new contacts.
  • Fixed delay of 14 days, then a Smart delay with As early as 5 minutes, As late as 3 days, ranking strategy Recommended, timing preference Relaxed.
  • Branch by an event the contact did: a contact with an Order created in the last 30 days, the order that created the contact included, ends the flow there; the rest get the message.
  • Message: asks the contact, by first name, whether they are still deciding and invites them to see what's new, with the link to your Store website. Policy No opt-out.
  • Goal & exit: exit event Order created, used as the flow's goal.
  • Limits: Once only.
SMS sign-up confirmation
  • Trigger: Customer subscribed, only when the contact subscribes to your SMS.
  • Message, right away: thanks the contact for subscribing and explains how to unsubscribe, with the unsubscribe text and link for the contact's country. Keep that part. Policy Basic: it confirms the sign-up the contact just made, so it carries no offer and no link to your store.
  • Goal & exit: none.
  • Limits: the defaults.
Lead follow-up
  • Trigger: Form submitted, or Deal added when the deals of your CRM reach your project.
  • Fixed delay of 5 minutes, so the lead hears back while the request is fresh.
  • Message: tells the lead, by first name, that their request has arrived and that you will call them soon. It has no link. Policy No opt-out. If your team answers leads another way, change the promise.
  • Goal & exit: exit events Meeting registered and Deal won, both used as the flow's goal.
  • Limits: Minimum time between enrollments of 30 days. The gallery offers it to businesses that work with leads, such as B2B, education or software, rather than to online shops.

Browsing

Viewed product reminder
  • Trigger: Product viewed.
  • Smart delay: As early as 4 hours, As late as 12 hours, ranking strategy Purchase intent, timing preference Balanced. A product view is a mild signal, so there is no rush: the reminder arrives a few hours later, at a good time to send.
  • Branch by contact field: only contacts who have bought before, with one order or more, get the message; the rest end the flow there, since a product view alone says little.
  • Message: reminds the contact, by first name, of the product they viewed, by its name, with the link to that product when your source sends it, and to your Store website otherwise. Policy No opt-out.
  • Goal & exit: Product added to cart and Checkout started end the flow, so the cart and checkout reminders take over, without counting as a goal; Order created ends it and counts as the goal.
  • Limits: Minimum time between enrollments of 30 days.
Campaign click follow-up
  • Trigger: Campaign click / call to action.
  • Smart delay: As early as 20 hours, As late as 2 days, ranking strategy Purchase intent, timing preference Balanced.
  • Message: asks the contact, by first name, whether they are still thinking about what they saw, with the same link they clicked. Policy No opt-out.
  • Goal & exit: exit event Order created, used as the flow's goal.
  • Limits: Minimum time between enrollments of 7 days, so contacts who click often aren't followed up after every campaign.
Back in stock
  • Trigger: Back in stock restock, which some shops send when a product a contact was waiting for is available again.
  • Fixed delay of 5 minutes, so the news arrives while it is fresh.
  • Message: tells the contact, by first name, that the product, by its name, is back in stock, with the link to that product when your source sends it, and to your Store website otherwise. Policy No opt-out.
  • Goal & exit: exit event Order created, used as the flow's goal.
  • Limits: the defaults.

Abandoned checkout

Abandoned cart
  • Trigger: Product added to cart.
  • Fixed delay of 1 hour, so the reminder arrives while the cart is fresh.
  • Message: tells the contact, by first name, that their cart is saved, with the link to their own cart taken from the event. If your source doesn't send the cart link, replace it with your store's link. Policy No opt-out.
  • Goal & exit: Checkout started ends the flow so that Abandoned checkout takes over, without counting as a goal; Order created ends it and counts as the goal.
  • Limits: Minimum time between enrollments of 1 day.
Abandoned checkout
  • Trigger: Checkout started, from the source that sends your checkouts. When a source only sends Checkout abandoned, the flow starts on that one.
  • Fixed delay of 1 hour, so the reminder arrives while the checkout is fresh.
  • First message: tells the contact, by first name, that they left something in their cart, with the link to finish the order taken from the checkout event. Policy No opt-out.
  • Second Smart delay: As early as 20 hours, As late as 26 hours after the first message, ranking strategy Purchase intent, timing preference Balanced.
  • Second message (on Wait complete): tells the contact that their order is still saved and ready to finish whenever they like, with the same checkout link. It carries no incentive; add your code to the text if you want to offer one. Policy No opt-out.
  • In RCS mode, each message is a card with a Finish my order button that opens the contact's own checkout, and the SMS fallback keeps the link in the text; see RCS send mode.
  • Goal & exit: exit event Order created, from the same source as the trigger, with Use this event as the flow's goal checked. A contact who orders at any point leaves the flow, so nobody who has already bought receives a reminder; an order placed after the first message counts as the flow's goal. The exact counting rule is in Goals and exits.
  • Limits: Minimum time between enrollments of 1 day, so a contact who starts several checkouts in a few hours goes through the flow once.
Abandoned checkout with follow-up
  • Trigger: Checkout started, from the source that sends your checkouts, or Checkout abandoned when a source only sends that one, as in Abandoned checkout.
  • Fixed delay of 1 hour, so the reminder arrives while the checkout is fresh.
  • First message: tells the contact, by first name, that their order is waiting just as they left it and is one step from done, with the link to finish the order taken from the checkout event. Policy No opt-out.
  • Wait for activity of up to 20 hours for a click on that link. The follow-up depends on what the contact did.
  • After a click (Any link click): a contact who opened the link and still hasn't ordered gets, after a Fixed delay of 2 hours, a message asking whether they have any questions about their order and saying it is saved so they can finish it whenever they like, with the same link. Policy No opt-out.
  • Without a click (No interaction): a Smart delay with As early as 5 minutes, As late as 8 hours, ranking strategy Purchase intent, timing preference Balanced and Follow marketing time-of-day laws on, then a reminder that their order is still saved, with the same link. Policy No opt-out. So a contact receives at most two messages: the first one and one follow-up.
  • In RCS mode, each message is a card with a Finish my order button that opens the contact's own checkout. Right after the first message, a Wait for delivery split by channel decides how the flow goes on. A contact who got it by RCS (Delivered · RCS) waits for a tap on the button or a click, and their follow-up is again an RCS card with its SMS fallback. A contact who got the SMS fallback (Delivered · SMS) waits for a click on the link in the text, and their follow-up is sent by SMS only. If the first message isn't delivered, the flow ends there. Why a tap is only awaited after an RCS delivery is explained in Waits.
  • Goal & exit: exit event Order created, from the same source as the trigger, used as the flow's goal. A contact who orders at any point leaves the flow, so nobody who has already bought receives a follow-up.
  • Limits: Minimum time between enrollments of 1 day.
  • This one or Abandoned checkout. The gallery offers both, and they start on the same checkout, so use one of the two: a contact who enters two published flows gets the messages of both (see What Flows doesn't limit). Once you have a flow made from one of them, the gallery ranks the other one lower.

Orders

Thank you for your order
  • Trigger: Order created, from the source that sends your orders.
  • Message, right away: thanks the customer by first name for their order, with the order number taken from the event, and says it is being prepared. Policy Basic, because it is an order confirmation rather than marketing.
  • Goal & exit: none.
  • Limits: the defaults, so each new order sends its thank-you as long as it doesn't arrive within a few minutes of the previous one.
Order canceled
  • Trigger: Order cancelled.
  • Message, right away: confirms to the customer, by first name, that the order, by its number, has been canceled, and says that a paid order will be refunded. Adapt that sentence to your refund policy, or remove it. It has no link. Policy Basic.
  • Goal & exit: none.
  • Limits: the defaults.
Order refunded
  • Trigger: Order refunded.
  • Message, right away: confirms to the customer, by first name, the refund of the order, by its number, and says the money may take a few days to arrive, depending on their bank. It states no amount, because partial refunds start it too. Policy Basic.
  • Goal & exit: none.
  • Limits: the defaults.

Shipping

Shipping notification
  • Trigger: Order shipped.
  • Message, right away: tells the customer, by first name, that the order, by its number, is on its way, with the carrier and the tracking link taken from the event. If your source doesn't send one of them, remove it from the text. Policy Basic.
  • Goal & exit: none.
  • Limits: the defaults.
Order delivered
  • Trigger: Order delivered, so it only runs when your source reports deliveries.
  • Message, right away: tells the customer, by first name, that the order, by its number, has arrived. It has no link and no offer. Policy Basic.
  • Goal & exit: none.
  • Limits: the defaults.
Ask for a review
  • Trigger: Order delivered if deliveries reach your project; if only shipments do, Order shipped. The card shows which one your flow will use.
  • Smart delay: As early as 7 days, As late as 10 days, ranking strategy Engagement, timing preference Balanced, so the customer has had time to use the product. Change the window if your product takes longer.
  • Message: tells the customer, by first name, that you hope they are enjoying the order and asks for a review, with the link you give in Review link. Policy No opt-out.
  • In RCS mode, the message asks how the order went with three Quick reply buttons, ⭐⭐⭐⭐⭐ Love it, ⭐⭐⭐ It's fine and ⭐ Didn't like it. A Wait for delivery split by channel follows: only contacts who got it by RCS (Delivered · RCS) wait up to 3 days for a tap. Those who got the SMS fallback already have the review link in the text and leave the flow, and so does a contact whose message isn't delivered. Each answer is sent right after the tap: Love it gets a message with a Leave a review button that opens your Review link, and Didn't like it gets an apology. It's fine, or no tap, ends the flow. Why the tap is only awaited after an RCS delivery is explained in Waits.
  • Goal & exit: none.
  • Limits: Minimum time between enrollments of 30 days, so a customer who orders often is asked at most once a month. A contact can only be in one run at a time, so a second delivery during the wait doesn't start another one.

Loyalty

Cross-sell after delivery
  • Trigger: Order delivered, or Order shipped when only shipments reach your project.
  • Smart delay: As early as 12 days, As late as 14 days, ranking strategy Recommended, timing preference Relaxed, after the review request's window, so the two messages don't arrive together.
  • Message: tells the customer, by first name, that you hope they are enjoying the order and invites them to find what goes well with it, with the link to your Store website. Point that link to a collection if you have one. It carries no incentive. Policy No opt-out.
  • Goal & exit: exit event Order created, used as the flow's goal.
  • Limits: Minimum time between enrollments of 30 days, so a customer who orders often gets this suggestion at most once a month.
Second purchase offer
  • Trigger: Order created.
  • Smart delay: As early as 1 day, As late as 2 days, ranking strategy Recommended, timing preference Relaxed.
  • Branch by contact field: only customers with exactly one order continue, so the offer reaches first-time buyers; anyone else ends the flow there.
  • First message: thanks the customer, by first name, for their first order and gives your discount code and percentage for the next one, with the link to your Store website. Policy No opt-out. The code and the percentage are yours to fill in; see Values the template asks for.
  • Wait for activity of up to 7 days for a click on that link. The follow-up depends on what the customer did.
  • After a click (Any link click): a customer who opened the link and still hasn't ordered gets, after a Smart delay with As early as 2 days, As late as 3 days, ranking strategy Recommended, timing preference Relaxed, a short reminder asking whether they saw something they liked and saying that their code is still active, with the same link. Policy No opt-out.
  • Without a click (No interaction): once the 7 days are over, a Smart delay with As early as 2 days, As late as 4 days, ranking strategy Recommended, timing preference Relaxed, then the offer presented in another way: the message asks how their order went and invites them to pick something new, with the code, the percentage and the same link. Policy No opt-out. So a customer receives at most two messages: the first one and one follow-up. In either follow-up, mention an expiry date only if your code has one.
  • In RCS mode, each message is a card with the code in its text and a button that opens your Store website: Go to the store on the first card and on the reminder, Pick something new on the offer. A tap on that button counts as a click on the link, and a contact who gets the SMS fallback clicks the link in the text, so the 7-day wait works the same on both channels and needs no Wait for delivery split; see Waits.
  • Goal & exit: exit event Order created, used as the flow's goal: a second order at any point ends the flow, so nobody receives a follow-up after using the code.
  • Limits: the defaults.
Replenishment reminder
  • Trigger: Order created.
  • Fixed delay of 25 days, then a Smart delay with As early as 5 minutes, As late as 2 days, ranking strategy Recommended, timing preference Relaxed.
  • Message: asks the customer, by first name, whether they are running low on what they ordered and invites them to order again, with the link to your Store website. Policy No opt-out.
  • Goal & exit: exit event Order created, used as the flow's goal. A new order ends the current run and starts a new one, so the 25 days always count from the latest order. It suits products that run out, such as cosmetics, food or supplements: change the days to your product's real cycle.
  • Limits: the defaults.
VIP customers
  • Trigger: Order created, on every order.
  • Smart delay: As early as 5 minutes, As late as 1 day, ranking strategy Recommended, timing preference Relaxed.
  • Branches: a contact who already has the vip tag ends the flow there (a branch by tag); a contact with 3 orders or more gets the vip tag and the message (branch by contact field); anyone else ends the flow. The tag is what makes it happen once per contact, so keep that step.
  • Message: thanks the customer, by first name, for ordering again and again and tells them they are now a VIP customer who will hear about everything new first. If you don't run early access for your VIPs, change that promise. Policy No opt-out.
  • Goal & exit: none.
  • Limits: the defaults. The vip tag can select those customers in a segment for your early-access campaigns; how a flow adds tags is in Updating the contact.

Win-back

Win back customers
  • Trigger: Order created, from the source that sends your orders.
  • Fixed delay of 60 days.
  • Branch by contact field: customers with 2 orders or more go one way, and everyone else, normally customers who have ordered once, goes the other.
  • Repeat customers (2 orders or more) get the winback-at-risk tag, then a Smart delay with As early as 5 minutes, As late as 3 days, ranking strategy Recommended, timing preference Relaxed, and a message telling them, by first name, that you miss them and inviting them to see what's new since their last order, with the link to your Store website. The tag lets you select these customers in a segment and treat them apart in your campaigns. A later order doesn't remove it; how a flow adds tags is in Updating the contact.
  • One-time buyers (everyone else) get the same Smart delay, then a message asking them, by first name, how their order went and inviting them to see what's new since then, with the link to your Store website.
  • Neither message carries an incentive, both use the policy No opt-out, and each contact receives only the one for their branch.
  • In RCS mode, each message is a card with a See what's new button that opens your Store website, and both cards show a sample image to replace with your own; see Sample image on the first card.
  • Goal & exit: exit event Order created, used as the flow's goal. A new order ends the current run and starts a new one, so the 60 days always count from the latest order. How an event can both end a run and start the next one is explained in Goals and exits. Change the days to your customers' buying cycle.
  • Limits: the defaults.

Billing

Failed subscription payment
  • Trigger: Payment, only payments that failed.
  • Fixed delay of 5 minutes, so the customer hears about it soon after the payment fails.
  • Message: tells the customer, by first name, that the payment could not be processed and gives the link to complete it, taken from the event. If your source doesn't send that link, remove it from the text. Policy Basic, because it is about the customer's own account.
  • Goal & exit: a Payment that succeeds ends the flow and counts as the goal, so a retry that goes through before the message sends nothing.
  • Limits: the defaults.
Unpaid invoice reminder
  • Trigger: Invoice, only invoices that are unpaid.
  • Smart delay: As early as 2 days, As late as 3 days, ranking strategy Recommended, timing preference Balanced. Change the window to your payment terms.
  • Message: reminds the customer, by first name, that the invoice, by its number, is still unpaid, with the link to view and pay it, taken from the event. If your source doesn't send that link, remove it from the text. Policy Basic.
  • Goal & exit: exit event Payment, used as the flow's goal.
  • Limits: the defaults. The gallery offers it to software and B2B businesses rather than to online shops.

Use a template

  1. 1

    Pick the card

    Open the gallery and find the template, with the filters or the event chips if you need them, or select it in Recommended flows. Selecting a card opens the template's sheet, with the flow's diagram and what it sets up.

  2. 2

    Check the source and the values

    In the sheet, check which source the flow will listen to under Listens to, and fill in the values the template asks for under Finish setting up, if any. Both are explained below.

  3. 3

    Click Use template

    A new flow is created, named after the template in the panel's language (for example Abandoned checkout). Its draft holds the template's trigger, steps, limits and, when the template has them, exit and goal. The template now shows Used.

  4. 4

    Review the draft in the editor

    The editor opens on the new draft. Nothing is published and the flow's entry is off, so no contact enters yet. You can rename the flow (the name is sent with the links in its messages; see Managing flows) and change anything on the canvas.

  5. 5

    Test and publish

    Run a test with one contact, then publish to everyone or to a small group first. Both are explained in Testing, publishing and versions. The first publish also turns the flow's entry on.

Choose the source

The sheet's Trigger block says what starts the flow (Starts on), which source it will listen to (Listens to) and whether that source is sending the event.

  • One source. Listens to shows it, with how many events it sent.
  • Several sources that have sent the event. Listens to is a list, one line per source with what it sent. The one the template picks is marked Recommended and comes selected; a source that sent the event a while ago shows the date of its last event. Select another one if your events should come from it.
  • None has sent it yet. If a connected integration can send the event, Listens to shows it with No events yet, and the flow will listen to it. If no source can send it, the sheet says No source sends it yet and offers to connect one or to send the event through the API.

Only sources that have actually sent the event are offered in the list. The exception is the gallery's Data source filter: if you opened the template with a connected integration selected there, the sheet listens to that integration, marked No events yet, until it sends the event. When a template can start on more than one event (such as Ask for a review or Abandoned checkout), the event can change with the source, and Starts on shows the one the flow will use.

The source selected when you click Use template is the one the flow listens to. The exit listens to the same source, or to every source when that one never sends the event that ends the flow.

Sources that import their events every so often

Some connections, such as Klaviyo, PrestaShop, Magento and HighLevel, don't send each event the moment it happens: Instasent imports their events every so often, and how often depends on your plan and on your account's activity. Flows go by when each event happened, but a purchase made after one import only arrives with the next one; how flows handle these sources is explained in Sources that import their events every so often.

That matters most for the templates that react to something the person has just done: Abandoned cart, Abandoned checkout, Abandoned checkout with follow-up, Viewed product reminder, Back in stock, Lead follow-up and Failed subscription payment. Their first wait is short, so an order placed in the meantime could still be on its way when the message is due, and the person would get a reminder about something they have already bought. When the source selected under Listens to works this way, the template takes care of it:

  • The template's sheet shows a warning next to the source, or next to the connection the sheet offers to connect. For a source that imports about every 90 minutes, it reads: This source doesn't send events the moment they happen: it imports them about every 90 minutes. So that what the person does in the meantime, such as buying, can stop the flow, this template's first wait is 90 minutes longer. If you change the waits, keep them longer than 90 minutes. The figures are those of your source.
  • The flow's first wait is lengthened by about one import interval, at most a day. That way the order, or whatever event stops the flow, arrives in time and ends the run before the message goes out. When the template's waits are already long enough, nothing is added, and the warning says instead: This template's waits already leave room for it.
  • The sheet shows the flow you will get. Its diagram and What it does show the waits as they will be on the source selected under Listens to, the longer first wait included. Selecting another source updates them.

The wait is lengthened once, when you click Use template. If you then change the waits, or change the trigger's Data source in the editor, nothing is adjusted again: keep the waits before the first message longer than the source's import interval. Flows already created keep their waits as they are.

Values the template asks for

Some messages need a value from you. Before the flow is created, the template's sheet shows them under Finish setting up, and it lists only the values the messages of the selected send mode use, so the same template can ask for more in RCS mode than in SMS mode:

  • Second purchase offer asks for a Discount code (for example, WELCOME10) and a Discount percentage, a whole number from 1 to 99 written without the % sign (Write a whole number from 1 to 99, without the % sign), in both send modes. Every message of the template uses them. They come empty, so they are yours to fill in.
  • Ask for a review asks for the Review link, the page where the customer leaves their review, in both send modes. It comes empty too.
  • Store website comes filled in with your brand's website, Taken from your project. Change it if this flow should open another page, such as a collection. In both send modes it is the link in the message of Welcome without a purchase, Viewed product reminder, Back in stock, Cross-sell after delivery, Second purchase offer, Replenishment reminder and Win back customers. In Viewed product reminder and Back in stock it is only used when the event doesn't send the product's own link.
  • In RCS mode only, Store website is also the page the card's button opens by default in Welcome new contacts, Lead follow-up, Campaign click follow-up, Abandoned cart, Abandoned checkout, Abandoned checkout with follow-up, Shipping notification, VIP customers, Failed subscription payment and Unpaid invoice reminder. Where the button opens the contact's own link (their cart, checkout, tracking or payment page), it opens the Store website when the event doesn't send that link.
  • Thank you for your order, Order canceled, Order refunded, Order delivered and SMS sign-up confirmation ask for nothing.

You can leave a value for later: the draft can't be published until it is filled in.

Before you can publish

On a draft made from a template, the editor shows a card, Before you can publish, with what is still left: a value to fill in (for example, Add your discount code) or a sender to choose (Choose who sends the SMS). Selecting a row opens that step. The card shows every time you open the draft while the flow has never been published and something is left, unless you close it with I'll do it myself or the cross, which hides it for that flow in that browser.

Finish it with Iris opens Iris with the request Help me personalize this flow for my business. Iris proposes the changes on the canvas, without saving. Reviewing, saving and publishing them is still up to you, as in Iris in the flow editor.

What to check before publishing

  • The sender of each message. Each message comes with a sender already selected when one can be chosen: your project's default sender for that channel if it is active, or your only active sender if you have just one. With several active senders and none set as default, the message is left without one so that you choose it (Choose who sends the SMS on the card). In RCS mode the RCS level is filled the same way, counting only RCS senders whose registration is approved in at least one country, and the SMS fallback gets an SMS sender. If your project has no active sender for a channel, that level is left without one too. Make sure the selected sender is the one you want for this flow.
  • The texts. They are a starting point written for any business; adapt them to your tone, remove what your source doesn't send (a tracking link, a carrier) and add an offer if you want one, keeping in mind that an offer makes a Basic message marketing. The message editor is described in Sending messages.
  • The source of the trigger and of the exit. They point to the source the template picked; change it if your events should come from another one.
  • The image of the first card, in RCS mode: replace the template's sample image with your own; see Sample image on the first card.
  • The waits and limits, if your customers' rhythm is different: a longer window for a review, a different number of days for a win-back. With a source that imports its events every so often, keep the waits before the first message longer than its import interval; see Sources that import their events every so often.

RCS send mode

Every template has an SMS version and its own RCS version. When your project has an active RCS sender, the gallery adds the Send mode switch with two options, shown as channel badges: SMS and RCS, whose tooltip reads RCS, with SMS when RCS can't reach the contact. In RCS mode, every message of the template is prepared as an RCS message with its SMS as the fallback and the same consent policy on both; the cards show the RCS badge next to the SMS one and Written for RCS. Each RCS version follows what its messages are for:

  • Marketing messages and reminders are a card with one button that opens the page the message is about, such as View my cart, Finish my order, Track my order or Update payment. The button opens the contact's own link when the event sends one, and your Store website otherwise. The link goes in the button and not in the card's text, where it couldn't be tapped; contacts who receive the SMS fallback get the link in the text. In several marketing templates the first card shows a sample image you replace with your own; see Sample image on the first card. How these buttons work is in Creating a campaign.
  • Order confirmations (Thank you for your order, Order canceled, Order refunded and Order delivered) are plain RCS text without buttons, so they stay service messages. SMS sign-up confirmation has one Unsubscribe button, which is how the contact unsubscribes in RCS.
  • Ask for a review asks with three star replies and answers the one the contact taps, as described in its entry under Shipping.

When your project has an active RCS sender, the gallery opens in RCS mode, and the Recommended flows blocks show the RCS version too. Switch to SMS before using a template if you want an SMS-only flow: the mode selected when you click Use template is the one the flow is created with. Without an active RCS sender, the switch doesn't appear and templates use SMS only. How the fallback decides between the two channels is explained in SMS fallback.

Sample image on the first card

In the RCS version of several marketing templates, the first card shows a neutral sample image: Welcome new contacts, Welcome without a purchase, Viewed product reminder, Back in stock, Abandoned cart, Abandoned checkout, Abandoned checkout with follow-up, Cross-sell after delivery, Second purchase offer, Replenishment reminder, VIP customers and Win back customers. It is there so the message looks finished in the preview, with the room an image takes on the card; it is not meant to reach your contacts.

Replace it with your own image before publishing. In the card's editor, the image carries the notice Sample image from the template: replace it with your own., and Replace opens your gallery. While a card still shows the sample image, the draft saves but the flow can't be published: the message step is listed among the problems that block publishing, with The card still shows the template's sample image: change it for your own. (see Fix what blocks publishing). The other cards of these templates carry no image; add one in the editor if you want. Win back customers sends a single card on each of its two branches, so both cards carry the sample image.

Message language

The template's messages are written in your project's language: in Spanish for a Spanish-language project, and in English for any other. The flow's name, like the gallery itself, follows the language of the panel.

If your plan includes messages in several languages, each message also carries the other language (English or Spanish) as a translation, and each contact receives the version in their own language; everyone else receives the main one. Translations are added in the message editor, one version per language; see Sending messages.

Billing

Using a template costs nothing: it only creates a draft. Once published, each message is billed according to the channel it goes out on, like any other send. In RCS mode, a message delivered by RCS is billed as RCS, and when the SMS fallback runs, the SMS conditions apply, as explained in SMS fallback. Test runs send real messages and are billed too; see Testing, publishing and versions.

Related

Building a flow

Create a flow, add and move steps, save the draft and fix what blocks publishing.

Testing, publishing and versions

Test a draft with one contact and publish it to everyone or to a small group.

Project status

Where the project home suggests the same recommended templates.

Last updated October 27, 2026

PreviousBuilding a flowNextTriggers & entry
  • Where to find templates
  • Find the right template
  • Will it run? The readiness badge
  • Recommended and Used
  • What a card shows
  • The templates
  • What every template has in common
  • Welcome
  • Browsing
  • Abandoned checkout
  • Orders
  • Shipping
  • Loyalty
  • Win-back
  • Billing
  • Use a template
  • Choose the source
  • Sources that import their events every so often
  • Values the template asks for
  • Before you can publish
  • What to check before publishing
  • RCS send mode
  • Sample image on the first card
  • Message language
  • Billing
  • Related

© 2026 Instasent

Privacy PolicyTerms & ConditionsCookie PolicyLegal Notice
All systems operational