Frequently Asked Questions

Bold360 21.10 release notes

Bold360 version 21.10 contains the following new enhancements:

Enforcing HTTPS and removing HTTP across widget scripts

Going forward, there will no longer be an option to choose (non-secure) HTTP-only connections when generating widget touchpoint scripts. HTTPS will be enforced across all touchpoints going forward and HTTP-only widget configurations will no longer be supported as of December 31, 2021. Any widget script using HTTP only will need to be changed by this date in order to continue uninterrupted

Access to the Genesys DX AI management (*.nanorep.co) will only be accessible through HTTPs

In-product announcements will be present to raise awareness of this change

Important: Any widget script using HTTP only will need to be changed by this date in order to continue uninterrupted.

In-Product Rebranding

As part of the transformation to Genesys DX, the product interfaces are now rebranded to reflect this change. Logos, product names, and company links are now updated to Genesys branding and is present within each of the product interfaces.

getEstimatedWaitTime API call

Using the "getEstimatedWaitTime" API call will provide the estimated wait time that the visitor would spend waiting before starting a live chat with an agent.

Details on using this API can be located in this article.

Allowlists and the Digital DX AI platform

To use Genesys DX, you may want to allowlist certain URLs so that its connected services are able to connect.

We recommend you add the following URLs to your network's allowlist:

  • *.boldchat.com, *bold360.com - Genesys' service for adding chat to websites
  • *.nanorep.co ? The site for customers who have access to the Bold360 AI platform (Service, Advise, and Acquire)
  • authentication.logmeininc.com, auth.bold360.com - LogMeIn's sign-in service
  • launch.bold360.com, myaccount.logmeininc.com, profile.logmeininc.com - LogMeIn's MyAccount page, where you can manage and access all your LogMeIn products

*** Please note that *.logmeininc.com domains and IP Addresses/ranges are only needed temporarily while the BoldChat/Bold360 platforms complete their migration to Genesys architecture.

Note: This list includes sub-domains for the listed domains, so it is advisable to use wildcard rules wherever possible when you allow or block any LogMeIn service on your network. Specifically, we recommend you to allow *bold360.com and *logmeininc.com. The services themselves communicate using port 443 (HTTPS/SSL) and port 80, so you don't need to open any additional ports within a firewall.

LogMeIn IP ranges

We recommend you add LogMeIn domains and URLs to your network's allowlist instead of allowing LogMeIn IP ranges. If that is not feasible, refer to the list of LogMeIn IP addresses.

CIDR Notation Numeric IP Range Netmask Notation
67.217.80.0/23 67.217.80.0 - 67.217.81.255 67.217.80.0 255.255.254.0
95.172.70.0/24 95.172.70.0 - 95.172.70.255 95.172.70.0 255.255.255.0
173.199.52.0/23 173.199.52.1 - 173.199.53.254 173.199.52.0 255.255.254.0

IP addresses for the sign in service

To sign in to your Bold360 work environment, you must allow LogMeIn's sign-in service. To do that by IP addresses, add the following IPs to your firewall settings:

  • 34.199.209.240
  • 35.173.84.18
  • 78.108.120.24
  • 173.199.2.47
  • 173.199.4.47

Email addresses for the sign in service

Make sure you allow the following email addresses so that identity-related and authentication emails are received:

  • noreply@logmein.com
  • support@bold360.com

Third-party IP Ranges

You must also allowlist ranges for these third-party services based upon your use of these service providers:

Email Domains

For email invitations and correspondences from us and the BoldChat/Bold360 software, we recommend allowing the following email domains through your email's spam and allowlist filters.

  • noreply@logmein.com
  • support@bold360.com

*** Please note that *.logmeininc.com domains and IP Addresses/ranges are only needed temporarily while the BoldChat/Bold360 platforms complete their migration to Genesys architecture.

 

Update as of September 14, 2021

Beginning on October 9, 2021, additional changes are taking place as part of the migration process of the DX platform from LMI to Genesys. The failover will take place in 3 stages from LMI on-premise data centers to Genesys cloud-based environment which provides robustness, flexibility and better scalability to the DX platform.

[ACTION] - If you allow list Agent (formerly known as BoldChat) by domain (preferred to DNS or IP allowlisting), you will need to allowlist the following domains in your organization's network/firewall:

  • bold360.com
  • boldchat.com

Alternatively, you can allowlist the following DNS servers:

