Three interfaces: one for field staff, one for clients, and one for our operations team.
The MVP already handles reports, notification calls and call history. This is the proposed structure for adding client accounts, staff access and reporting.
People who find and remove signs
Staff need a simple way to report work while moving around the city and check what happened to each submission.
Usually a city or municipality
Clients need to see what work we have completed for them and which businesses have been notified.
People managing No Sign operations
We need to control access, onboard clients and keep track of work across every account.
Each client has its own users, staff assignments and reports.
Each report identifies the client, staff member, business and location.
A call notifies the business. The outcome and recording stay with the report.
Staff see their work, clients see their account, and our team sees everything.
An open form could be used to submit fake reports and trigger unwanted calls. Only approved staff should be able to create reports.
Each staff member gets their own code. Our team can approve or decline access, assign them to a client, and replace or revoke their code.
We create an account and user access for each client. Its dashboard contains only that client’s work. Our admin view covers all accounts.
They sign in and enter the business and sign location.
The report is linked to the staff member and client account.
A personalized message is played. The call outcome and recording are saved.
The report and notification outcome appear in their dashboard.
Report submission, automated notification calls, call outcomes, recordings and a shared report history.
Client accounts, controlled staff access, personal report histories, client dashboards and an internal admin view with cross-client statistics.