[docs] made structure for user docs combining manual and existing help
This commit is contained in:
17
docs/docs.user.support.customer_issue.md
Normal file
17
docs/docs.user.support.customer_issue.md
Normal file
@@ -0,0 +1,17 @@
|
||||
---
|
||||
{
|
||||
"_label": "Customer Issue"
|
||||
}
|
||||
---
|
||||
If you are selling **Items** under warranty or if you have sold and extended service contract Annual Maintenance Contract (AMC), your **Customer** may call you about an issue or a bread-down and give you the Serial No of this Item.
|
||||
|
||||
To record this, you can create a new **Customer Issue** and add the **Customer** and **Item** / **Serial No**. The system will then automatically fetch the Serial No’s details and indicate whether this is under warranty or AMC.
|
||||
|
||||
You must also add a description of the **Customer**’s issue and assign it to the person who needs to look into solving the issue.
|
||||
|
||||
To create a new **Customer Issue**:
|
||||
|
||||
> Support > Customer Issue > New Customer Issue
|
||||
|
||||
If a Customer visit is required to address the issue, you can create a new Maintenance Visit record from this.
|
||||
|
||||
Reference in New Issue
Block a user