Frequently asked questions

One afternoon for a serious start: import your asset Excel, create locations, add your team, print QR labels. The in-app Getting Started guide plus a sample data kit walk you through it step by step. Most plants run their first live breakdown on day one.

No. It runs in the browser, and installs on phones like an app in two taps (Android and iPhone) — no app store, no IT involvement.

Assets, spares, services and masters import from CSV with a preview step. Historical breakdowns are usually left behind deliberately — your honest data starts the day operators start scanning.

The operator flow is: scan QR → photo → submit, in their own language. We designed it so a new joiner can report a fault in their first hour without being taught.

Yes — 25 assets, 5 users, all core modules, no card. It exists so you can prove value before paying.

Per-user pricing makes companies restrict logins, which kills adoption — and adoption is the whole point. One price per plant, add everyone.

Monthly or annual (2 months free), GST invoice provided. Enterprise plans can include an onboarding service where we import your data, print QRs and train your team on site.

7-day grace, then the account suspends. Your data is retained for 90 days and remains exportable throughout — it is never held hostage.

You do, unambiguously. Settings → Download all data exports every record as CSVs, one click, anytime.

Yes — tenant isolation is enforced at the database layer and verified by automated tests on every release.

The audit trail is immutable (entries can never be edited or deleted) and exports to CSV: who approved what, when, with remarks. PM on-time % answers the compliance question auditors ask first.

A read-only REST API for ERP/BI integration, plus an authenticated endpoint for IoT meter pushes. Nothing can be modified through the API by design.

Yes — the machine QR pages work offline; reports queue on the phone with a visible banner and submit automatically when the network returns.

English, हिन्दी, العربية (RTL), Deutsch, Français, Español, 日本語, 中文 and more — each user picks their own from the header; the company sets the default.

Connect your own gateway (Meta Cloud API, UltraMsg, AiSensy, Twilio or Interakt) in Settings. Every event can then ring bell + email + WhatsApp, with editable templates.

Yes — completion is blocked until failure mode, cause and remedy are set. That discipline is what makes the failure Pareto real.

It is a first-class flow: coverage badges at approval, send-to-vendor service calls, quote approval gates, and bill passing to the work-order cost.

You set rated output and downtime cost/hour per machine once. Every breakdown's captured duration then converts to ₹ automatically — no spreadsheet.

A reasoned recommendation per machine from its repair-cost ratio, failure acceleration, downtime losses and age — printed on its one-page History Card with the reasons listed.

Completely — they are captured as people do their jobs (report, approve, start, finish), not entered afterwards. That is why the analytics can be trusted.