Configure Steps to Migrate DialogFlow ES

Available Languages

Download Options

  • PDF     (773.8 KB)
    View with Adobe Reader on a variety of devices
  • ePub     (930.7 KB)
    View in various apps on iPhone, iPad, Android, Sony Reader, or Windows Phone
  • Mobi (Kindle)     (358.6 KB)
    View on Kindle device or Kindle app on multiple devices
Updated:April 11, 2024
Document ID:221861

Bias-Free Language

The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.



    Introduction

    This document describes steps to migrate Dialogflow ES migration required with the ongoing transition of all customers to use the Next generation media platform (RTMS). Our contact centre platform is undergoing some improvements with a focus on two key areas. Firstly, we are introducing enhanced security measures, particularly around virtual agent features, and secondly, we are working towards a seamless integration of security and user experience. Our top priority is to ensure the safety of user data, especially credentials and token information. Therefore, we are introducing additional security layers for our existing customers. This will involve migrating to our cloud-based AI connectors, which are powered by secure vaults to store and process sensitive data. As part of the migration process, we will move from the Dialogflow ES virtual Agent template to the Google CCAI connector, which will consolidate the onboarding process for all voice-related virtual agents.

    Call to Action 

    To incorporate the new security enhancements into your tenant, customers/partners must place a zero-dollar SKU order to gain formal entitlement on their tenant.

    IMPORTANT


    Cisco is currently transitioning all customers to use the Next generation media platform (RTMS). If the partner does not add a zero-dollar SKU then after migrating to RTMS, the Customer will be unable to add new CCAI connectors in the Control Hub. It is important that you review your customers CCAI services license.

    Note: A separate maintenance window notification will be sent when your RTMS migration has been scheduled, please look out for this.

    Licence Type

    This document contains instructions for both FLEX2 and FLEX3 licenses.

    Before proceeding, please check if your customer is using a FLEX2 or FLEX3 license and follow the instructions for updating that kind of license.

    Procedure to update A-FLEX-3-CC (FLEX 3.0) Order

    note-icon

    Note: The following procedure applies to all customers who have purchased CCAI services from Cisco or directly from Google.


    The process below explains how to modify existing subscription only. All production Webex CC tenants must have active subscription. Please contact your Sales representative or Account Manager in case you don’t have active Webex CC subscription.>

    Adding Google CCAI to FLEX 3.0 order

    1) Access https://ccrc.cisco.com/subscriptions/landing/ and open subscription which contains A-FLEX-3-CC product family.



    2) Click Modify/Renew Subscription.

    note-icon

    Note: You need to have respective permissions to modify production subscriptions. Contact your Account Manager for assistance if needed.

    anubhati_0-1712324342286





     3) Click on Edit Options



    anubhati_0-1712324449487


    4) Expand Additional Options section. For Google CCAI select the below options (select “usage based” only)



    anubhati_1-1712324493763



    5) Save and Submit

    note-icon

    Note: You can now see in the Summary the additional SKUs added. These are all usage- based SKUs, so you pay only if you start using it.




    6) Submit the order.



    7) Contact A2Q team with a request to release Compliance Hold of the new Web Order by writing email to cjp-qualification@cisco.com with a request to release the hold.


    8). The new provisioning email will be generated by new web order. You need to go through the wizard to apply changes to your Webex CC tenant.



    Procedure to update A-FLEX-CC (FLEX 2.0)

    To add CCAI features to Webex Contact Center the owners of A-FLEX-CC orders (FLEX 2.0) should NOT create a FLEX 3.0 but modify existing subscription.

    note-icon

    Note: The following procedure applies to all customers who have purchased CCAI services from Cisco or directly from Google

    The process below explains how to modify existing subscription only. All production Webex CC tenants must have active subscription. Please contact your Sales representative or Account Manager in case you don’t have active Webex CC subscription.

    Adding Google CCAI to FLEX 2.0 order

    1) Access https://ccrc.cisco.com/subscriptions/landing/ and open subscription which contains A-FLEX-CC product family.



    2) Click Modify/Renew Subscription.

    note-icon

    Note: You need to have respective permissions to modify production subscriptions. Contact your Account Manager for assistance if needed.

    anubhati_0-1712324602958


    3) Click on Edit Options

    anubhati_1-1712324651404


    4) Expand Additional Options section. For Google CCAI select the below options (select “usage based” only)



    anubhati_2-1712324715260

    5) Save and Submit

    note-icon

    Note: You can now see in the Summary the additional SKUs added. These are all usage- based SKUs, so you pay only if you start using it.


    6) Submit the order.

    7) Contact A2Q team with a request to release Compliance Hold of the new Web Order by writing email to cjp-qualification@cisco.com with a request to release the hold. The new provisioning email will be generated by new web order. You need to go through the wizard to apply changes to your Webex CC tenant.

    Revision History

    Revision Publish Date Comments
    4.0
    11-Apr-2024
    Version 5.0
    3.0
    11-Apr-2024
    Version 4.0
    2.0
    05-Apr-2024
    Version 3.0
    1.0
    05-Apr-2024
    Initial Release
    TAC Authored

    Contributed by Cisco Engineers

    Was this Document Helpful?

    FeedbackFeedback

    Contact Cisco

    This Document Applies to These Products