Service app
Easier access to services through a mobile app
A scenario for a service whose requests, document submissions, and status follow-up depend on repeated phone calls and long forms.
This page presents a conceptual scenario, not a real customer project. It illustrates problem analysis, scope definition, and the choice of evaluation criteria. None of the improvements described are measured results from a real project.
What problems does the current situation create?
Users don't know the status of their requests and call to follow up. Support staff spend considerable time answering recurring questions, finding documents, and relaying messages between departments.
Users and stakeholders
Customers or applicants, intake operators, reviewers, process managers, and the support team.
Proposed approach
How does the solution take shape step by step?
The request journey is divided into short stages. Only the information needed at each stage is collected, documents are sent from the phone, and statuses are understandable to users. Notifications are sent only for important changes or required actions.
Real data samples, processes, and constraints must be reviewed before choosing technology. This scenario illustrates only one possible approach.
Conceptual scope
Areas explored in this scenario
This list is not a contractual scope or quotation. First-version features are defined after understanding users and dependencies.
Suggested metrics
How would we measure success in a real project?
Request completion
Measure the proportion of users who complete the journey without abandoning it.
Follow-up calls
Compare calls asking about request status.
Handling time
Review time spent waiting at each stage.
Missing documents
Record returned requests and their reasons.
These metrics are not achieved results. In a real project, they must be defined before implementation and then measured.
Assumptions and risks
What needs investigation before implementation?
- Complex forms
- Intrusive notifications
- Sensitive data and documents
- Inexperienced users
- Offline requirements
- App store or SMS dependencies
Mobile app design and development
App and infrastructure design based on user behavior and the actual service journey.
