Technician Android App

Phone sign-in

Technicians can select Continue with phone, enter the complete international number registered on their existing ISPbills staff account, and verify the one-time SMS code. Firebase proves control of the number; ISPbills then issues the normal technician API session and applies the same status, role and permission checks as other login methods. Verification does not create a staff account.

The ISPbills Technician app is an Android field-work client. In the current server build, authentication and customer work use registered production API routes. The dashboard, jobs, inventory, barcode lookup, job map, and dispatch-location upload do not yet have registered production routes and must be treated as demo-only.

Sign in

Enter the account’s email or mobile identifier and password, then select Login. The app needs a working connection to the ISPbills server. Use Use demo account only to explore sample data.

Google and Facebook sign-in can authenticate an existing account only when the platform provider is enabled and that account can be matched. Social sign-in in the Technician client does not create a new technician account.

Signing out removes the app’s saved session token from the active session. It does not erase Android backups or files chosen elsewhere on the device.

Production-supported customer work

The registered Technician API supports these live operations:

• list customers and open one customer record;
• create a customer;
• update a customer using the current PUT operation;
• send an SMS to a customer; and
• record a customer payment or collection.

Open Customers to search and select a record. Review identity, contact, address, package, service status, and payment details before saving. Add Customer creates a live record, so provide every field required by the current app form and server validation. A customer page may open external directions when valid coordinates are stored; that uses the device’s installed maps app.

Customer photos, NID images, identity fields, messages, and collection details may contain sensitive data. Process only information the operator is authorized to collect, and verify the customer before sending SMS or recording money.

Demo-only screens

The following screens can display sample or locally held data, but their intended production endpoints are not registered in the current server:

The barcode scanner can read a code locally, but it cannot confirm a production inventory record without a registered lookup route. A locally added inventory item is temporary and can disappear after the app process restarts. The location foreground service may collect device coordinates when permission is granted, but the current server has no registered Technician location-upload route.

Device permissions

Denying a permission disables the related device feature. Turn off location access after testing, and do not infer that a visible foreground notification means coordinates reached the server.

Current limitations and troubleshooting

• There is no offline queue or conflict resolution. Retry live customer work after connectivity returns.
• If sign-in fails, verify the email/mobile identifier, password, account access, server URL, and connectivity.
• If a customer save fails, review the form’s required fields and server validation message. Customer updates must use the app version with the fixed PUT request.
• If SMS or collection recording fails, confirm the signed-in account is allowed to perform that operation and that the server integration is configured.
• Missing jobs, inventory, barcode results, job-map entries, or dispatch receipts are expected outside demo mode until their server routes are implemented and registered.