Padappai public guide

Workflow ID: PUB-001
Approval: Approved baseline

Access

No account is required to browse the public provider directory, public provider details, public offers, or a public storefront. Registration, private ledgers, orders, and provider operations require the relevant account. Public pages never expose staff or company-private data.

Android app

When an Android release is published, use Android App on the padappai.com landing page to see its version, requirements, release notes, and official download choices. The page may offer a direct APK, an external app-store link, or both.

For a direct APK, Android may ask you to allow installation from the browser. Confirm that the download page is on padappai.com, install the package, and remove the browser's installation permission afterward.

Workflow

1. Open the public provider directory using route providers.index.
2. Choose a visible provider. Only approved, visible providers are listed.
3. Use contact verification when a provider requires OTP before revealing contact details.
4. Use Request service to send a verified request. A successful request creates a funnel lead only.
5. Use portal.register for a customer account or provider.register to apply as an individual provider.

Required fields depend on the action. OTP requests require a valid mobile number and captcha when enabled. Service requests require the displayed enquiry fields and a valid, unexpired OTP.

Errors and recovery

• A hidden, blocked, or unavailable provider cannot accept a request. Return to the directory and choose an available provider.
• If OTP expires, request a new OTP and use only the latest code.
• Rate-limit responses require waiting before retrying; repeatedly submitting does not bypass the limit.
• A public request must not create a work order, invoice, receipt, or stock movement. Report any such result as a critical flow defect.

Result and next step

A verified public request creates or reuses the customer identity in the selected provider workspace and creates one service funnel lead with public source metadata. The provider handles the lead later. Audit using ProviderManagementModuleTest and public-host browser UAT.