Documentation:Store complaint handling

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 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 are "password" for both users
• 200 fake complaints in various states of handling
• MDrivenServer logon
  • User: "a"
  • Password: "password"

Here you can download the complete database copy: File:StoreComplaintHandling.zip

Key features (to users)

• Complaint tracking
• Tracking of what information has reached the customer
• Internal notes
• Customer chat using QR-code for easy customer access
• Tracking of the following 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

Main classes

State machines

Complaint view

Mobile chat view