CVG 1.6.2 (08-Dec-2020)

Last update in 2020! Version 1.6.2 comes with some smaller improvements regarding UX, Dialogflow integration, assist use case and outbound calls. We start with our frozen zone now without any changes before mid of January.

It was a very special year. We are fortunate to be able to contribute to digitization, which has become so important in times like these. Bots that our customers have built have answered many standard queries. This made it easier to manage the rush; human agents could concentrate on the more complex tasks.

Wishing you a very joyful holiday season despite these difficult times. And a healthy new year!

Console (UI)

Improved Filters for Dialogs History

For usability reasons the filters are now delivered with the following operators instead of regex expressions:

• starts with

• ends with

• contains

• equals

• not equals

Chips, small UI elements, display the state of the filters for opened and closed filter accordeon.

Dialogflow Integration

Just a few days after initial release of our Dialogflow integration we got requests to make more API parameters available to Dialogflow. Here we go. We’ve aligned these parameters now, so that in general all parameters available in our API are available in Dialogflow.

We also send greeting, termination, inactive, answer as input context now and not longer as status.

E.g., the input context greeting send from CVG to your Dialogflow agent now includes the phone number of the caller

{
  "dialogId": "09e59647-5c77-4c02-a1c5-7fb2b47060f1",
  "timestamp": 1535546718115,
  "local": "+4972112345678",
  "remote": "+4972110203040",
  "language": "de-DE"
}

Please note our updated documentation.

Cognigy Integration

The new parameters available in Dialogflow are also available in our Cognigy integration.

Please note our updated documentation.

APIs

Improved Dial-out Timeouts

Timeout handling of dialogs initiated via /call/dial has been corrected. A two minutes (120000 ms) limit for ringTimeout has been introduced.

Bugfix: Prevent Assist Messages from getting sent to Bots

In the assist use case transcriptions are now only sent to the given Assist-URL via /assist/transcript. The Bot does not (accidently) receive these /message requests any longer.