Choose a useful recurring journey
People install an app to reorder, manage an appointment, view documents or check a service status. Promotional screens alone do not justify installation. Identify who returns, how often and what currently requires a call. Infrequent tasks may be better served by a mobile website.
Customers need a short journey and trustworthy information; staff need accurate records and exception handling. A displayed confirmation must correspond to the underlying system, not an unverified price, slot or stock value.
Accounts and customer functions
Scope may include registration, profiles, history, bookings, documents, enquiries and notifications. Retail, equipment servicing and appointments have different states. Loyalty features require defined accrual and redemption rules.
Include login, contact changes, recovery and logout. Agree multi-device and organisation-account behaviour. Another identifier or a shared device must not expose someone else’s documents and addresses.
Data exchange and communication
Identify the authoritative source and update frequency for catalogue, schedule and CRM data. Unavailable services need honest pending states. Retried requests must not create duplicate records.
Push is a reminder, not the only place to access an important status. Users declining notifications still need a working journey. Separate promotional and operational messaging; the owner approves consent and retention rules. Avoid personal information in analytics parameters.
Phone-number changes and account merging need their own rules. A matching contact field does not prove ownership of every linked order or document. Require appropriate verification and support handling. Organisation or profile switching should be explicit, without unexplained automatic history merging.
Pilot and acceptance
Build around one complete journey, such as repeat ordering. Test with intended users and staff, including cancellation and support. Agree release-account ownership and maintenance.
- The operation appears once in the core system.
- Customers see only their own records.
- Recovery and device changes follow agreed rules.
- Declining push does not hide status.
- Cancellation and support journeys are verified.
Project questions
Should the whole website become an app?
No. Focus on recurring tasks where an app adds value; information and rare actions can remain on the site.
Can the existing customer base be retained?
Where permitted access and suitable identity mapping exist. Account matching, contact verification and history require review.
Can every customer receive messages?
Capabilities depend on the platform and channel. Purpose, consent, frequency and opt-out rules are defined before launch.
Illustrative image