Ireland

  • eub-app16-01.boldchat.com
  • eub-app16-02.boldchat.com
  • eub-app16-03.boldchat.com
  • eub-app16-04.boldchat.com
  • eub-app16-05.boldchat.com
  • eub-app16-06.boldchat.com
  • eub-app16-07.boldchat.com
  • eub-app16-08.boldchat.com
  • eub-app16-09.boldchat.com
  • eub-app16-10.boldchat.com
  • eub-app16-11.boldchat.com
  • eub-app16-12.boldchat.com

Frankfurt

  • eub-app17-01.boldchat.com
  • eub-app17-02.boldchat.com
  • eub-app17-03.boldchat.com
  • eub-app17-04.boldchat.com
  • eub-app17-05.boldchat.com
  • eub-app17-06.boldchat.com
  • eub-app17-07.boldchat.com
  • eub-app17-08.boldchat.com
  • eub-app17-09.boldchat.com
  • eub-app17-10.boldchat.com
  • eub-app17-11.boldchat.com
  • eub-app17-12.boldchat.com

[ACTION] - If you allow-list Agent (formerly known as BoldChat) by IP, here are the IPs you will need to allow list in your organization in order to avoid connectivity issues with the new Data Center on October 9th:

Ireland

  • 34.246.13.84
  • 54.155.23.252
  • 46.137.48.149
  • 34.254.28.102 5
  • 2.49.80.82
  • 63.33.229.51
  • 54.75.218.75
  • 54.216.206.26
  • 34.246.145.123
  • 52.212.90.186 5
  • 4.77.148.81
  • 34.251.74.92

Frankfurt

  • 3.122.210.241
  • 18.192.113.151
  • 3.68.175.68
  • 18.196.140.195
  • 3.68.178.202
  • 18.194.200.171
  • 18.198.110.95
  • 18.192.7.127
  • 3.65.55.253
  • 3.64.238.21
  • 3.64.109.185
  • 18.198.123.19

In the 21.10 release, a new API call was introduced for presenting the estimated wait time until a chat waiting in queue would be assigned to an agent and/or department.

Parameter

Type

Required

Description

DepartmentID

numeric - ID code

No

The identifier of the department.

When not set, all queue' data is returned. Estimated Wait Time is fix 0.

When null value set, department less queue (account level) data is returned.\

Request format

curl "https://api.boldchat.com/aid/$accountID/data/rest/json/v1/getEstimatedWaitTime?auth=$authHash&DepartmentID=$DepartmentID"

Return values

Parameters are provided in alphabetic order. See Sample code for probable output.

Parameter

Type

Description

EstimatedWaitTime

integer

Estimated wait time for the requested queue in milliseconds.

When null DepartmentID requested, department less queue (account level) estimated wait time returned.

Without DepartmentID parameter it will be always 0.

QueueDepth

integer

Queue size for the requested queue.

Cumulated queue size value when DepartmentID is not provided.

Status

codes - set values

"Success" when the call completes; "Error" when the call fails.

Truncated

Boolean

Whether or not the above JSON array is the complete result set, or if the server limited the returned results. For these methods, it is unlikely the limit will be hit, but if it is either filter down the results set or contact us to try to find a way to get at the data you are looking for.

Sample code

{

    "Status": "success",

    "Truncated": false,

    "Data": [

        {

            "EstimatedWaitTime": 65340,

            "QueueDepth": 3

        }

    ]

}      

 

Validating Chats, Visits and Conversions (Data Validation)

Set Digital DX to validate all chats, visits and conversions. Use this feature to ensure that incoming chats originate from the website associated with the chat button and that chat and visit parameters provided by the customer cannot be viewed or modified by any third party. When customer monitoring and/or conversion tracking is enabled, this feature also ensures that the visit/conversion data originates from the website with the monitoring/conversion HTML code.

Setup

Data validation is set for a Digital DX Website. Even if you have a single webpage only where you want to display a chat window, you must create a Digital DX website.

Fastpath: In the Web Admin Center, go to Organization > Websites > Data Validation

When enabled and required, all chat, visit, or conversion data must be validated as originating from your server before reaching an agent.

Data Validation Methods:

  • PGP: The data passed to Digital DX can be PGP encrypted using our public key and signed with your private key to completely hide the parameters passed into chat
  • HMAC-SHA512: The customer can be disallowed from tampering with the data passed to Digital DX by generating a hash of the data using a private hashing key

