Chat
The notion of "Chat" is used to allude to the exchange of written messages of instantaneous form. In this case, it allows the user to have the right contact with the system attendant in order to solve doubts, make requests, and others. The parameters of this application allow activating the chat, setting the default agreement for call opening, and adjusting the default group, and other actions.
Chat can be used in three ways:
- Manual: exchange of messages between several types of users (e.g.: requester and attendant) on a 4biz instance;
- Automatic: used for messaging between the user and a virtual assistant - via Chatbot, using Helper artificial intelligence;
- Both: used to enable contact between the requester and the attendant, also allowing a user to interact with a chatbot.
🖊 Note: To interact with a Chatbot, it is necessary to have purchased this service. If you have any questions, contact 4biz.
In order for chat to be available, it is necessary:
To configure the parameters of activation of the functionality.
- Access the functionality through the main menu Parametrization > Chat;
- Set the value of the parameters (attributes);
- Click on "Save";
- The list below presents the parameter of the functionality "Chat" and the purpose of each one of them.
# | Name | Possible Values | Purpose | Additional Guidance |
|---|---|---|---|---|
118 | Default Contract ID for call opening. | | Default contract ID to open calls | Not applicable |
315 | The ID of the requests created by the chat | | Source ID of requests created by chat | Not applicable |
316 | Activate Chat | Y or N | Activate Chat | Not applicable |
317 | Activity ID of requests created by chat | | Activity ID of requests created by chat | Not applicable |
388 | Default user ID (External request) | | Default user ID (External request) | Not applicable |
389 | Default group ID (External request) | | Default group ID (External request) | Not applicable |
390 | Default unit ID | | Unit ID that will be assigned to the user registered in the profile | Not applicable |
447 | Email template ID for notification of new messages in the chat | | Email template ID for notification of new messages in the chat | Not applicable |
299 | Ticket - Activate message exchange | Y or N | Activate a chat icon next to the ticket number in the attendance queue | Not applicable |
448 | Text editor used by the application | | Text editor used by the application | Not applicable |
5. The parameters 315, 316, 317, 447 and 423 must be set manually.
6. By enabling parameter 423 the chat will open integrated with the virtual assistant Helper.
Access the Main Menu > Parametrization > Chat
It will be presented the following parameters:
Parameter | Description |
|---|---|
Enable guest mode | Configure whether Smart Chat will be displayed on the login screen or not. The options will be Yes or No, default No. If the user chooses "Yes", the system will ask for the user's login. The login must follow the pattern: domain\login |
Guest mode - User ID | Required field. It is the identifier number of the user who will log in as a guest. Information contained in the UserID column of the user table |
Guest mode - Secret key | Required field. The secret key is a security word to let the user know they are talking to a guest user. |
Welcome message | Change or keep the default welcome message |
Starts opened | When enabled, it means that Smart Chat will always be in message waiting mode. The default will be No |
Initial action | When informed, action will start from the virtual assistant on the Smart Chat screen |
Save | Button to save the configurations |
After saving, the Smart Chat screen will be available on the login screen, but only for interactions with the virtual assistant. The services will follow the restrictions, group and access profile imposed on the guest user.
Below there are some examples of how to use 4biz Chat in different scenarios:
- Access the Smart Portal or Experience Center;
- Click on the "Talk" icon at the bottom of the screen to start the conversation;
- Enter in chat that you want to create a new ticket and add the required information;
- The system will return the number of the ticket created;
- The system will redirect to the talk screen;
- Enter a new message on the chat screen;
- The attendance may assume the following status: a. Awaiting Attendant (attendant may be the requester or the analyst) - signaled by an unfilled green ball b. Online - Both parties are active for conversation - signaled by a filled green ball
- Both being online, it is possible to keep the conversation;
- If one of the parties is not online and parameter 447 - is set, then the system sends a message stating it.
- Access the Smart Portal or Experience Center;
- Click on the "Talk" icon at the bottom of the screen to start the conversation;
- Enter the name of the Activity;
- The system returns options to create a new ticket or resume the attendance;
- Access the Smart Portal or Experience Center;
- Click on the "Talk" icon at the bottom of the screen to start the conversation;
- Enter the title or part of a knowledge title;
- The system will return the knowledge options found and allowed for viewing;
- Click on the knowledge title and the system will open the knowledge;
- The system will present the preview button and, when clicked, opens the knowledge portal;
- The system will present the close button and, when clicked, reduce the knowledge, returning to the original status.
- Click on the icon at the top of the screen called "Virtual Assistant" to talk to Helper;
- Type your search or subject;
- The virtual assistant can identify knowledge or activities to be opened;
- When the virtual assistant gives the fallback message, the options "Talk to Attendant" or "Resume Attendance" are immediately displayed;
- Click on the icon to start the conversation;
- The system will return the number of the ticket created;
- The attendance may assume the following status: a. Awaiting Attendant (attendant may be the requester or the analyst) - signaled by an unfilled green ball b. Online - Both parties are active for conversation - signaled by a filled green ball
- Both being online, it's possible to keep the conversation;
- If one of the parties is not online and parameter 447 - is set, then the system sends a message stating it.
- Access the Smart Portal or Experience Center;
- Click on the "Talk" icon at the bottom of the screen to start the conversation;
- Enter the name of an Activity;
- The system returns the options to create a new ticket or resume an attendance;
- Access the Smart Portal or Experience Center;
- Click on the "Talk" icon at the bottom of the screen to start the conversation;
- Enter the title or part of a knowledge title;
- The system will return the knowledge options found and allowed for viewing;
- Click on the knowledge title and the system will open the knowledge description;
- The system will present the preview button and, when clicked, opens the knowledge portal;
- The system will display the close button and, when clicked, reduce the knowledge, returning to the original status.
- Analysts must have the ticket screen open;
- Analysts must link contacts to chat through the Attendants tab;
- The analyst involved in the conversation should also link the contact to receive the conversation;
- The analyst opens the Attendants tab, selects a contact, and starts a conversation;
- If the other party has this analyst in his/her contact, then you can maintain the communication;
- If the other party does not have this analyst in his/her contacts, it is not possible to keep in touch;
- The attendance may assume the following status: a. Awaiting Attendant (attendant may be the requester or the analyst) - signaled by an unfilled green ball b. Online - Both parties are active for conversation - signaled by a filled green ball
- Both being online, it is possible to keep the conversation;
- The analyst must have the ticket screen open;
- The requester, when sending a message, the system will send to the attendant, regardless of whether the analyst has the ticket opened or not, the system displays an exclamation mark in the SmartChat icon;
- A blue ball will appear in the attendance tab informing that there are new messages in the chat;
- When the attendant opens the attendance list screen, this screen has the following fields: a. Search for the ticket number; b. Attendance in the Queue - These are attendances that did not capture the ticket; c. Attendances in Progress - These are attendances that have already been captured and are being answered.
- In order to have integration between both channels, the following parameters must be enabled: 402, 423, 441, 442, 450 3 453;
- Parameter 453 must contain the information in the menu format. Eg.: Sorry my dear, I did not understand very well what you asked for. Type menu so that I can show you the ways and help you;
- Item 1: The user will talk with Helper;
- Item 2: The virtual assistant will send several fallback messages;
- Item 3: The virtual assistant will send options to talk to the attendant or to open a new service/incident request;
- Item 4: The user selects to talk to the attendant;
- Item 5: The virtual assistant opens a new request/incident, and if there is an agent on the request side, the ticket will be created with an alert;
- Item 6: At this moment, the interaction between the user and the attendant may occur.
