Lifecycle

Writes your seven always on flows in your voice and builds them in your email or WhatsApp tool, disabled, so you enable each one with a tap.

AdviseActAutonomous $79 a month, ₹4,999

Email us to start See the workflow

Who it is for

The owner whose welcome email is still the app default and whose abandoned cart flow was never switched on.

What it reads from the brain

Before every run. Sections are addressed as layer.section.

identity.*customer.objectionscustomer.vocabularyproduct.hero_productsmodule:market

What it does, step by step

Read the brain
Opens the sections above and the inputs.
Gather evidence
Fetches your storefront and lists the flows already in your email tool. Every finding cites its source.
Decide and draft
Writes the seven flows: welcome, cart, browse, post-purchase, winback, replenishment, VIP. Drafts use your customers' vocabulary and only claims_allowed, with timing and exclusions per flow.
Advise stops here
You get the seven flows and a ranked plan for which to enable first.
Act
Creates each flow in the connected tool with status disabled, then requests one approval per flow to enable it.
Write back
Decisions appended to the brain's decisions log.

Tools it uses

storefront.fetchProducts, collections and policies the flows reference
klaviyo.flows.listWhat already exists, so nothing is duplicated or edited
klaviyo.flows.createAct: creates each flow disabled
klaviyo.flows.enableApproval gated, one tap per flow
brevo.flows.createAct: the same on Brevo
whatsapp_business.templates.listWhich WhatsApp templates are approved for the flows to use

The three modes for this agent

AdviseYour own AI, no credentials

Read tools only. You get the seven flows written with timing and exclusions, and a ranked plan.

ActConnected, every write waits for a tap

Flows created disabled in your connected tool. Each enable waits for your tap.

AutonomousHosted, scheduled, still gated

No schedule. Same gates. Planned: keeping the flows current as your products and objections change.

Guardrails and approvals

Enforced in code. Items with a filled circle wait for your tap in Telegram.

Flows created disabled.
Nothing sends until you enable it.
Suppression and exclusion rules mandatory.
Never edits a flow it did not create.
Every claim in every draft is in claims_allowed or is removed and listed as needs your confirmation.
A draft that would fit any store in your category is rejected and redrafted against your customers' vocabulary.

What it writes back to the brain

Dated and sourced. Learnings and performance sections are append only.

learnings.decisions_log (append only)

Example output

Example output: summary.md and the flow mapExample output

Example output. Structure only.

Lifecycle, your store

Ran at data level 3 (Klaviyo connected). A higher level would add nothing here.

Seven flows written in your voice. Enable order I suggest: cart, welcome, post-purchase, browse, replenishment, winback, VIP, with the one line reason for each in flows.md.

Created disabled in Klaviyo: 7 flows. Waiting for your approval to enable: cart flow first.

flow-map.json (one entry)

`` { "flow": "cart", "trigger": "checkout started, no order", "delays": ["1h", "20h", "48h"], "exits": ["order placed", "unsubscribed"], "exclusions": ["suppressed", "already in winback"], "status": "disabled" } ``

Also delivered: flows.md (all seven, copy per step, timing, exclusions).

Planned: the delays shown in this example are illustrative. Timing per flow is set per store and is not fixed in the contract yet.

Price

$79₹4,999a month, hosted. Cancel any month.

Email us to start