Both methods rely on a new parameter in the HTML: SecureParameters. This replaces custom variable parameters such as VisitRef, VisitInfo, etc. Any visit, chat or conversion related data when validation is enabled that are not passed into the SecureParameters variable will be ignored by the server. Additionally, if security fails, the chat, visit or conversion will fail as well.

For browsers with JavaScript disabled, Digital DX loads an image inside the noscript tag to register the visit/conversion. In this case, use the parameter secured to pass the secured parameters.

Note: When using a Digital DX AI-enabled chat widget, you can set the domain manually as follows:
_bcvma.push(["setDomain", "s3.amazonaws.com"]);

PGP Encryption

Passed parameters should be URL-form encoded into a single string (for example, VisitName=Robert%20Smith&VisitEmail=r.smith%40gmail.com&ChatWindowID=123456). This is what you will PGP encrypt, sign and pass as the SecureParameters variable. The final string passed in as the SecureParameters variable will look like this:

"-----BEGIN PGP MESSAGE-----\nVersion: BCPG v1.50\n\nhQEMA9/66abKVXSZAQf/UT+3OtVApwD0H+Fv2S5bXqMfkvHEQgbvXLwMiLPRy2gs\nv3L4EbMGMoIjt8Leg1D/M8bgbovYEs546LwXdAcOQt/n4c2+9WB8mph9lDW4+z9U\n5eWwwDjatrF8yKvpVM+g0+y8SEtuuBr2xrNfXBaCXRSyEN/88tl7drvIjzAg5lUV\nuPMtDvLnE9bAhu02FQx04Dc0lKGDROPlXCp/6tW6rXRmdvZfPRe4GDCzkHoZVOGR\nByNMD1swSIWC60IL5so4wWvmOqgP/fU57W2QNz7wmF9RtSG+L8zdhYX0BKdQAOVL\nKzhRtoMbBpNcT1m0prFhw40sfGDcVnPLJhD4RvLv79LBpwE2HeW3LNm6ZH45ou1A\nmIzik8ZGExDVLY4N9tax6goP1tYXTOq2Zc/XuwIQHhXMdEZaxeLppsjt1cOym/BV\n/2y8uPO8DPQa4jTXDPOsmLJpzAJMnk3EhMMaDDzOIS32i8IyY2sYPgd651ifXrO7\n38zCnPC6zMByBuwqvoT5xlELYE0KFRvm7fmYhYK2KHQrazneESRX0TnLrI3k6mSR\ndK/MSLVb5v6aNY6f/RySADE/XqhEJ8DVXRyN8Qum+vtl1PMGOothaFemT4bZbZ+8\nw7PKCZSFWqKcEZyk1eJl02V8u1VgmYkaya2vvLGFqTGxSVk6jALrPcIyCxW7z1XV\nVSwdraDtqMyJ6aAOkUEF5qidyupoajpyjxWRsaM5Al/VJOjR6u97fu9aSNtGNW73\nmmpqBh2MwbPvO5wWTadN3VLRowlkzNWIX0pdKvdA69fQ4NlGLra9bmH0ofjQuCl9\nNTRAqn5pbyb8aCyWtxMTtgxZwgNsdWMg0yYMLV+HdH3zVT6Bc+lExzOl5rxOXxbz\nQxj3Bqil615AQP2JIi4A6FQ0+Om1xNtm+t6eIFAR3GDYjaw+GgBv+r4mdXRfz/6I\nOQysntG1rMgCHjXg6B2y46PAp2tdVptJVcUhyz93m99MBT3nKtUmmb5sVHJRnmIg\nQjQv+3SKjVnMwncHveNXosBBeem2Vdrb+lVbI3eQ0XD/fEi43oQdl8hSNuqfw1jy\nDz4Gi2EaYyaDqrRMS6nEMaOujfD6zcPpbR8MSbmQTvmi5eOWPQZhopXrN2ogxtea\n5jUabllMN5PxGkXWBAhWG1hUVkYH8SMucQ==\n=/htM\n-----END PGP MESSAGE-----"
Important: When using a Digital DX AI-enabled chat window, the ChatKey is pre-populated by the system. In this case, an Unsecured=ChatKey parameter must be used.

You can provide your public signing key on the New/Edit Website window. Digital DX uses it to generate a new server key in the back-end for encrypting the data and providing you a public key for encrypting the data.

