Store complaint handling
No edit summary |
No edit summary |
||
Line 2: | Line 2: | ||
This is a complete app, model and example data for a clothing shop helping the staff to handle customer complaints in a professional way. | This is a complete app, model and example data for a clothing shop helping the staff to handle customer complaints in a professional way. | ||
[[File:ComplaintTrackerStartScreen.png|none|thumb|853x853px]] | |||
Key features (to users) | === Key features (to users) === | ||
* Complaint tracker | * Complaint tracker | ||
* | * Internal notes | ||
Key features (to developers) | * 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 |
Revision as of 13:17, 5 August 2017
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.
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
This page was edited more than 9 months ago on 03/26/2024. What links here