Enhancement Ideas

We need the submitted data with emails provided in the Sign Up section to be connected with Zoho and the below mentioned email addresses: 1.Hello@hoory.com 2.yeva@ucraft.com 3.lilithjalalyan@ucraft.com

We need the submitted data with emails provided in the pre-chat form to be connected with Zoho and the below mentioned email addresses: 1.Hello@hoory.com 2.yeva@ucraft.com 3.lilithjalalyan@ucraft.com

As an admin user having WhatsAPP or/and Messenger channels I need to get email/system notifications to Refresh temporary Access Token on my Developer Facebook Account every 23 hrs. Please, check how we can get a Long-Lived User Access Token here : https://developers.facebook.com/docs/facebook-login/guides/access-tokens/get-long-lived/ . If you need a long-lived User access token you can generate one from a short-lived User access token. A long-lived token generally lasts about 60 days. You will need the following: A valid User Access Token Your App ID Your App Secret Query the GET oauth/access_token endpoint.

When a user's email address is longer than usual, the user interface (UI) is not displaying as expected.

1: Let's say we have 3 agents and they are called "X", "Y" and "Z" . The "X" and "Y" agents have 2 chats each (Chat limit is 2 for each of them). We have 7 chats in Queue. The "Z" operator is offline and when he becomes online he doesn't get any chat from the Queue. When The "X" operator resolves one of his chats he gets a chat from the Queue and the "Z" agent gets only one chat from the Queue (Not 2 as you told us during the meeting). The "Z" Agent gets a chat form the Queue each time "X" or "Y" agents resolve their chats. 2: When the "Z" agent gets a chat as described above there is a system message like this in the chat <<Assigned to Vahram by Zhora>>, but the chat wasn't assigned from Zhora to Vahram. This is confusing for agents and they don't know if the chat is from the queue or transferred from another agent. This May lead to a problem when we are not able to keep transferred chats on the control 3: When a chat goes to "X" or "Y" agent from the Queue there is a system message like this in the chat <<Vahram self-assigned this conversation>>

If the admin user visits the billing page s/he should see the following data: Billing date: [27]th of every month Billed to Visa ending in xxxx4545 Expires [Jun 2027] Your free trial ends [Jan 27, 2023]. After that your subscription will renew [monthly] Subscription Plan Price/ [mo/yearly] Start up $16 {view upgrade options} Seats included 1 {Update Qty}. 1 Total _______________________________________________________________________________ $16

The pixel base code tracks activity on our website, providing a baseline for measuring specific events. Please, copy the base code below and paste it between the header tags on every page of the website . <!-- Meta Pixel Code --> <script> !function(f,b,e,v,n,t,s) {if(f.fbq)return;n=f.fbq=function(){n.callMethod? n.callMethod.apply(n,arguments):n.queue.push(arguments)}; if(!f._fbq)f._fbq=n;n.push=n;n.loaded=!0;n.version='2.0'; n.queue=[];t=b.createElement(e);t.async=!0; t.src=v;s=b.getElementsByTagName(e)[0]; s.parentNode.insertBefore(t,s)}(window, document,'script', ' https://connect.facebook.net/en_US/fbevents.js '); fbq('init', '1027379308624103'); fbq('track', 'PageView'); </script> <noscript><img height="1" width="1" style="display:none" src=" https://www.facebook.com/tr?id=1027379308624103&ev=PageView&noscript=1 " /></noscript> <!-- End Meta Pixel Code -->

Description: We have encountered an issue while setting up an inbox, where the script presented at the final stage differs from the one available in the channel settings configurations. Additionally, the script from the final stage is not functioning as expected.

As an agent, who went from online status to offline and than came back to online again I want to immediately fall into queue logic and get conversations to resolve. As an agent, who logged out and logged in again, I want to immediately fall into queue logic and get conversations to resolve.

Please gather all data that we are getting in the report section.