The server-side generated keys are 2048-bit, and we recommend you use the same key size for your signing key.

For your first test, you can encrypt your data and pass it into the website setup data verification area. The server will decrypt it, verify the signature, and return the plain-text data or any error messages encountered.

HMAC-SHA512 Hashing

The most secure method of validating chats is the full PGP encryption. However, for ease of implementation, we also support the HMAC-SHA512 hashing algorithm.

The parameters you want to pass should be URL-form encoded into a single string (for example, VisitName=Robert%20Smith&VisitEmail=r.smith%40gmail.com&ChatWindowID=123456&Unsecured=ChatKey). The private hashing key will be concatenated in front of this value, and then hashed using the HMAC-SHA512 algorithm. The hashed value should then be hex-encoded and appended to the front of the SecureParameters variable. The final string passed in as the SecureParameters variable will look like this:

"1939D964B68EBFA61DE8C0B45D0C3C4836169C87DAB362116474A3B67B113B65F0172D3FA3191EC3525DA3E50B11A09B00B0A2869A1585EF148420347DE17A9EVisitName=Robert%20Smith&VisitEmail=r.smith%40gmail.com&ChatWindowID=123456&Unsecured=ChatKey"
Important: When using a Digital DX AI-enabled chat window, the ChatKey is pre-populated by the system. In this case, an Unsecured=ChatKey parameter must be used.

On the New/Edit Website window, you can create and delete the private hashing keys used to validate the customer data.

For your first test, you can hash the key and data to append the data to the hash and pass it to the data verification area of the New/Edit Website window. The server will parse out and verify the hash, returning plain-text data or any error messages.

Parameters

Once validation is enabled, you can use both original parameter names ("vr", "vn", etc.) and human-readable versions:

Friendly Name Original Meaning
URL url The current page of the customer (also the chat launch url when a chat is launched)
ReferrerURL referrer The referring page of the customer
VisitName vn The name of the customer
VisitRef vr A reference value for the customer
VisitInfo vi An information value for the customer
VisitEmail ve The email address of the customer
VisitPhone vp The phone number of the customer
CustomURL curl The custom URL for the chat
VisitorIcon vicon The chat icon for the customer
OperatorIcon oicon The default chat icon for the agent
LastName ln The last name of the customer
FirstName vn The first name of the customer (synonymous with VisitName)
InitialQuestion iq The initial question for the customer in chat
ConversionRef cr The conversion reference value for the conversion (must be unique per conversion code)
ConversionInfo ci An information value for the conversion
ConversionAmount ca The amount of the conversion (should be a number simply as 1000.15 for one thousand and fifteen one hundredths)
LanguageCode lc The language code for the chat
customField_[name]   Value of the custom field with the given name

Additional fields that require validation:

Friendly Name Original Meaning
ChatButtonID cbdid The ID of the chat button used to launch the request (which will additionally set the department and chat window if not overridden with another parameter)
Important: To show the proper chat window, you must either define the ChatWindowID (or ChatButtonID) parameter as a secure parameter, or the cwdid (or cbdid) parameter as an unsecured one. Otherwise, your chat will be displayed in a default chat window. The default window does not support bot chats.
FloatingChatButtonID cbdid The ID of the floating chat button used to launch the request (synonymous with ChatButtonID)
ChatWindowID cwdid The ID of the chat window to show to the customer in chat
Important: To show the proper chat window, you must either define the ChatWindowID (or ChatButtonID) parameter as a secure parameter, or the cwdid (or cbdid) parameter as an unsecured one. Otherwise, your chat will be displayed in a default chat window. The default window does not support bot chats.
DepartmentID rdid The ID of the department to which the chat should be assigned
OperatorID roid The ID of the agent to whom the chat should be assigned
ConversionCodeID ccid The ID of the conversion code
InvitationID idid The ID of the associated Auto-Invite Ruleset

Finally, there are several validation-related fields for enhancing chat functionality once the chat is validated:

