1. What an Operator does

An Operator is a cashier-level account: created by an Admin, assigned to one or more hotspots, and given exactly the screens needed to run the daily voucher business. Nothing more, nothing less.

If you work the counter at an internet café, the front desk of a hotel, or the reception of a clinic — and your job is to sell WiFi access, hand customers their cards, and help when codes don't work — this is your role.

Your scope

You see a streamlined six-item menu:

Dashboard — what's happening right now
Profiles — define the WiFi products you sell (with admin's approval)
Batches — generate and print voucher cards
Printing Templates — design how the cards look
WiFi Users — help individual customers
Sessions — see who's connected and how long

That's it. You don't see (and don't need to see):

Hotspots / Servers — your admin owns the infrastructure
Login Pages — your admin or distributor designs the captive portal
Statistics / Auth Logs — admin-level reporting
Billing / Hardware / Sub-admins / ZeroTier — you're not running the business

If a customer issue requires anything outside your six screens, escalate to your admin or distributor.

Who created your account

Your parent admin set up your login from their Admins screen. They sent you an email with a temporary password. After your first login, change your password from the Account menu (top-right corner).

2. Dashboard

Your home screen, scoped to the hotspots you're assigned to.

What you see

Active sessions right now across your hotspots
Today's revenue from voucher sales at your locations
Top batches by burn rate — which products are selling fastest today
Top users by data consumption — useful for spotting heavy users
System status — green if the controller and WiFi are healthy

The dashboard auto-refreshes every few seconds. Use the date picker (top-right) to look back over the day, week, or month — handy for explaining a slow shift to your manager.

3. Profiles

A profile is a "WiFi product" — it defines what each voucher gets: time, data, speed, concurrent device limit, and validity window.

You have full control: create, edit, and delete. But before adding new products, agree with your admin on naming and pricing — operators across the same admin share the profile catalog.

Profile fields

Name — keep it customer-friendly: "1 hour, 500 MB", "Daily unlimited", "Monthly 10 GB"
Time quota — total minutes (60 = 1 hr, 1440 = 24 hr, 0 = unlimited)
Data quota — total bytes up + down (524288000 = 500 MB, 0 = unlimited)
Speed limits — download / upload kbps (0 = no limit)
Concurrent sessions — usually 1 (one device per code) or 2-3 for family/group cards
Validity window — how long after first use the voucher remains valid (e.g. 24 hours means the customer has 24 hours to consume their quota once they first connect)
Idle timeout — auto-logout after N minutes of inactivity. Default 10
Monthly recurring — enable for prepaid users where the quota resets monthly

Tips

Use Clone to copy an existing profile when adding a similar product — saves time and keeps naming consistent
Don't delete a profile that's in active use — it can break authentication for vouchers already sold. Wait until they all expire, or just leave the profile in place

4. Batches (vouchers)

Your daily bread and butter. A batch is a group of voucher codes generated together for the same profile.

Creating a batch

Click Add batch
Pick a profile — this determines time/data/speed
Pick the hotspot(s) the codes are valid at (default: all hotspots in your scope)
Set quantity — how many codes to generate
Optionally set expiry — when unused codes auto-expire
Optionally add a batch name ("Friday rush", "Reception desk Q2") for tracking
Choose a printing template
Click Generate. Codes are created instantly. Click Print to download a print-ready PDF

Editing an existing batch

You can rename a batch and adjust its expiry / batch-name metadata after creation. You cannot delete a batch — that's reserved for the admin. If you generated a batch by mistake, ask your admin to delete it.

Selling vouchers — the workflow

Customer asks for WiFi
Quote the price (e.g. "1 hour for 10 EGP")
Take payment (cash, card, whatever your business uses)
Hand them a card from the appropriate batch
Customer scratches the silver foil, reveals the code
Customer enters it on the captive portal — and they're connected

Tracking sales

The batch list view shows: total codes, used codes, remaining codes, total revenue, and "burn rate" (codes used per day on average). When burn rate is high and remaining is low, print more.

Voiding & refunds

Open a batch → click any voucher row → Void to invalidate an unused code (e.g. customer returned a damaged card). If a customer already used the code and had a problem, Refund credits their wallet (when applicable).

Exports

Every batch has Export PDF (the printable cards) and Export CSV (raw codes + status, useful for end-of-day reconciliation with the cash register).

5. Printing Templates

Customize the look of your voucher cards.

Built-in templates

Compact — 12 cards per A4 page, minimal design (good for high-volume shifts)
Premium — 6 cards per A4 with gradient and your logo prominent (good for hotels)
Receipt-roll — single-column for thermal receipt printers (80 mm width)

Creating your own

Click Add template:

Set page size (A4, A5, receipt roll)
Set cards-per-page
Upload background image and logo
Choose font (Cairo for Arabic, Inter for English; auto-switches based on locale)
Drag-and-drop the code, expiry, and instructions text blocks
Save → preview → use in any batch

Editing existing templates

Edit any template you (or others under the same admin) created. Deletion is reserved for the admin — ask them when an old template should go.

Print quality tips

Use a 600 dpi printer for crisp codes
Buy scratch-off stickers from a stationery shop
Laminate the front for durability
For mobile sales (e.g. at a poolside table), receipt-roll templates work well with a Bluetooth thermal printer

6. WiFi Users

Anyone who has ever authenticated at a hotspot in your scope appears here, voucher or registered.

List view columns

Username — the voucher code or registered username
Profile — the WiFi product they're on
MAC address — auto-detected on first connection
Status — Active / Expired / Disabled / Wallet
Total used — bytes consumed
Last seen — last successful authentication

What you can do

View any user's full session history (the menu's Show button)
Disable a user (cannot log in until re-enabled) — useful for abuse cases
Reset accounting (clear data counter) — useful for monthly users in edge cases
Delete a specific stuck session — force-disconnect without disabling the account
Top up wallet for prepaid recurring users

Some advanced edits (changing profile, etc.) are available via the API but the operator UI may hide the Edit button. Your admin or distributor can make those edits if needed.

Filters

By status, profile, hotspot, or date range. Export to CSV when reconciling with paper receipts at end of shift.

7. Sessions

Every successful authentication produces a session record — even a 30-second connection.

Columns

Username / Hotspot / Started / Stopped / Duration / Bytes in/out
Terminate cause — why the session ended (idle-timeout, user-logout, NAS-reboot, session-timeout, admin-reset)
MAC / IP — for forensics

Real-world use cases

"I only used 1 hour but you said 3" — find by MAC, show the customer the actual session start/stop times
"My phone keeps disconnecting" — filter to that user, look for repeated idle-timeouts (often weak signal, not a code issue)
"WiFi was down at 2pm" — filter to that hotspot and time range, count sessions, see if there was a flat zero (yes → outage; no → it was just one customer's device)

Operators don't see the Auth Logs screen (failed authentication attempts). When a code truly doesn't work, escalate to your admin so they can pull the auth log to see why.

8. Tips & day-to-day playbook

Start of shift

Open the dashboard — confirm green status, glance at active sessions
Check Batches — note how many codes remain in each active batch. Print more if burn rate × remaining hours > remaining codes
Glance at the printer — paper, ink, scratch stickers all topped up

Customer asks for WiFi (the 30-second flow)

"How long do you need?" → match to a profile
Quote the price
Take payment
Hand them a card
Smile

Customer says "my code doesn't work"

Spell-check the code — most issues are typos. "0" vs "O", "1" vs "I", missing dash
Check the card hasn't been scratched twice (some customers scratch off the printed code too)
Check the WiFi is connected to the right SSID before they try the code
Look up the code in the batch — is it marked used? expired?
If the code is unused, the WiFi is right, and there's no spelling issue → escalate to admin (they can pull the auth log)

End of shift

Sessions screen — quick glance for anything weird (a 24-hour session that never logged out; a hotspot with zero activity for hours)
Batches screen — note remaining codes per batch for next shift's notes
Reconcile cash with sold codes (export the batch CSV if needed for the manager)

Things you should NEVER do

Don't share an admin login. Use only your operator login. If you don't have one, ask your admin to make one
Don't try to "fix" a hotspot by power-cycling routers unless your admin asks you to. The router auto-recovers from most issues
Don't delete profiles in heavy use — even if "they look messy". Coordinate with the admin
Don't promise refunds you can't deliver. Use the Refund button — and if it doesn't work, escalate

When to escalate

Situation	Escalate to
Code doesn't work and you've checked everything	Admin
WiFi down across multiple hotspots	Admin
Customer wants their money back and the Refund button doesn't apply	Admin
Need to add a new hotspot or change router config	Admin
Need a new login page design	Admin or distributor

Stuck on something not in this guide? Ask your admin first — and if you're both stuck, email [email protected].