Two Nordis projects, two ways to organise follow-up. Explore the functions behind the interfaces and the decisions they make visible.
A selection of documented projects, not a list of delivered client engagements.
About the screenshots — LeadsPage (CRM) and Requests (Rivyo) components rendered in isolation; synthetic data, French interfaces, no connected service. This is not the full authenticated application: backend and production use are not established, no SMS sending or Google access was exercised.
Nordis CRM
Enquiries and follow-up, in one record.
The problem
A residential enquiry needs qualification, assignment and follow-up. The queue helps choose what to handle; the record keeps the context behind the decision.
The work in the product
A filtered queue linked to a tabbed record: summary, assignment and history. Follow-up actions require explicit confirmation.
The queue shows what is needed to decide. The record loads details when opened. This keeps every row from becoming a full case file.
Identified functions
Queue filtered by status, priority and territory.
Record: summary, assignment, commercial workflow and history.
Guarded manual follow-up and CSV export.
Qualify the enquiry
Assign the record
Find the history
Functions documented in the CRM enquiries route and its tests.
Rivyo
See where each review request stands.
The problem
After a service, a review request passes through several states. A sent message, an opened link and a published review do not mean the same thing.
The work in the product
The portal distinguishes preparation, sending, delivery and opening. It provides a filtered history and settings for delays, reminders and quiet hours.