Friendly Name Original Meaning
Type type The type of the request to enforce. Chat, visit, or conversion. Recommended on all requests.
Expiration expires The time when the request should no longer be considered valid. Recommended on all requests. Counted in milliseconds from midnight 1970-01-01 UTC.
Note: The expiration should allow for a realistic duration of a session, and not too short.
ChatKey ck A unique identifier for this chat request. Repeated chat launches with this key will fail. Recommended on all chat-type requests.
Note: Assign this parameter to a session ID or similar to allow for launching more than a single validated chat during a session.
When using a
Digital DX AI-enabled chat window, the ChatKey value is pre-populated by the system. This parameter must be listed as a value in the Unsecured parameter.
VisitorKey vk A unique identifier for this customer. If an agent blocks the chat, it blocks any chat/customer with this VisitorKey from re-launching chat.
Unsecured unsecured An & separated list of parameter names. These parameters when not present in the validated data can be pulled from the query string of the request normally and/or changed/populated without server validation. For example: VisitName&InitialQuestion&VisitPhone (note the & must be URI encoded to %26 when it is part of the secure parameter string.)
Important: When using a Digital DX AI-enabled chat window, the ChatKey is pre-populated by the system. In this case, an Unsecured=ChatKey parameter must be used.

API Parameters

If you are using the chat API, the following parameters are required when the chat is created:

Friendly Name Original Meaning
APIKey APIKey The API key being used. This must match the API key passed in through the authentication header.
Data Data Pre-populated data passed into the chat. (Note: Individual fields must be listed in the 'Unsecured' parameter to not require validation.)

Error Messages

Improper setup can result in the following errors:

Chat Not Validated
You have not passed in the required validation. Either there is no validation or the Type parameter has been set incorrectly (for example, you use the type visit to launch a chat).
Error Validating Chat
You tried to validate the chat, but the hash/encryption process was unable to either decrypt or verify the information.
Validated chat launch has expired
You are passing in an Expiration timestamp that is in the past. Make sure of the following: Confirm that your server's clock is accurate; Confirm that you are passing in the time dynamically at chat launch; Confirm that you are providing a sufficient buffer so chats can't be launched after they expire.
Validated chat launch has already been used
You are passing in a ChatKey value that has already been used to launch a chat. Confirm that the chat key is unique per potential chat launch or is being dynamically generated at chat launch.

If customer monitoring or conversion tracking is not being generated correctly, use the verification area of the New/Edit Website window to verify that the data has not expired and that type is set correctly.

Bold360 AI 21.6 release notes

Bold360 AI version 21.6 contains the following new enhancements:

Bold360 Mobile SDK releases

Beta features

Important: The following features are available for Beta customers only. Contact your Success Manager to try these features.

Enhanced Smart Advisor

Important: Smart Advisor is available to agents if Bold360 Agent is integrated with Bold360 AI and it is enabled on both platforms. There are two versions of Smart Advisor available, one is available by default after the integration, the other must be enabled on account level and set up in Bold360 AI. For more information contact your Customer Success Manager.

Smart Advisor now contains the following enhancements:

  • It continuously displays suggestions based on the customer's questions.
  • Articles the agent suggests are now added to the Smart Advisor knowledge base.
  • Searches the agent completed in the Smart Advisor can now optionally be displayed in voices and Business Insights.
  • Context can now be set for the Smart Advisor touchpoint to control what articles it shows.

See the new features that the previous release introduced:

Bold360 AI 21.5 release notes

Support Center Customization

The support center is fully HTML supported and you can change the templates within its HTML code.

