|
| 1 | +================= |
| 2 | +Information panel |
| 3 | +================= |
| 4 | + |
| 5 | +The **Live Chat** information panel provides agents with the context they need to handle live chat |
| 6 | +conversations efficiently. It gathers key information about the visitor and the conversation |
| 7 | +history, allowing agents to respond faster and avoid repetitive messaging. |
| 8 | + |
| 9 | +Accessing the info panel |
| 10 | +======================== |
| 11 | + |
| 12 | +To view the info panel, open a live chat conversation either in the **Discuss** app or the **Live |
| 13 | +Chat** app. Live chat discussions in the **Discuss** app are listed on the left side panel, under |
| 14 | +the title of the live chat channel where the conversation began. In the **Live Chat** app, |
| 15 | +conversations can be accessed by navigating to :menuselection:`Live Chat --> Sessions --> All |
| 16 | +Conversations`. |
| 17 | + |
| 18 | +On the right side of the conversation, click the :icon:`fa-info` :guilabel:`(information)` icon to |
| 19 | +open the info panel. |
| 20 | + |
| 21 | +.. image:: information/info-panel.png |
| 22 | + :alt: The information panel for a known contact. |
| 23 | + |
| 24 | +Contact information |
| 25 | +=================== |
| 26 | + |
| 27 | +If the live chat conversation involves a known contact, a :guilabel:`View Contact` button appears at |
| 28 | +the top of the panel. Clicking this button opens the :doc:`contact record |
| 29 | +<../../essentials/contacts>` for the customer, without closing the conversation. The contact record |
| 30 | +links to the customers' sales, invoices, meetings, and previous live chat sessions. |
| 31 | + |
| 32 | +Status |
| 33 | +====== |
| 34 | + |
| 35 | +The *Status* feature allows agents to identify conversations that require immediate action, and |
| 36 | +inform other agents which conversations require their expertise at any given time. |
| 37 | + |
| 38 | +In progress |
| 39 | +----------- |
| 40 | + |
| 41 | +The *In progress* status is the default status for a conversation. This status indicates that the |
| 42 | +customer is waiting for a response from an agent. |
| 43 | + |
| 44 | +.. tip:: |
| 45 | + If a conversation is set to *Waiting for customer*, it will revert to *In progress* as soon as |
| 46 | + the customer sends a new message. |
| 47 | + |
| 48 | +Waiting for customer |
| 49 | +-------------------- |
| 50 | + |
| 51 | +The *Waiting for customer* status indicates that an agent has sent a message to the customer and is |
| 52 | +waiting for a response. When this status is applied, the conversation is highlighted in yellow with |
| 53 | +a :icon:`fa-hourglass-start` :guilabel:`(hourglass)` icon. |
| 54 | + |
| 55 | +.. image:: information/waiting-for-customer.png |
| 56 | + :alt: A conversation with the waiting for customer status. |
| 57 | + |
| 58 | +.. important:: |
| 59 | + The *Waiting for customer* status must be manually applied. |
| 60 | + |
| 61 | +Looking for help |
| 62 | +---------------- |
| 63 | + |
| 64 | +If a conversation is marked with the status *Looking for help*, it moves from under the channel name |
| 65 | +heading to the *Looking for help* heading, and the :icon:`fa-exclamation-circle` |
| 66 | +:guilabel:`(exclamation circle)` icon is added. Any user with **Live Chat** permissions can view or |
| 67 | +join these conversations, even if they are not currently active in a live chat channel. |
| 68 | + |
| 69 | +If a conversation with the *Looking for help* status has an :ref:`expertise <information/expertise>` |
| 70 | +listed that matches the user's, the conversation is marked with a :icon:`fa-star` :guilabel:`(star)` |
| 71 | +icon. |
| 72 | + |
| 73 | +.. image:: information/relevant-to-experience.png |
| 74 | + :alt: The looking for help panel with a star marking conversations relevant to user expertise. |
| 75 | + |
| 76 | +To join a conversation in progress, click the :icon:`fa-sign-in` :guilabel:`(sign in)` icon. Doing |
| 77 | +so moves the conversation back to the channel heading and reverts the status to *In progress*. The |
| 78 | +customer is also informed that a new user has joined the chat. |
| 79 | + |
| 80 | +Notes |
| 81 | +===== |
| 82 | + |
| 83 | +The :guilabel:`Notes` field allows agents to leave comments about the conversation, recap the |
| 84 | +situation when transferring it to another agent, or to add context to the conversation that can be |
| 85 | +viewed later in reporting. |
| 86 | + |
| 87 | +Tags |
| 88 | +==== |
| 89 | + |
| 90 | +Tags can be added to a conversation to assist with categorizing, tracking issues, and enhancing |
| 91 | +reporting. Click :guilabel:`Tags` :icon:`fa-plus`, then select a tag from the list, or enter a new |
| 92 | +one in the field. Multiple tags can be added to a single conversation. |
| 93 | + |
| 94 | +Chatbot answers |
| 95 | +=============== |
| 96 | + |
| 97 | +If the conversation was forwarded from a chatbot, the answers selected from the chatbot are included |
| 98 | +on the information panel under *Chatbot answers*. |
| 99 | + |
| 100 | +.. image:: information/chatbot-answers.png |
| 101 | + :alt: The chatbot answers section of the information panel. |
| 102 | + |
| 103 | +.. _information/expertise: |
| 104 | + |
| 105 | +Expertise |
| 106 | +========= |
| 107 | + |
| 108 | +The :guilabel:`Expertise` field allows agents to designate the topic of conversation to a specific |
| 109 | +expertise. This helps to categorize the conversation for assignment purposes, as well as issue |
| 110 | +tacking and enchanced reporting. Click into the field and select one or more options from the |
| 111 | +drop-down list. |
| 112 | + |
| 113 | +Recent conversations |
| 114 | +==================== |
| 115 | + |
| 116 | +Any recent live chat conversations with this customer also appear in the information panel. Click on |
| 117 | +the :icon:`fa-external-link` :guilabel:`(external link)` icon on the ticket title to open the |
| 118 | +conversation in a new tab. |
| 119 | + |
| 120 | +.. image:: information/recent-conversations.png |
| 121 | + :alt: The recent conversations field on the information panel. |
| 122 | + |
| 123 | +Open tickets |
| 124 | +============ |
| 125 | + |
| 126 | +Any open **Helpdesk** tickets created by the customer also appear in the information panel. Click on |
| 127 | +the :icon:`fa-external-link` :guilabel:`(external link)` icon on the ticket title to open the ticket |
| 128 | +record in a new tab. |
| 129 | + |
| 130 | +.. image:: information/open-tickets.png |
| 131 | + :alt: The open ticket field on the information panel. |
| 132 | + |
| 133 | +Outcome |
| 134 | +======= |
| 135 | + |
| 136 | +For closed conversations, the *Outcome* field defines how the conversation concluded: |
| 137 | + |
| 138 | +- *No Answer*: assigned when the customer does not respond to the agent. This usually occurs when |
| 139 | + the session is initiated, but the customer does not engage or send additional messages. |
| 140 | +- *No One Available*: assigned when no agents are available to respond to the customer. This occurs |
| 141 | + when the session is initiated, but no operator is online or available to be assigned to the chat. |
| 142 | +- *Success*: assigned when the live chat session is completed successfully. This outcome does |
| 143 | + **not** depend the customer providing a positive rating, it is dependent on the session being |
| 144 | + resolved without escalation or failure. |
| 145 | +- *Escalated*: assigned when the session is forwarded to another operator. This indicates the |
| 146 | + initial operator could not resolve the issue, and required assistance. |
| 147 | + |
| 148 | +Send transcript |
| 149 | +=============== |
| 150 | + |
| 151 | +When the conversation is complete, scroll to the bottom of the info panel and click the |
| 152 | +:icon:`fa-paper-plane` :guilabel:`(paper plane)` icon to send a copy of the conversation transcript. |
| 153 | +The email address in the field can be edited to send to a different address. |
| 154 | + |
| 155 | +.. image:: information/send-convo.png |
| 156 | + :alt: The send conversation button at the bottom of the info panel. |
0 commit comments