This app allows us to clearly identify an individual who is responsible for the customer’s survey request and proceed to respond to the request. A reminder email is sent based on the desired delivery date. In addition, the response can be divided among multiple people.<\/div><\/div>\n\n\n
<\/span>Worker (#of Swimlane: 4)<\/div>\n\n\n\n
\n- <\/i><\/span><\/span>Sales\/Support<\/strong>\n
\n- Sales and support personnel who are the point of contact with customers.<\/li>\n<\/ul>\n<\/li>\n\n\n\n
- <\/i><\/span><\/span>Administration Department<\/strong>\n
\n- The person in charge of the department that handles the request.<\/li>\n<\/ul>\n<\/li>\n\n\n\n
- <\/i><\/span><\/span>Contact Person(s)<\/strong>\n
\n- Person in charge of responding to requests.<\/li>\n<\/ul>\n<\/li>\n\n\n\n
- <\/i><\/span><\/span>Supervisor<\/strong>\n
\n- A leader among the people in charge of requests.<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n\n\n<\/div><\/div>\n\n\n
<\/span>Business Flow (Complexity of Workflow: 15)<\/div>\n\n\n\n
\n- <\/i>1<\/span><\/span><\/span>1. Receiving Requests<\/strong>\n
\n- The person in charge enters the details of the request received from the customer.<\/li>\n<\/ul>\n<\/li>\n\n\n\n
- <\/i>7<\/span><\/span><\/span>1x. Request Supplementary Information<\/strong>\n
\n- The person in charge enters additional details about the request.<\/li>\n<\/ul>\n<\/li>\n\n\n\n
- <\/i>18<\/span><\/span><\/span> 1y. Request Supplementary Information<\/strong> <\/li>\n\n\n\n
- <\/i>2<\/span><\/span><\/span>2. Designate person in charge<\/strong>\n
\n- The department manager will designate a person to respond to the request.<\/li>\n<\/ul>\n<\/li>\n\n\n\n
- <\/i>3<\/span><\/span><\/span>3. Response<\/strong>\n
\n- The person in charge enters the response results.<\/li>\n<\/ul>\n<\/li>\n\n\n\n
- <\/i>4<\/span><\/span><\/span>4. Response report summary<\/strong>\n
\n- The leader summarizes the results of the response.<\/li>\n<\/ul>\n<\/li>\n\n\n\n
- <\/i>6<\/span><\/span><\/span>5. Summary confirmation, report to customer<\/strong>\n
\n- The person in charge will check the summary of response results and report to the customer.<\/li>\n<\/ul>\n<\/li>\n\n\n\n
- <\/i>10<\/span><\/span><\/span>x1. Set Title<\/strong>\n
\n- The workflow platform sets the customer name and request date as the subject.<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n\n\n<\/div><\/div>\n\n\n
<\/span>Business App Variables (#of Data Item: 22)<\/div>\n\n\n\n
\n- <\/i><\/span> \u25bc Customer Information \u25bc<\/strong> <\/span>
17<\/code> <\/li>\n\n\n\n- <\/i><\/span>Customer<\/strong>q_customer<\/span>
0<\/code>*<\/span>\n\n- Stores the name of the customer who made the request.<\/li>\n<\/ul>\n<\/li>\n\n\n\n
- <\/i><\/span>Date<\/strong>q_date<\/span>
3<\/code>*<\/span>\n\n- Stores the request date.<\/li>\n\n\n\n
- processInstanceStartDatetime<\/span><\/li>\n<\/ul>\n<\/li>\n\n\n\n
- <\/i><\/span>Customer Contact Name<\/strong>q_name<\/span>
1<\/code>*<\/span>\n\n- Stores the name of the person in charge of the customer who made the request.<\/li>\n<\/ul>\n<\/li>\n\n\n\n
- <\/i><\/span>Customer Contact Email Address<\/strong>q_email<\/span>
2<\/code>\n\n- Stores the email address of the person in charge of the customer who made the request.<\/li>\n<\/ul>\n<\/li>\n\n\n\n
- <\/i><\/span> \u25bc Request Details \u25bc<\/strong> <\/span>
18<\/code> <\/li>\n\n\n\n- <\/i><\/span>Request Summary<\/strong>q_summary<\/span>
4<\/code>*<\/span>\n\n- Contains a summary of the request.<\/li>\n<\/ul>\n<\/li>\n\n\n\n
- <\/i><\/span>Request Details<\/strong>q_detail<\/span>
5<\/code>*<\/span>\n\n- Stores the details of the request.<\/li>\n<\/ul>\n<\/li>\n\n\n\n
- <\/i><\/span>Related Files<\/strong>q_file<\/span>
6<\/code>\n\n- Files related to the request are stored.<\/li>\n<\/ul>\n<\/li>\n\n\n\n
- <\/i><\/span>Desired Response Date<\/strong>q_limit<\/span>
7<\/code>*<\/span>\n\n- Stores the desired response date for the request.<\/li>\n<\/ul>\n<\/li>\n\n\n\n
- <\/i><\/span> \u25bc Internal Information \u25bc<\/strong> <\/span>
19<\/code> <\/li>\n\n\n\n- <\/i><\/span>Receptionist<\/strong>q_receiver<\/span>
8<\/code>*<\/span>\n\n- Stores the person in charge who accepted the request. (\u201cUser\u201d within the workflow platform)<\/li>\n\n\n\n
- ${processInstance.initQuserId}<\/span><\/li>\n<\/ul>\n<\/li>\n\n\n\n
- <\/i><\/span>Supervising Department<\/strong>q_org<\/span>
9<\/code>*<\/span>\n\n- Stores the supervising department that handles the request. (\u201cOrganization\u201d within the workflow platform)<\/li>\n<\/ul>\n<\/li>\n\n\n\n
- <\/i><\/span>Staff Leader<\/strong>q_staffLeader<\/span>
10<\/code>*<\/span>\n\n- Stores the leader of the person in charge of the request. (\u201cUser\u201d within the workflow platform)<\/li>\n<\/ul>\n<\/li>\n\n\n\n
- <\/i><\/span>Staff 1<\/strong>q_staff1<\/span>
11<\/code>\n\n- Stores the first person in charge who responds to the request. (\u201cUser\u201d within the workflow platform)<\/li>\n<\/ul>\n<\/li>\n\n\n\n
- <\/i><\/span>Staff 2<\/strong>q_staff2<\/span>
12<\/code>\n\n- Stores the second person in charge who responds to the request. (\u201cUser\u201d within the workflow platform)<\/li>\n<\/ul>\n<\/li>\n\n\n\n
- <\/i><\/span>Response Details<\/strong>q_responseDetail<\/span>
23<\/code>\n\n- Stores the details of the request response results.<\/li>\n<\/ul>\n<\/li>\n\n\n\n
- <\/i><\/span>Response Summary<\/strong>q_responseSummary<\/span>
13<\/code>*<\/span>\n\n- A summary of the request response results is stored.<\/li>\n<\/ul>\n<\/li>\n\n\n\n
- <\/i><\/span>Response Date<\/strong>q_responseDate<\/span>
15<\/code>\n\n- Stores the customer response date.<\/li>\n<\/ul>\n<\/li>\n\n\n\n
- <\/i><\/span>Communication Column<\/strong>q_note<\/span>
16<\/code>\n\n- Stores internal communication results, such as confirmation details to the requester and reasons for remand.<\/li>\n<\/ul>\n<\/li>\n\n\n\n
- <\/i><\/span>2. Supplement for designation of person in charge<\/strong>