Skip to main content

URL Migration

  • Updated

Index:

  1. How to Migrate Bots
  2. Activation of Contract View and Important URL Changes
  3. Reactivation of Bots - Post-Cluster Migration

 

How to Migrate Bots

After creating the Contract View, it's necessary to migrate the existing bots into this new profile. Just as new bots should be created within this view.

 

To migrate the existing bots, follow the steps below:

  • 1. Access the Blip Portal, and in the contract selection located in the upper-left corner, choose the option related to the user where the bots are currently located.

In the example image below, it's named "Sustentacao" (referring to the Portal login) and will be associated with "portal.blip.ai". Usually, this option is already selected by default when accessing the Portal via the link "portal.blip.ai".

 

 

  • 2. Once you've selected the correct option, you'll have a view of all your associated bots, as seen in the image below:

 

  • 3. To move the bots into the contract, click the "Move chatbots" button. The following page will appear:

 

  • 4. In the "Move chatbots" icon, click on the "Select contract" option and choose the new contract to which you want to migrate the chatbots, as shown in the image:

 



  • 5. With the contract selected, choose the chatbots you wish to migrate on the right.

Important: Migration will only be successful if the bots are migrated along with their respective routers. Therefore, it's essential that the person responsible for migration has knowledge of bot associations and has administrator permissions in both the bots and the attached routers.

Tip! If the list of bots to be moved is extensive, send them partially to avoid errors in the process. We recommend migrating a maximum of 10 chatbots at a time and not exceeding 200 unique users at once. When attempting to migrate more than 10 bots at once, the system displays an error message, so it's crucial to respect the limit for a successful process.

 

 

There will be cases where bots with a padlock will appear in the list. If this happens, it means you're not the bot's administrator. However, to perform the migration, you need to be logged in with the administrator profile. The padlock will appear as indicated in the image:

 

  • 6. With the selected chatbots, click "Confirm". A new screen will appear, requesting confirmation of the operation. To proceed, enter the requested text in the text box and click "Confirm".

 

Important: As noted in the text on this screen, once the bot is moved to the contract, this operation cannot be undone. So, be sure to select the correct bots and genuinely intend to carry out this operation.

 

 

  • 7. After this step, a new message confirms the migration of the chatbots.

 

If you have other chatbots to move, select the "Continue migrating" option and repeat steps 3 to 7.

Once you've moved all the necessary bots, select the "Access [your contract name]" option, and you'll be redirected to the contract, where you can see the chatbots associated with it.

 

 

Note that by completing the previous step, you've been redirected from "portal.blip.ai" to a new URL in the format "[your contract identifier].blip.ai".

Through this new URL, the chatbots associated with the contract will be displayed. However, access via "portal.blip.ai" will still work perfectly; you just need to select the contract in the upper-left corner, if necessary, as explained earlier in section 1.

 

Activation of Contract View and Important URL Changes

As part of the Contract View activation process on the Blip platform, some new URLs will be made available for your operation. Learn more about this change by following the topics below.

 

URL Changes for Blip Desk and Portal

The URL that agents use to access Blip Desk and the Portal will be changed, and all agents will need to access the new address mandatory.

 

The old URLs won't be deactivated, but they should be avoided. If access to the old Blip Desk URL persists, there might be performance issues in Blip Desk.

As a measure to address this risk, it's necessary to list the primary email domains of the operators and inform Blip. This way, a notice will be activated in Blip Desk to redirect the specific operator.

For this purpose, the responsible CM/CSM will provide a report with unauthorized accesses, and the client will communicate the operation.

 

Blip Chat URL Changes - App and Website

If you use Blip Chat to provide the conversational channel in your app and/or website, you need to adjust the installation script (found in Channels > Blip Chat > Installation) to consider the new URL.

After migrating the contract and cluster, the Blip Chat widget must be updated with the correct URL configuration. If this isn't done, there might be performance issues in this channel, impacting the support.

Changing the API Key is transparent and doesn't need updating.

 

Blip APIs URL Changes

API OLD URL NEW URL
API HTTP BLIP msging.net contractid.http.msging.net
API TCP BLIP tcp.msging.net contractid.tcp.msging.net
API WS BLIP ws.msging.net contractid.ws.msging.net

 

If the endpoints aren't changed in the consuming applications, their performance and functionality might be impacted. Therefore, it's crucial to pay attention to these changes.

 

HTTP API Clients

Change the URL for making HTTP calls. In all places where a request is made to the Blip API, it's necessary to update it to the new endpoint. The endpoints will be available on this page and should be copied and applied where they are already used.

 

TCP API Clients

Update the Host Name used by the C# SDK of the platform. If the TCP endpoint is used in any other routine, change it to the new URL.

 

WS API Clients

Update the Host Name used by the JS SDK of the platform. If the WS endpoint is used in any routine, change it to the new URL.

 

Messenger URL Changes

If you use Messenger as a channel, you need to access the application administration panel on Facebook and change the URLs, as shown in the example:

 

 

WhatsApp URL Changes (Container)

If you use WhatsApp, you need to change the URLs in the channel's containers. If Blip has access to the containers, we'll perform the changes ourselves. If the container is in another environment, we'll support you in making the change.

  • New URL: contractid-wa.gw.msging.net

 

Reactivation of Bots - Post-Cluster Migration

Republication of Builder Bots

After the cluster change, to finalize the process, it will be necessary to republish all bots in production so that they become online again.

Access to the builder of all migrated bots (after migrating the cluster).

 

Reactivation of HTTP Bots

For clients using the bot in HTTP protocol, it will be necessary to deactivate and activate this channel again.

Accessible at: Bot > Settings > Connection Information.

 

Reactivation of SDK Bots

For clients using the bot in SDK format, it will be necessary to deactivate and activate this channel again. Accessible at: Bot > Settings > Connection Information.

 

Blip is continuously evolving, always seeking to offer new possibilities for your business. With this new Contract View, your company will have more control over the data of your Intelligent Contacts, access to relevant information, and the ability to closely monitor the performance of all your chatbots!

Let's work together to complete this process and achieve even greater operational efficiency for your Intelligent Contacts. Count on us throughout the process!

 

If you have questions about the process, email csm@blip.aicsm@blip.ai, and our Customer Success Managers will be available to clarify them for you.



For more information, visit the discussion on the subject in our community or the videos on our channel. 😃

Related articles