Store complaint handling
No edit summary |
No edit summary |
||
| Line 1: | Line 1: | ||
=== What is it? === | === What is it? === | ||
'''Handling | '''Handling Customer Complaints for a Store.''' | ||
This is a complete app, model and example data for a clothing shop helping the staff to handle customer complaints | This is a complete app, model, and example data for a clothing shop, helping the staff to handle customer complaints professionally. | ||
[[File:ComplaintTrackerStartScreen.png|none|thumb|853x853px]] | [[File:ComplaintTrackerStartScreen.png|none|thumb|853x853px]] | ||
=== How to use === | === How to use it === | ||
The MDriven database image contains, in addition to the model, the following; | The MDriven database image contains, in addition to the model, the following; | ||
* User interface messages for all states | * User interface messages for all states | ||
| Line 11: | Line 11: | ||
** john@acme.inc (store employee) | ** john@acme.inc (store employee) | ||
** admin@acme.inc (system manager) | ** admin@acme.inc (system manager) | ||
** The password | ** The password is "password" for both users | ||
* 200 fake complaints in various states of handling | * 200 fake complaints in various states of handling | ||
* MDrivenServer | * MDrivenServer log-on | ||
** User: "a" | ** User: "a" | ||
** Password: "password" | ** Password: "password" | ||
You can download the complete database copy here: [[File:StoreComplaintHandling.zip]] | |||
=== Key | === Key Features (to users) === | ||
* Complaint tracking | * Complaint tracking | ||
* Tracking | * Tracking what information has reached the customer | ||
* Internal notes | * Internal notes | ||
* Customer chat using QR-code for easy customer access | * Customer chat using QR-code for easy customer access | ||
* Tracking | * Tracking the following use cases | ||
** The complaint process current state | ** The complaint process' current state | ||
** Decision process | ** Decision process: | ||
*** Store decision | *** Store decision | ||
*** Supplier decision | *** Supplier decision | ||
*** Manager decision | *** Manager decision | ||
** Where the broken product | ** Where the broken product is (complaint product) | ||
** | ** A replacement product (from the supplier) | ||
** Exchange product (from supplier or store) | ** Exchange product (from supplier or store) | ||
** Reimbursement | ** Reimbursement for the customer | ||
** Reimbursement to the store | ** Reimbursement from the supplier to the store | ||
** Credit tracking | ** Credit tracking | ||
* Staff to do list | * Staff to-do list | ||
* User editable messages | * User editable messages | ||
* Automatic event tracking | * Automatic event tracking | ||
| Line 43: | Line 43: | ||
** Logo | ** Logo | ||
=== Key | === Key Features (For Developers) === | ||
* Very complex setup of state machines | * Very complex setup of state machines | ||
* Summary views | * Summary views | ||
| Line 54: | Line 54: | ||
* Binding information to state machines (messages in this example) | * Binding information to state machines (messages in this example) | ||
* Serverside assignment of numbering | * Serverside assignment of numbering | ||
* QR-code setup for linking to | * QR-code setup for linking to applications | ||
* Printing setup of viewmodel | * Printing setup of viewmodel | ||
* AngularJS dynamic styling | * AngularJS dynamic styling | ||
=== Content | === Content Examples === | ||
[[File:StoreComplaintHandling, main classes.png|657x657px|Main classes|none|thumb]][[File:StoreComplaintHandling, state machines.png|519x519px|State machines|none|thumb]] | [[File:StoreComplaintHandling, main classes.png|657x657px|Main classes|none|thumb]][[File:StoreComplaintHandling, state machines.png|519x519px|State machines|none|thumb]] | ||
[[File:StoreComplaintHandling, Complaint view.png|none|thumb|677x677px|Complaint view]] | [[File:StoreComplaintHandling, Complaint view.png|none|thumb|677x677px|Complaint view]] | ||
Revision as of 07:12, 16 January 2023
What is it?
Handling Customer Complaints for a Store.
This is a complete app, model, and example data for a clothing shop, helping the staff to handle customer complaints professionally.
How to use it
The MDriven database image contains, in addition to the model, the following;
- User interface messages for all states
- Two users
- john@acme.inc (store employee)
- admin@acme.inc (system manager)
- The password is "password" for both users
- 200 fake complaints in various states of handling
- MDrivenServer log-on
- User: "a"
- Password: "password"
You can download the complete database copy here: File:StoreComplaintHandling.zip
Key Features (to users)
- Complaint tracking
- Tracking what information has reached the customer
- Internal notes
- Customer chat using QR-code for easy customer access
- Tracking the following use cases
- The complaint process' current state
- Decision process:
- Store decision
- Supplier decision
- Manager decision
- Where the broken product is (complaint product)
- A replacement product (from the supplier)
- Exchange product (from supplier or store)
- Reimbursement for the customer
- Reimbursement from the supplier to the store
- Credit tracking
- Staff to-do list
- User editable messages
- Automatic event tracking
- Multiple stores
- Address information
- Logo
Key Features (For Developers)
- Very complex setup of state machines
- Summary views
- Login handling
- User management views
- User rights setup
- Derived attributes and associations to ease user interface creation
- Uploading and showing images
- Automatic logging on state changes
- Binding information to state machines (messages in this example)
- Serverside assignment of numbering
- QR-code setup for linking to applications
- Printing setup of viewmodel
- AngularJS dynamic styling
Content Examples
This page was edited more than 9 months ago on 03/26/2024. What links here