Dashboard

Owner login

Your sign-in is secured by Firebase. Change your password below.

Business details

Shown on receipts and the customer portal.

Payment QR code

Upload your UPI QR (from GPay/PhonePe/Paytm business app or your bank). Customers on the website scan this to pay.

Company logo

Upload your logo once — it appears automatically on every invoice and on the website header.

Brands

The companies whose connections you resell. Each customer is assigned one, so you can tell at a glance which company a VC belongs to — and see revenue split by brand in Reports.

UPI payments (QR)

Your employee can show a QR locked to the exact amount, so the customer pays by GPay, PhonePe or any UPI app and cannot change the figure. No Razorpay account needed and no transaction fee.

Printing from the employee app

Your printer only accepts print jobs from a computer, not from a phone. So receipts taken on the app are sent here and printed on this computer automatically — as long as this panel is open. Leave it open during collection hours.

Receipt printer (optional)

For an Epson TM-T82X or similar with the network (LAN) option, plugged into your router. Find its address by printing a self-test: hold the FEED button while switching the printer on. Leave blank if you don't have one — receipts can still be printed from this panel.

Website address

The address customers' apps use to reach your server for payment verification. Update this if you move to your own domain.

Online payments (Razorpay)

Paste your Razorpay Key ID (starts with rzp_live_). Customers then get a "Pay now" button inside their login for UPI / card / net banking. Leave blank to use QR only. Never paste the Key Secret anywhere.

Backup your data

Download all customers, plans and settings as a file. Keep it safe — it's your only copy.

Restore data

Load a backup file. This replaces everything currently saved and syncs it to the cloud — this is also how you migrate your old browser data.

Create missing customer logins

After restoring old data, run this once — it creates Firebase logins for every customer who doesn't have one yet, using their saved mobile & password.

Renumber customer IDs (5-digit)

Converts any old SAI-#### IDs to new unique 5-digit numbers. Their invoices, payments and logins are re-linked automatically — nothing is lost. New customers already get 5-digit IDs; run this only to update older ones.

Staff / employee logins

Create logins for your staff. They get the limited Employee panel — customer search, cash collection, expiring/expired lists and enquiries — never totals, reports, settings or deletion.

NOC (transfer to another operator)

When a customer moves to a different operator they need a No Objection Certificate from you. The NOC button on any customer fills it in automatically — set your own LCO details here so they print on it.

Nearby operators

The operators you transfer customers to. Adding them here means picking from a list instead of typing the number each time — and anyone you have already issued an NOC to appears automatically.

Salary privacy

Employees could read each other's salary, because the database treated all staff as administrators. That is now fixed — each employee sees only their own. Older entries need an employee id added first, or they will disappear from that employee's own history.

App problems

If the app crashes on someone's phone it is recorded here, with the version and where it happened — so you find out without waiting for a customer to ring. Nothing personal is stored, only the fault itself.

Remove stored passwords

Customer and employee passwords were being kept in readable form so old parts of the system could use them. They are not needed any more — logins keep working exactly as now, and if someone forgets their password you set a new one from their record. Anyone who got hold of your data could read the stored ones, so it is worth clearing them.

Clear leftover logins

If you deleted customers before and their mobile numbers still can't be re-registered, their login accounts are stranded in Firebase. This removes them.

Fix revenue from imported customers

Adding a customer (by Excel import, or in older versions by registering) used to count as money collected, which inflates revenue and profit. This finds those entries and removes them. Real collections are never touched.

Fix invoices missing from the app

A customer's first invoice is created a moment before their app login exists, so it can end up unlinked and invisible in their app. This links them up. Safe to run anytime.

Clean up incomplete records

Removes stray "ghost" rows that have no valid registration (no plan, no VC, no join date) — usually left over from failed logins or an old build. Real customers are never touched. Run this if your dashboard count or "login pending" list looks wrong.

⚠ Danger zone — delete all customers

Permanently removes every customer and their data from the cloud. Their logins, invoices and records go too. This cannot be undone — download a backup first. Use only when clearing test data before going live.