Veribl logo

Flows

Updated

Flows are automated journeys that run on their own once a customer does something. A flow starts with a trigger, then runs steps such as emails, tags, alerts and waits. They are for brand teams who want to follow up with product owners, or automate how warranty claims are handled, without doing it by hand.

Open Flows in the sidebar. The list shows every flow with its Type (Customers or Claims), Status (Live or Draft), Last updated, In flow now, Entered, Emails sent, Open rate and Click rate. Search and filter by status or type.

Create a flow

  1. Click Create flow.
  2. Pick a ready-made flow, or Build your own (an empty customer journey or an empty claim flow).
  3. The flow opens in the editor as a Draft.

Below the list, Recommended flows shows ready-made customer journeys you have not added yet. Click the cross to hide one.

Customer journeys

Customer journeys are for people who own your products. The trigger is one of:

  • A product is registered: right after a customer registers.
  • A warranty is about to end: a set number of days before the warranty end date (you choose the days, 1 to 365).
  • A warranty claim is resolved: when your team resolves the customer's claim.
  • Every few months of ownership: owners enter again every set number of months after they registered (1 to 60), for as long as they own the product. A new round starts each period. Good for maintenance and service schedules.
  • On a date every year: every owner enters on the month and day you choose. The date is in UTC. Only people who registered before that date this year enter. A flow you set live more than 3 days after this year's date first sends next year. Seasons differ by hemisphere, so add a Country filter to send to one hemisphere at a time.
  • A notice to owners: everyone who matches the flow filters enters once, including people who register later while the flow is live. It is meant for safety notices, recalls and firmware updates. Send the email as a service email (turn Marketing email off) so it reaches owners who have not given marketing consent. Big notices go out gradually, about 200 people every 15 minutes.

For a notice, set filters such as Product and Serial number so only the owners it concerns get it.

Ready-made journeys

  • Thanks for registering: confirms the warranty and sends a thank-you code.
  • Welcome series: tips after 3 days, a review request after about 2 weeks, accessories for owners who opened an email.
  • Refill reminder: remind owners to restock consumables.
  • Warranty ending soon: a heads-up 30 days before, with a reminder a week before.
  • Extend your warranty: offers your extended warranty plan 45 days before the warranty ends, with a reminder if they do not click.
  • Follow up after a claim: a week after resolution, check in and ask for a review.
  • Accessory suggestions: three weeks after registering.
  • Maintenance schedule: every 6 months of ownership, reminds owners to service their product. Owners with marketing consent also see the part that fits. Everyone else still gets the care reminder as a service email.
  • Season check: every year on April 1, helps owners get their product ready for the season, with a reminder a week later.
  • Notice to owners: a safety notice, recall or firmware update. The Product filter starts empty, so nobody gets it until you choose which products it concerns. Write your message in the email, then set it live.
  • Learn your product: six short lessons over three weeks, sent on days 1, 3, 6, 10, 15 and 21 after registering. Each lesson features one article from the product's Articles & Manuals. A lesson with no matching article is skipped and the next one still goes out.
  • Tag loyal owners: tags customers with three or more products and alerts a teammate.

Steps

Click the plus on the canvas, or use the Actions panel, to add a step:

StepWhat it does
EmailSends an email (see below)
Add tagAdds a tag to the customer, visible in Customers
Internal alertNotifies a team member you choose
WebhookSends the customer, product and flow as JSON to an HTTPS URL, for example to your CRM
Time delayWaits a number of hours or days (checked every 15 minutes)
Conditional splitSends customers down Yes or No branches that join up again afterwards

Click any step to edit it, then Save. Steps can be cloned, deleted or linked to with Copy link.

Write an email step

Each email has a Subject, Preview text, Heading and Message. You can use {{first_name}}, {{product}}, {{brand}}, {{warranty_expiry}}, {{discount_code}} and {{guide_title}} (the title of the product article). Choose a Button that opens their product page, your Help Center, the featured item or a link you enter. Use Preview to see it for a sample customer.

  • Featured item — the refill or accessory that fits their product, the extended warranty for their product, or a specific item from Commerce › Catalog. If nothing matches, the card is left out. See Commerce.
  • Product article: features one of the product's articles as a card with its title, the first lines and a Read the guide button. You pick the Nth article, in the order of the product's Articles & Manuals. If the product has fewer articles, the email is skipped and the flow carries on.
  • Discount code — a code from Commerce › Discounts.
  • Marketing email — on, the email is sent only with consent and carries an unsubscribe link. Off, it is a service message sent to everyone in the flow.

Conditions

Splits and flow filters can check Marketing consent, Product, Product family, Country, Products registered, Months since registering, Serial number, Warranty claims, Has an open claim, Owner health, Customer tag, and whether they Opened or Clicked an email in this flow.

Months since registering is at least or at most a number of months. Serial number is between two serials (a range, for example a batch), any of a list, or none of a list. Owners with no serial number never match.

Flow filters (in the trigger panel) are checked when a customer enters and again before every step. Anyone who stops matching leaves the flow.

Claim flows

Claim flows automate warranty claim handling. The trigger is A claim is submitted, The customer replies, A claim is approved, A claim is denied or A claim is resolved. Steps include Reply, Ask for info, Approve, Resolve, Set priority, Add tag, Assign, Internal alert, Webhook, plus delays and splits. A switch, Leave when the claim closes, stops the flow when the claim is resolved, denied or canceled.

Ready-made claim flows: Chase missing photos, Safety alert, Check in after a fix and Repeat claimants. See Warranty claims.

Go live

Use Update status at the top of the editor. A flow needs at least one step, and every step must be fully set up, before it can go live. Draft pauses the flow: nobody new enters and nothing is sent. Setting the Welcome series live turns off the old post-registration emails.

Marketing emails are skipped for customers who have not subscribed to your brand, and the flow continues. See Consent and privacy.

Tip: Start from a ready-made flow and change the copy. The template cards on the Recommended flows list show the whole journey at a glance.

Was this article helpful?

More ways to get help

  • Support

    Can't find the answer? Send us your question and the product or page it's about.

    Contact support
  • Specialists

    Get hands-on help with setup, migrating manuals, or designing your product pages.

    Book a call
  • Enterprise

    Dedicated onboarding, custom integrations, and regulatory guidance for large teams.

    Contact enterprise