Store complaint handling
No edit summary |
No edit summary |
||
| Line 1: | Line 1: | ||
=== What is it? === | |||
Handling of customer complaints for a store? | Handling of customer complaints for a store? | ||
| Line 53: | Line 54: | ||
=== Content examples === | === Content examples === | ||
[[File:StoreComplaintHandling, main classes.png| | [[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:StroeComplaintHandling, mobile chat view.png|none|thumb|Mobile chat view]] | |||
Revision as of 13:35, 5 August 2017
What is it?
Handling of 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 in a professional way.
How to use
The MDriven server database to upload contains, in addition to the model, the following;
- Messages for all states
- Two users
- john@acme.inc (store employee)
- admin@acme.inc (system manager)
- The password are "password" for both users
- 200 fake complaints in various states of handling
Key features (to users)
- Complaint tracker
- Internal notes
- Customer chat using QR-code for easy customer access
- Tracking of what information has reached the customer
- Tracks these use cases
- The complaint process current state
- Decision process
- Store decision
- Supplier decision
- Manager decision
- Where the broken product are (complaint product)
- Replacement product (from supplier)
- Exchange product (from supplier or store)
- Reimbursement to the customer
- Reimbursement to the store from the supplier
- Credit tracking
- Staff to do list
- User editable messages
- Automatic event tracking
- Multiple stores
- Address information
- Logo
Key features (to developers)
- Very complex setup of state machines
- Summary views
- Login handling
- User management views
- User rights setup
- Derived to ease user interface creation
- Upload 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 application
- 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