The right ping, on the right device.
An autonomous engine still owes you the truth: 34 event types across orders, money, and system health — each one yours to route (in-app, email, mobile push, web push), threshold, or silence, per user.
- 34 event types spanning orders, returns, batches, manifests, reconciliation, VMS, billing, inventory, and system health.
- Four channels — in-app, email, mobile push, web push — chosen per event, per user, with thresholds.
- Robnu specifically alerts when something needs a human, so autonomy never means silence.
Too many alerts is the same as none.
Notification systems fail in two directions. The noisy ones fire on everything until thumbs learn to swipe-dismiss unread — and the one alert that mattered dies in the pile. The quiet ones save you from noise by hiding failures too, which with an autonomous system is the nightmare scenario: an engine silently stuck while you assume it's running.
The underlying mistake is treating notifications as one stream with one volume knob. A stuck label, a finished run, a return spike, and a connection death are different events with different urgencies for different people.
Granular events, personal routing.
You decide what's worth a buzz, what's worth an email, and what's just a log line.
Pick your events
All 34 types are individually toggleable — from run-completed and claim-won to low-stock and connection alerts.
Set thresholds
Where volume matters, thresholds keep signal high: alert on returns above a rate, stock below a level — not on every instance.
Route per channel
Urgent events to mobile push, daily summaries to email, ambient awareness in-app. Each event picks its channels.
Tune per person
Preferences are per-user: the packer's phone buzzes for run-complete; the accountant's inbox gets reconciliation digests; you get the human-needed flags.
What calibrated alerting feels like
- Buzzes regain meaning. When the phone goes off, it's real — because everything lesser was routed quieter.
- Autonomy with receipts. Run summaries and human-needed flags mean trusting the engine never requires assuming.
- The team self-serves. Each role subscribes to its own slice — no forwarding, no 'did you see the alert?'
- One-click test. Verify any channel instantly, so 'is push even working?' never haunts a critical moment.
Coverage spans the whole platform: order and batch events, manifest and sync status, returns and claims milestones, reconciliation findings, VMS uploads, inventory thresholds, billing, integration health, and system notices — 34 types in all, each opt-in/out.
Thresholds and routing. High-volume events support conditions (only above X, only below Y), and channel choice lets routine events live as in-app or email while only genuine urgencies reach push.
The human-needed category — stuck items, connection failures, approval requests. They're rare by design, and they're the contract that makes the autonomy safe.
- freeAvailable
- paidAvailable
- ajioLive
- meeshoLive
The modules around this one.
Web, Android & iOS apps
The full product on web, a native Android app with push notifications live today, and iOS in the pipeline. One account, real-time alerts everywhere.
Automations
An automation builder with run history and automated emails — set a routine once and let it run itself.
Integrations & connected accounts
Connect AJIO, Meesho, and a Gmail mailbox once. Robnu keeps every connection alive on its own — a dead session auto-recovers in seconds, with zero prompts.
You sell. Robnu runs the rest.
Live for AJIO and Meesho. Free during early access — no card, no caps. Forever free under 25 orders/day.