Example call flow for the data dip connector


Note: This article applies to the web services data dip connector.

This article describes example call flows in Architect that uses connector actions with the web services data dip connector.

In this example call flow, the IVR plays audio messages based on information that the connector group retrieves from a web service, which returns information from a CRM. The connector group retrieves this information by calling a bridge action (ExampleContactByPhoneNumber) that is associated with the default connector action GetContactByPhoneNumber.

  1. In the task called Query CRM, the Call Bridge Action sends a request to the web service with the default connector action GetContactByPhoneNumber. The web service calls the CRM for the ANI. The IVR returns information about the contact from the CRM, which sends the information to the web service. The web service forwards the information to the bridge action.
    1. If the Call Bridge Action succeeds, Architect proceeds to the decision tree. (See step 2.)
    2. If the Call Bridge Action fails or times out, Architect plays an error message and then disconnects.
  2. In the decision tree, Architect checks to see if the contact is associated with the membershipLevel Diamond.
    1. If the contact is associated with the membershipLevel Diamond, Architect plays a message and then disconnects the call.
    2. If the contact is not associated with the membershipLevel Diamond, Architect plays a different message and then disconnects the call.

Click image to enlarge.

Screenshot of an example call flow in Architect for the data dip connector

In this example call flow, the IVR plays an audio message requesting input from the caller. The bridge action sends this input to the web service and receives data back from the web service. The call flow then evaluates this data and plays audio messages based on the result of the evaluation. The connector group retrieves this data by calling a bridge action (SampleAppCodeEvaluation) that is associated with the custom connector action CustomAction.

  1. In the task called Collect Input, the IVR asks the caller to input the caller’s five-digit code.
    1. If the Collect Input succeeds (the caller inputs five digits), Architect proceeds to the bridge action. (See step 2.)
    2. If the Collect Input fails (the caller does not input five digits), Architect plays an error message and then disconnects.
  2. In the task called Evaluate Code via Web Service, the Call Bridge Action sends a request to the web service with the custom connector action CustomAction. The web service retrieves the status of the code input and whether the caller won from the CRM. The web service forwards this information to the bridge action.
    1. If the Call Bridge Action succeeds, Architect proceeds to the decision tree. (See step 3.)
    2. If the Call Bridge Action fails or times out, Architect plays an error message and then disconnects.
  3. In the decision tree, Architect compares the status code received from the web service to determine if the caller is the winner.
    1. If the caller is a winner, Architect plays a message and then disconnects the call.
    2. If the caller is not a winner, Architect plays a different message and then disconnects the call.

Click image to enlarge.

Example call flow for the web services data dip connector

For more information about creating call flows for this connector, see Use bridge actions in Architect.

For more information about the connector, see About the web services data dip connector.