Vaera Agents

Vaera Agents is your always-on AI Agents. Four specialist agents — Growth, Marketing, Customer, and Operations — watch your store continuously, do the safe work autonomously, and queue the consequential decisions for your one-click approval. The summary of what they did and what needs you arrives every morning as the Agent Briefing.

Plan and access
Vaera Agents is a Growth-plan feature and is owner-only. Team members do not see the briefing or the approval queue. Find it in the sidebar under AI Agents → Vaera Agents.

How It Works at a Glance

1

Agents wake up on the daily 6am(WAT) sweep

Every morning, all four enabled agents read your store data — orders, products, customers, content, inventory — and decide what to surface, what to act on, and what to queue for you.

2

They build today's Agent Briefing

The briefing is a single card with three sections: What we did, What needs your approval, and What to watch. It is the first thing you see on the dashboard.

3

You approve or dismiss queued items

Approve runs the action immediately through the platform's existing pipelines (email, back-in-stock notifier, draft surfaces). Dismiss puts that exact suggestion on cooldown so it does not pester you.

4

An email digest lands at your preferred hour

If you have the digest enabled, the same briefing is emailed to you between your chosen hour (default 7am WAT). You can act on items straight from the dashboard later.

The Four Agents

Each agent has a fixed domain. They do not see data outside their domain, and they cannot be reconfigured to act outside their built-in guardrails — you can only make them less active, never more autonomous.

Growth Agent

Watches revenue, order volume, AOV, top products, cancellations, and abandoned-cart rate. Daily: weekly health summary, top opportunities, prior-year seasonal heads-ups, zero-sales-14d flag. Queued: prep_seasonal, clear_slow_mover, restock_priority, reengage_abandoned_carts, investigate_cancellations.

Marketing Agent

Watches social posting cadence, blog freshness, and email-campaign performance. Daily: cadence checks, best-send-time recommendation. Queued: social_post_drafts, email_campaign_draft, blog_brief_draft — each materialises directly into the relevant existing surface on approve.

Customer Agent

Watches RFM segments, at-risk VIPs, dormant customers, support themes, and review trends. Daily: top-5 at-risk VIPs always shown, weekly support-conversation summary. Queued: send_winback (per VIP), winback_campaign, loyalty_recognition, kb_update_suggestion. Customer data never leaves your account.

Operations Agent

Watches stock levels, fulfilment rate, processing-too-long orders, and back-in-stock subscriber demand. Daily: inventory health (OOS / low-stock / value-at-risk), restock priority ranked by velocity + waiting subscribers. Queued: restock_priority_list (acknowledgement), back_in_stock_message (real send through the existing notifier).

