Documentation:Store complaint handling

What is it?

Handling Customer Complaints for a Store

This is the complete app, model, and example data for a clothing shop, helping 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 (For 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

Main classes

State machines

Complaint view

Mobile chat view