Discover the business
On installation, Emma maps the Clover records and history available under the permissions granted. The first screen is an operating brief—not an empty prompt.
How Emma works
No perfect prompt.
Emma opens with
the business.
Connect Clover and Emma begins with what is actually there: sales, orders, stock, products, customers and operating history. The conversation starts after she has something useful to say.
5Focused operating spaces
6Stages from signal to result
5Levels of earned autonomy
1Traceable context per merchant
The complete operating loop
From Clover signal to verified result.
Every Emma workflow follows the same legible sequence. The merchant always knows what was found, what is being prepared and what needs a decision.
Prioritise useful work
Emma groups issues by impact, urgency, risk, confidence and dependency: a likely stockout outranks routine catalogue cleanup, while missing evidence stays visible.
Prepare the complete response
Instead of completing one isolated command, Emma connects the relevant sales, stock, customer and catalogue facts and orders the work that should happen next.
Request the right approval
Merchants see the reason, scope, risk, dependencies and before-and-after view. Approval can happen item by item or as a safe batch—never as a vague “trust me” step.
Execute inside Clover
Authorised supported actions run through tightly scoped tools with permission checks, rate-limit handling, retries and safeguards against duplicate work.
Verify and record
Emma reads the Clover value again, isolates failures, reports exactly what changed and keeps the decision and outcome in the activity history.
One connected Clover app
Five spaces. No operational fog.
The interface mirrors Emma’s state: what she detected, what she is preparing, what is waiting, what ran and what failed.
Operator
Ask naturally, open the daily brief and turn a business question into a structured response.
Analytics
Inspect sales, stock, customers, products, coverage, movements and data confidence.
Execution
Preview, approve, reject, retry and verify every supported prepared operation.
Activity
Follow reads, proposals, decisions, Clover writes, failures and verified outcomes.
Emma settings
Manage language, connection, document privacy and the approval boundary.
A business-aware command centre
Open Emma and see what needs doing.
The daily brief is where proactivity becomes concrete. It is not an endless feed of alerts; it is an ordered set of opportunities with a reason, expected effect and safe next move.
- Stockouts, sales anomalies and urgent evidence rise first
- Related fixes are combined into one reviewable batch
- Low-confidence recommendations are labelled clearly
- Dismissed work does not keep returning unchanged
Priority · Business risks3 actions
!4 high-velocity products out of stockImmediate availability and lost-sales riskReview
✓Reorder proposal readyCoverage and supplier assumptions includedReady
↗Yesterday’s sales change explainedVolume, basket and product mix separatedPrepared
Watch · Data and operations9 actions
↓5 items below Clover thresholdGrouped for review—stock changes stay protectedWatch
Aa7 catalogue records miss a SKUExact affected items ready for reviewPrepare
Quiet items are hidden until usefulView all 12
Operator
Memory
Memory
Stock policies
Margin floors
Supplier facts
Business calendar
Approval habits
Decision history
Compounding context
A good operator remembers the corrections.
If you repeatedly separate high-value stock changes, use a particular lead time or reject recommendations without enough evidence, Emma should stop making the same mistake. Operator Memory converts daily feedback into durable operating context.
Explicit rulesPolicies you set and can edit
Observed preferencesPatterns inferred from decisions
Operating historyWhat changed, failed and worked
Permission memoryWhat Emma may prepare, by workflow
A deliberately clear boundary
Automate the useful work. Protect the sensitive edge.
Emma reads broadly where authorised, but writes narrowly. Sensitive customer, employee and financial workflows remain protected.
Emma operates
- Daily business brief and natural-language analysis
- Sales, customer and product performance
- Catalogue quality and inventory control
- Stock movement, coverage and reorder preparation
- PDF analysis and action extraction
- Approved supported changes applied in Clover
Always protected
- Refunds, voids and financial transactions
- Employee accusations or surveillance
- Unapproved inventory or price changes
- Customer communication without a dedicated consent-aware workflow
- Unsupported bulk or destructive operations
- Any action beyond the merchant’s Clover permissions
See the first priorities
Start with your Clover data. Delegate when ready.
Emma’s first job is to show where attention, availability and operating quality are leaking from the business.