Autonomous vs. queued vs. never
Every possible agent action is fixed at design time into one of three buckets: autonomous (informational — agent does it and reports it), queued for approval (consequential — you approve, then it executes), or never (outside the agent's authority entirely, e.g. changing billing or team permissions). This classification is not negotiable.

The Agent Briefing

The Agent Briefing is the primary surface for the agents. It appears at the top of your dashboard homepage and is the first thing you should check each morning. Vaera writes it in her own voice — calm, direct, and grounded in your actual numbers.

The Three Sections

What we did

Autonomous actions completed overnight: weekly revenue summary, inventory health report, RFM segment refresh, top-5 at-risk VIPs, stock-out flags. No action required from you — this is your morning brief.

What needs your approval

Queued items from any of the four agents, each with the signal that triggered it, the draft or recommendation in plain language, and Approve / Dismiss buttons. Clicking the item expands the full context.

What to watch

Things trending in a direction that may need attention soon — for example, fulfilment rate slipping, abandoned-cart rate creeping up, or a seasonal window approaching. No decision required today, but worth knowing.

Opening the Briefing

1

Open the dashboard

The briefing card sits at the top of the homepage. If there are pending items, the sidebar item Vaera Agents shows an unread count badge.

2

Expand the briefing

By default the card shows a headline (e.g. “3 items need your attention”) with an expand button. Click to read the full briefing.

3

Action the items

Work through the approval queue one item at a time. Once every item has been actioned, the card collapses to All clear — next briefing at 7am.

The Approval Queue

The approval queue is the safety layer between agent intelligence and anything that actually happens in your store or with your customers. Nothing consequential runs without you tapping Approve.

Approving an Item

1

Read the context

Each queued item shows: which agent raised it, the signal that triggered it (e.g. “Chisom hasn't ordered in 47 days”), and a plain-language description of exactly what will happen if you approve.

2

Review the draft or payload

For drafts (win-back messages, social posts, email campaigns, blog briefs), the full text is shown. For recommendations (restock priority, loyalty recognition list), the full list is shown.

3

Click Approve

The action runs immediately through the platform's existing pipelines — the same email queue, back-in-stock notifier, or draft surface you would use yourself. The item moves to What we did in the next briefing, and a record lands in the activity log.

Atomic and safe
Approve claims the row atomically (pending → approved) so two team-member sessions can never accidentally fire the same action twice. If the underlying executor fails for any reason, the item is returned to pending and an error is recorded so you can retry.

Dismissing an Item

1

Click Dismiss on the queued item

A normal dismiss puts that specific suggestion on cooldown using the value from your settings (default 7 days). The agent will not raise the same item against the same target (same customer, same product, same campaign window) until the cooldown expires.

2

Or dismiss permanently

If the suggestion is one you never want to see again (for example, you have decided to stop running win-backs for a particular segment), choose Dismiss permanently. The agent will not surface that exact suggestion again.

How cooldown identity works
Cooldowns match on (agent, action type, identity) — for example “Customer agent, send_winback, customer Chisom Okafor” or “Operations agent, back_in_stock_message, product Shea Butter Whip 200ml”. The agent regenerating a fresh draft for the same customer or product will not bypass an active cooldown — identity, not draft text, is what keys the suppression.

What Approve Actually Does, by Agent

Customer — send_winback

Sends the drafted win-back message to that one VIP customer through your existing email pipeline. Logged in their customer history.

Operations — back_in_stock_message

Triggers the existing back-in-stock notifier for everyone on the waitlist for that restocked product. No new transport, no new sender domain.

Marketing — social_post_drafts

Materialises the drafts into your Social content surface where you can review, schedule, or publish them. Nothing is posted directly to a social network.

Marketing — email_campaign_draft

Creates a draft campaign in your Email Marketing surface, ready for you to review and send.

Marketing — blog_brief_draft

Creates a draft blog brief (title and outline) in your Blog surface, ready for you to expand into a full post.

Growth / Operations — restock priorities, seasonal prep, clear slow movers, investigate cancellations

These are acknowledgement actions — approving them records that you have read and accepted the recommendation, and clears the item from the queue. The actual restock or pricing change is yours to action through the relevant section of the dashboard.

Agent Settings

Open settings from the Vaera Agents page. Settings are owner-only and apply to the entire account.

Enable / disable agents

Turn any individual agent on or off. A disabled agent contributes nothing to the briefing and queues nothing for approval. The other agents continue to run normally.

Cooldown days

The default cooldown applied when you dismiss a queued item. Choose 7, 14, or 30 days. This is account-wide; individual dismisses cannot override it on the fly.

Daily email digest

Toggle the briefing email on or off. When on, you receive that day's briefing in your inbox at your preferred hour.

Preferred delivery hour (WAT timezone)

Pick the hour the digest should land in your inbox (default 7am WAT). The scheduler claims the briefing atomically, so you will never receive duplicates.

Activity log

A 30-day timeline of every autonomous action, every approval, every dismissal, and every email send. Useful for audit, for catching anything unexpected, and for understanding what your agents have been up to.

What you cannot do from settings
Settings can only make agents less active. You cannot widen an agent's authority beyond its built-in autonomy boundaries, you cannot remove the approval requirement on consequential actions, and you cannot grant the briefing to non-owner team members in V1.

The Daily Email Digest

The email digest is the same content as the in-dashboard briefing, delivered to your inbox so you can act on the day even before opening the dashboard.

1

Enable the digest in settings

Toggle Daily email digest on and pick your preferred WAT-timezone hour.

2

A scheduler claims the briefing for you

Each hour, a background scheduler checks which merchants have opted in and whose preferred hour matches the current WAT hour. It claims that day's briefing atomically — even with multiple scheduler ticks, you can only ever receive one digest per day.

3

The email arrives in your inbox

Same three sections as the dashboard briefing. Clicking through takes you straight into the dashboard to approve or dismiss.

Existing email pipeline
The digest goes through the same email transport and template loader as your other Vaendora notifications. There is no extra setup — if your other Vaendora emails arrive, the digest will too.

Data and Privacy

  • Domain isolation. Each agent only reads data from its domain. The Operations Agent cannot read email-campaign data; the Marketing Agent cannot read individual customer profiles.
  • Merchant isolation. The Customer Agent reads only your customers, your orders, and your reviews. No signal from another merchant's store ever influences your briefing or queue.
  • Approval ownership. Every approve and dismiss call checks that the queue item belongs to your account before doing anything. A token from one account can never action another account's queue.
  • Audit trail. Every approve, dismiss, autonomous action, and email send is recorded in the activity log with timestamp, actor, decision, and outcome — available for 30 days from the settings page.

How It Relates to Other Vaera Surfaces

Vaera is the intelligence layer that coordinates six specialist agents across your business: Business Strategist, Visibility, Customer Support, Content, Marketing, and Operations. Each agent covers a distinct domain, and together they form a complete operating picture of your store. The in-app Vaera Agents feature (Growth, Operations, Marketing, Customer) is the always-on execution layer within that system, running in the background and surfacing only what needs your decision.

Vaera Support

The chat widget on every dashboard page. Use it when you have a question about how Vaendora works or need to open a support ticket.

AI Business Strategist

On-demand business advice grounded in your live data. Part of the broader Vaera system, it handles the deeper explanatory work when you want to interrogate a specific question rather than act on a suggestion.

Visibility Agent

Monitors your store's discoverability, surfacing search and content opportunities so your products stay findable.

Customer Support Agent

Handles routine customer enquiries and escalations, keeping response times short without extra effort from you.

Content Agent

Generates and schedules content across your channels, drawing on your brand voice and live store data.

Marketing Agent

Plans and coordinates campaigns, promotions, and outreach across your customer segments.

Operations Agent

Keeps an eye on fulfilment, stock levels, and day-to-day store health so nothing slips through the cracks.

Vaera Agents (this page)

The always-on in-app execution layer. Four agents (Growth, Operations, Marketing, Customer) run continuously in the background, monitor your store data, and surface only what needs your decision each morning in the Agent Briefing.

Tips for Getting the Most Out of Your Agents

  • Make the briefing your morning ritual. The whole design assumes you read it once a day, before anything else. Skipping it means queued items pile up and the cooldown clock starts ticking on dismisses that may not be what you actually wanted.
  • Dismiss confidently. A 7-day cooldown is a feature, not a punishment — it stops a noisy agent from re-raising the same suggestion every morning. If you do not want to action something this week, just dismiss it.
  • Use Permanent Dismiss for structural decisions. If you have decided you will never run win-backs for a segment, mark it permanent. That is the cleanest way to teach your agents your preferences.
  • Disable an agent rather than dismissing item by item. If an entire domain is not relevant to you right now (e.g. you are deliberately on a content pause), turn that agent off in settings. Re-enable it when you are ready.
  • Pair the agents with the Strategist. If the Growth Agent flags an anomaly you want to dig into, open the AI Business Strategist and ask the deeper question. The agents surface; the Strategist explains.
What is on the V2 list
WhatsApp / push delivery of the briefing, longer-term agent memory beyond the cooldown window, merchant-configurable trigger thresholds, team-member access to the briefing, and a direct hand-off from a Growth-Agent anomaly into a pre-populated Strategist conversation are all on the roadmap for V2.