Manage Customers

the working and features of manage customers page is similar for both supervisor and agent however, the group manager does not have the privileges to access the manage customers from workbech, as the group manager is not allowed to work in interaction and chat campaigns customer tab in the agent interface shows the list of customers it allows the agent to manage the customer's information and access them click "customers" icon present adjacent to the dashboard icon, to access the customer's page each customer is listed in an individual row following information of customer is available on this page customer name the first column of the customer information contains the name of the customer's name phone this column of the customer information contains the phone number of the customer here, all the phone fields such as phone1, phone2, phone3, and so on; that the administrator has created at system level is showing email id the email id column of the customer information page contains the email id of the customers timezone the timezone column shows the timezone in which the customer is present media channel id the media channel id includes the facebook, instagram, twitter, messenger, and google play id of the registered customer if the media channel id of the customer is not registered in the system, then it will show blank operations agent can perform the following two operations on the customers page customer's information click on the customer's name, a page opens up with the complete customer's information error messages if the agent does not fill a mandatory field, then an inline error message will be shown in red color just below that field as a result thereof, the agent will not be able to save the details of the customer agent can perform the following operation on the customer's information section view customer's information the first column of this page shows the customer's personal information agent can view the details or modify them if needed the agent table definition allows the administrator define the order of appearance of the customer information fields and mark the fields in which the agent can change the values or not the administrator can create multiple agent table definitions using a single data table definition for a process it means there can be multiple agent table definitions for a campaign the administrator can assign the agent to a particular agent table definition for a campaign, and that agent will view the customer information fields as per the selected agent table definition and can modify the customer information in the editable fields only important points an agent can be assigned to one agent table definition in one campaign and to another agent table definition in another campaign for example, agent1 can be assigned to "atd1" in voice1 and "atd2" in voice2 if the agent is staffed to the multiple campaigns, including an interaction campaign, then the agent table definition of the interaction campaign will be used on top of other agent table definitions if the agent is staffed to only voice campaigns, then the agent table definition of that voice campaign will be applicable in which the call has been made or received edit customer's information click "edit" button to modify the customer's information the customer's information is now editable change or add the information which you want to change click "update" button to save the changes made, else, click “cancel” button to cancel the changes click “refresh” button to refresh the customer’s information customer's information on crm click "crm" button present on the top of the customer's information bar to see the customer's information on the crm(if integrated on ameyo) the complete information of the customer is available on the crm page agent can change view or change the information according to the usage ticket dashboard in the "tickets" section, all the tickets raised by the same customer visible only it contains the same ticket dashboard but contains only the tickets of the specific customer agent can perform the same operations here like ticket dashboard agent can perform the same operations on the present tickets raised by the customer the agent is able to manage the customer information for the tickets attached with calls if there are multiple customers with the same number and customerquery node is used in the inbound nodeflow, then a modal is displayed to the agent that displays all customers with the same phone number when the agent clicks a number and click "link" button, the customer is linked, but the name of the linked customer is not displayed in "name" field of the customer information this issue has been fixed now now, when the agent links the customer in the modal displaying the multiple customers for the same phone number, then the name of the linked customer is being displayed in the "name" field of the customer information