Tip: Check out this video to see support center configuration in action.
  1. Go to Touchpoints > Support Center and click the Page Templates tab.

    Result: The HTML Master page set-up is displayed, which you can then customize using placeholders (documented here).

  2. Use the special syntax in the tables below to insert the dynamic content (i.e article body) to your pages.
    Table 1. Entity Selector Placeholders

    Attributes

    Syntax

    Description

    Name

    Type

     

    < nR:Entity type="label" id="B025" >

    Selects the specified label by ID

    label

    Entity Selector

     

    < nR:Entity type="article" id="B025" >

    Selects the specified article by ID

    article

    Entity Selector

    Table 2. Repeater Placeholders

    Attributes

    Syntax

    Description

    Name

    Type

    labelId = -1 articles with no parent labellabelId = < %Label.ID% > current label ID, maxItems, sort(=faq), days

    < nR:Repeater type="article" sort='faq' labelId='1234' > ... < /nR:Repeater >

    Repeater's enclosed code for each article in the specified enumeration. For information on sorting articles in your Support Center, see How to change the sorting of support center articles

    article

    Repeater

    labelId, maxItems, sort(=faq), days

    < nR:Repeater type="attachment"> ... < /nR:Repeater >

    Repeater's enclosed code for each attachment for current article

    attachment

    Repeater

     

    < nR:Repeater type="phrasings"> ... < /nR:Repeater >

    Repeater's enclosed code for each phrasing for current article

    phrasing

    Repeater

    type='root'/'all'/'nestedUnder/list' maxItems='10' (OPTIONAL)

    < nR:Repeater type="label"> ... < /nR:Repeater >

    Repeats for each Label

    Label

    Repeater

      < nR:IF condition="Site.IsMultiKB" > < nR:Repeater type="language" > < a href="< %Lang.URL% >" >< %Lang.Code% >< /a > < /nR:Repeater > < /nR:IF > Repeats for each separate language KB Language KB Repeater
    Table 3. Value Placeholders

    Attributes

    Syntax

    Description

    Name

    Type

     

    < %Site.Name% >

    Configured site name

    Site.Name

    Value

     

    < %Site.Domain% >

    Configured site domain

    Site.Domain

    Value

     

    < %Site.URL% >

    Configured site URL (includes http/s)

    Site.URL

    Value

     

    < %Site.Account% >

    Configured site Account

    Site.Account

    Value

     

    < %Site.KBID% >

    Current knowledge-base ID

    Site.KBID

    Value

     

    < %Label.Name% >

    Label name

    Label.Name

    Value

     

    < %Label.ID% >

    Label ID

    Label.ID

    Value

     

    < %Label.Link% >

    Link to dedicated label page

    Label.Link

    Value

     

    < %Label.Count% >

    Amount of elements in label

    Label.Count

    Value

     

    < %Label.PositionInPath% >

    0 based index of position in current path, -1 returned if label is not in path

    Label.PositionInPath

    Value

     

    < %Article.ID% >

     

    Article.ID

    Value

     

    < %Article.Title% >

     

    Article.Title

    Value

     

    < %Article.Body% >

     

    Article.Body

    Value

     

    < %Article.Link% >

     

    Article.Link

    Value

     

    < %Article.AttachmentCount% >

     

    Article.AttachmentCount

    Value

     

    < %Article.Attachment.URL% >

     

    Article.Attachment.URL

    Value

     

    < %Article.Attachment.Name% >

     

    Article.Attachment.Name

    Value

     

    < %Article.MetaDescription% >

    Articles Meta-Description

    Article.MetaDescription

    Value

     

    < %Article.PhrasingCount% >

     

    Article.PhrasingCount

    Value

     

    < %Article.Phrasing% >

     

    Article.Phrasing

    Value

     

    < %Repeater.Ordinal% >

    The ordinal for current repeater loop

    Repeater.Ordinal

    Value

    Use in condition "Page.Type=Home" to check page type:Home/Label/Article

    < %Page.Type% >

    Determines the current page type

    Page.Type

    Value

    checks if current Label is the current page label

    < nR:IF condition= "Article.IsPageArticle" >

     

    Article.IsPageArticle

    Value (condition only)

    check if the current Article is the current page article

    < nR:IF condition= "Label.IsPageLabel" >

     

    Label.IsPageLabel

    Value (condition only)

     

    < %Site.NanorepDomain% >

    Places Bold360 AI servers domains

    Site.NanorepDomain

    Value

     

    < %Page.Error% >

    The error that is displayed

       

Featured

Bold360 21.10 Release Notes

Bold360 21.10 release notes

Bold360 version 21.10 contains the following new enhancements:

Enforcing HTTPS and removing HTTP across widget scripts

Going forward, there will no longer be an option to choose (non-secure) HTTP-only connections when generating widget touchpoint scripts. HTTPS will be enforced across all touchpoints going forward and HTTP-only widget configurations will no longer be supported as of December 31, 2021. Any widget script using HTTP only will need to be changed by this date in order to continue uninterrupted

Access to the Genesys DX AI management (*.nanorep.co) will only be accessible through HTTPs

In-product announcements will be present to raise awareness of this change

Important: Any widget script using HTTP only will need to be changed by this date in order to continue uninterrupted.

In-Product Rebranding

As part of the transformation to Genesys DX, the product interfaces are now rebranded to reflect this change. Logos, product names, and company links are now updated to Genesys branding and is present within each of the product interfaces.

getEstimatedWaitTime API call

Using the "getEstimatedWaitTime" API call will provide the estimated wait time that the visitor would spend waiting before starting a live chat with an agent.

Details on using this API can be located in this article.