Signal
Three things happen in one morning
A restock on Priya's wishlisted item, her points entering the expiry window, and a referral milestone. Three signals from three modules, one profile.
Solution · Retention automation
Retention automation that decides, not just sends.
Ayra is customer retention automation software for Shopify that works as one loop instead of a stack of triggers. Signals from Shopify and every module land on a single customer profile, rules open opportunities, and the engine picks one next best action per customer, with frequency caps, conflict resolution and a recorded reason. Doing nothing is a valid outcome.
Private beta. Free migration from the apps Ayra replaces. Pricing
Decision log
4 opportunities open Cap 1 / 7d · WhatsApp
- 09:02 VIP_RESTOCK · P1 Sent WhatsApp · +1,100 pts attached
- 09:02 POINTS_EXPIRY · P3 Merged Into the restock alert above
- 09:02 REFERRAL_PUSH · P4 Scheduled Tue next week · cap 1 / 7d
- 09:02 REVIEW_REQUEST · P3 Held Trust Recovery · ticket #812 open
Every row has a rule you can open.
01 The merchant problem
Automation stacks send more and decide less.
Most retention automation is a set of if-this-then-that triggers spread across four apps. Each one is correct on its own. Together they produce noise.
-
Triggers don't know about each other
The restock alert, the points reminder and the win-back all fire the same Tuesday, because each app only checks its own rules.
-
There is no priority
A VIP's restock and a cold lead's welcome email carry the same weight in a queue. Whatever fires first, sends first.
-
Silence is not an option
Most tools cannot decide to send nothing, so every qualifying customer gets a message, even one with an open complaint.
-
Nobody can explain a send
When a customer asks why they got three messages in a day, the answer is spread across three dashboards.
What to measure
- Actions per customer per week
- Sends, holds and skips across every module, read from the customer timeline.
- Opportunities closed by an order
- How many opened opportunities ended in an attributed order, by type.
- Held and suppressed actions
- What Journey Guard stopped and why, so you can see the noise you did not send.
No benchmarks. Ayra compares your store to itself, by cohort and segment.
02 How Ayra solves it
How Ayra automates the decision, not just the send.
- 01Explore Opportunities
Opportunities, not triggers
Rules watch the profile for patterns worth acting on and open an opportunity with a type, evidence, priority and expiry. Triggers fire. Opportunities wait to be decided.
- 02Explore Customer 360
One next best action per customer
Eligibility, scoring, priority from P0 to P4 and conflict resolution produce one action, or none. A win-back and a referral push never go out on the same day.
- 03Explore Flows
Journey Guard on every send
Frequency caps, quiet hours, channel limits and conflict rules apply to flows and to module actions alike. Every hold is logged.
- 04Explore Flows
Your flows, or Shopify Flow
A visual builder for email, SMS, WhatsApp and push, and every Ayra signal exposed as a Shopify Flow trigger if you would rather build there.
- 05Explore Analytics
A reason on every decision
The customer timeline records each action, hold and skip with the rule behind it, and revenue is attributed once.
03 The workflow
One customer, start to finish.
Priya, 4 orders · Silver. Signal to outcome, one decision, every reason recorded.
Priya
4 orders · Silver
5 stages
Customer
One profile, one frequency cap
Silver tier, 1,100 points, last message five days ago, cap of one promotional send per seven days, WhatsApp preferred.
Opportunity
Three opportunities, three priorities
VIP_RESTOCK at P1 expiring in 72 hours. POINTS_EXPIRY at P3 with 14 days. REFERRAL_PUSH at P4 with 30 days.
Action
One send, one merge, one scheduled
The next best action is the restock alert, with the expiring points attached as the incentive. The referral push is scheduled for next week. Nothing else goes out.
Outcome
An order, and a readable timeline
Priya orders and spends the points. The timeline shows the send, the merge and the hold with their rules. The referral push runs the following Tuesday.
04 Use cases
What it looks like in your store.
Collision 01
A customer qualifies for a win-back offer and a referral push the same morning.
Ayra decides
One is sent, the other is scheduled, and the timeline says why.
Quiet hours 02
A restock happens at 2 a.m. in the customer's timezone.
Ayra decides
The alert waits for the send window. When it opens, VIP and high-intent customers still go first.
Doing nothing 03
A customer with an open delivery complaint qualifies for a review request and a points reminder.
Ayra decides
Trust Recovery holds both. NO_ACTION is recorded with the ticket as the reason.
The modules behind it
All features- Explore Flows
Lifecycle Flows
Email, SMS and WhatsApp journeys that respect the customer's timeline.
- Private betaExplore Segments
Segmentation
Segments built from every signal Ayra sees, synced back to Shopify.
- Private betaExplore Analytics
Retention Analytics
Repeat rate, LTV and cohorts, with revenue attributed per module.
- Private betaExplore Loyalty
Loyalty & Rewards
Points, store credit and VIP tiers that know who the customer is.
Read next
Switching?
Dated, sourced comparisons against the apps Ayra replaces. Migration is free during private beta.
05 FAQ
Questions merchants ask first.
Is Ayra an AI retention tool?
Not at launch. The engine is rule-based with explicit, inspectable logic. Prediction for churn, lifetime value and send time is added on top of the same infrastructure later.
What makes this different from a flow builder?
A flow builder runs journeys. Ayra also decides between journeys and module actions per customer, with one priority list, one frequency cap and conflict resolution across all of them.
Can I keep using Shopify Flow?
Yes. Ayra's signals are Shopify Flow triggers and its actions are Flow actions. Integrations that let external email tools consume Ayra signals follow after private beta.
Will it send messages I did not approve?
No. Only through flows and actions you have enabled, inside the caps you set.
How do I know what it stopped?
Every hold, merge and skip is recorded on the customer timeline with the rule that caused it.
06 Related solutions
Same engine, different outcome.
- See the workflow
Increase repeat purchases
Turn deliveries, wishlists and balances into second and tenth orders.
- See the workflow
Customer winback
Detect lapsed customers from their own rhythm and bring them back once.
- See the workflow
Reduce customer churn
Read churn as signals and answer with a save, not a discount.
Every solution runs the same loop. How it works
Private beta
See every decision the engine would make for your customers.
Private beta merchants get the loop on their own customers, with rules they can read and edit and a timeline for every action.