01
the advisor creates an order manually or imports it from a CSV file
Product case study
Vehicle Pickup Panel: status and scheduling in one workflow
This product for car dealerships connects a public vehicle status for the customer, preparation-team work, and advisor decisions. The customer sees the current stage and pickup time while the dealership manages the process in one panel.
Key implementation elements
public vehicle status for customers without account creation
stages for arrival, equipment fitting, washing, ready, and collected
advisor dashboard with priorities, orders, history, and pickup times
preparation-team panel with equipment-fitting and washing queues
pickup slots with confirmation, counterproposal, and cancellation states
manual order creation and CSV import through shared order logic
basic email notifications, dealership branding, and data-retention rules
Problem before implementation
Vehicle status and pickup timing move between the customer, advisor, and preparation team
Customers contact the dealership to ask whether the vehicle is ready. The advisor checks with the preparation team, while pickup proposals live in calls, messages, and notes. There is no single change history or clear next action.
customer calls asking about the current vehicle-preparation stage
manual status checks between advisors and the preparation team
pickup times scattered across messages and notes
no shared history of changes and action priorities
What we built
Three views of one process: customer, advisor, and preparation team
We built a web application with a public status link that requires no account, an advisor dashboard, and a preparation-team queue. Orders can be added manually or imported from CSV, while pickup scheduling moves through a customer proposal, advisor confirmation, or counterproposal.
Process after implementation
How the process works after implementation
From input data to a cleaner outcome. Below is a shortened view of the process after implementation.
02
the customer receives a secure link to the public status of their vehicle
03
the team marks equipment-fitting, washing, and preparation stages
04
once the vehicle is ready, the customer selects an available pickup time
05
the advisor confirms the proposal or offers another time, while the history preserves each change
Before / after
How the process changed
The table shows the main differences between manual work and the process after implementation.
| Before implementation | After implementation |
|---|---|
| the customer calls to learn the vehicle status | a public link shows the current stage and next step |
| the advisor checks progress directly with the team | advisor and team work on the same order |
| pickup times are agreed in messages and notes | proposal, confirmation, and counterproposal have explicit statuses |
| imports and manual entry create separate paths | both inputs use the same order logic |
Process outcome
customers can check the preparation stage without contacting the dealership
advisors see priorities and pickup times requiring a decision
the preparation team has a simple stage-based work queue
statuses, scheduling, and history remain attached to one order
Technologies
Next.jsReactPrismaSQLiterole-based sessionsCSV importemail notificationsdata retention and anonymization
What can be implemented in a similar way
What can be implemented in a similar way
These are examples of processes that can be organized with a similar approach: start from one concrete problem and a clear data flow.
public customer-status portals without account creation
preparation and handover of products with several operational stages
appointment scheduling with employee-side approval
operational panels connecting imports, roles, and change history
Related services
This type of implementation can be connected with MorenaTech's core areas
If a similar process still runs manually or is scattered across files, it can be connected with automation services, Google Workspace, or further process development.
Final CTA
Want to organize statuses, scheduling, and customer communication?
If the customer, operational employee, and decision-maker use different channels today, they can be connected in one clear process without building a heavy system from scratch.