Series: Architect tutorial for beginning users

In this lesson, you continue setting up actions that you will eventually add to the Main Menu. 

Objectives

  • Create lost and found pet reporting reusable tasks.
  • Add task actions to collect information from the caller and determine where to send the call, based on input.
  • Continue the flow path using data actions to obtain caller information.

Estimated time to complete: 25 minutes

Prerequisites

  • Ensure that your administrator created and configured a working data action. For more information, see Add a data actions integration.
  • Complete lessons 1–2.
  • Review Work with tasks.
  • Have a telephone number appropriate for tutorial testing, such as a mobile phone or direct line, to which you can transfer calls.

Additional resources


Lost Pet completed task

Click the image to enlarge.

Completed task

Found Pet completed task

Click the image to enlarge.

Completed task

Tasks

In this section, you create reusable tasks that give callers the option to access the Pet Lost and Found menu to report a lost or found pet. Using Pet ID information collected from the caller, Architect passes the data to an external system using a data action. Architect requires a data action to pass data collected in an IVR to an external system.

  1. From the Toolbox, expand the Task category and drag a Task action into the Reusable Tasks area.
  2. In the Name box, type Lost pet and then click Done.
  1. From the Toolbox, expand the Data category and drag a Collect Input action to just below the Start menu and complete the following tasks:
    1. In the Name box, type Get Pet ID or Phone.
    2. In the Input Audio box, type Prompt.GCACPetID.
    3. In the Input Data Name box, type Flow.PhoneOrPetID.
    4. In the Number of Digits areas, click change to range.
    5. Move the digit sliders until the Range of Digits reads Any number of digits between 8 and 10, inclusive.
    6. Leave the remaining settings unchanged.
  2. Expand the Audio category and drag a Play Audio action below the Get Pet ID or Phone action’s Success path and do the following:
    1. In the Name box, type Processing ID.
    2. Click the Edit Audio Sequence  button at the end of the Audio box. The Edit Audio Sequence dialog box opens.
    3. Click Add TTS and in the Text To Speech box, type Thank you. Please wait while we process your account request.
    4. Click Add blank Audio and in the Blank audio field, leave the default blank audio unchanged.
    5. Click Close.

Add a Decision action to the flow that decides the path the call takes, depending on whether the caller entered an 8-digit Pet ID, or a 10-digit telephone number. Use the following expression:

length(Flow.PhoneOrPetID) == 8

Based on the expression as written, if the entry is eight digits, then Architect matches the ID to the account via a previously created data action. If the entry is not eight digits, then Architect transfers the call to the Reporting office, where the caller can speak with a Genesys Cloud Animal Care representative.

  1. Expand the Logical category and drag a Decision action into the task editor below the Processing ID action.
  2. In the Name box, type Phone or Pet ID.
  3. In the Expression area, click the Expression modes button and select Expression button to switch to expression mode. The box changes to allow expression entry.
  4. In the Expression box, type length(Flow.PhoneOrPetID) == 8.

If the caller entered an 8-digit number, then Architect retrieves the customer’s account information, matches it to the Pet ID, and checks the pet as lost. If the customer did not enter a valid Pet ID, then Architect transfers the caller to Genesys Cloud Animal Care’s pet shelter, where a representative personally collects the caller’s information.  

  1. From the Toolbox, expand the Data category, drag a Call Data Action below the Phone or Pet ID action’s Yes path, and complete the following steps:
    1. In the Name field, type Submit Pet ID as Lost.
    2. Click the arrow at the end of the Category list and select the category that contains the data action.
    3. Click the arrow at the end of the Data Action list and select the data action that contains the Pet ID database.
    4. In the Inputs area, a field for account number entry or equivalent appears. Type Flow.PhoneOrPetID, which holds the caller’s entered information.
  2. From the Toolbox, drag a Play Audio action below the Submit Pet ID as Lost action’s Success path and complete the following steps:
    1. In the Name box, type Pet ID Sent.
    2. In the Audio box, type prompt.GCACShelter.
  3. From the Toolbox, expand the Transfer category and drag a Transfer to Number action below the Phone or Pet ID Decision Action’s No path and complete the following steps:
    1. In the Name box, type Transfer to Shelter.
    2. In the Pre-Transfer Audio box, type prompt.GCACRepresentative.
    3. Add your choice of TTS for failed transfer audio.
    4. In the Number box, type a telephone number appropriate for tutorial testing, such as your mobile phone or direct line.
  4. From the Toolbox, expand the Menu category, drag a Jump to Menu action below the Submit Pet ID as Lost action’s Failure path, and select the Main Menu.
  5. From the Toolbox, expand the Menu category and drag a Previous Menu action below the Submit Pet ID as Lost action’s Timeout path.
  6. From the Toolbox, drag a Disconnect action below the Pet ID Sent action.
  7. Click Return to Overview.

Practice

Following similar strategy used in the Tasks section, create a Found Pet reporting task. 

  1. Name the reusable task Found Pet.
  2. Add a Collect Input action to the task and do the following:
    1. Name the action Enter Pet ID or hold for representative.
    2. Add the Prompt.GCACPetID prompt.
    3. Use Flow.PhoneOrPetID as input data.
    4. Use a range of digits between 8 and 10 inclusive.
    5. Leave the remaining settings unchanged.

Add a Decision action to the flow that decides the path that the call takes, depending on whether the caller enters an 8-digit Pet ID, or a 10-digit telephone number. Complete the following steps:

  1. Name the action Was Pet ID entered?
  2. Switch to expression mode and add the following expression: length(Flow.PhoneOrPetID) == 8.

  1. Add a Call Data Action below the Was Pet ID entered? action’s Yes path and complete the following steps:
    1. Name the action Submit Pet ID as Found.
    2. Select the category that contains the data action.
    3. Select the data action that contains the Pet ID database.
    4. In the Inputs area, a field for account number entry or equivalent appears. Type Flow.PhoneOrPetID, which holds the caller’s entered information.
  2. Add a Play Audio action below the Submit Pet ID as Found action’s Success path and do the following:
    1. Name the action Pet ID Sent.
    2. In the Audio box, type prompt.GCACShelter.
  3. Add a Transfer to Number action below the Phone or Pet ID Decision Action’s No path and complete the following steps:
    1. Name the action Transfer to Shelter.
    2. In the Pre-Transfer Audio box, type prompt.GCACRepresentative.
    3. Add your choice of TTS for failed transfer audio.
    4. In the Number box, type a telephone number appropriate for tutorial testing, such as your mobile phone or direct line.
  4. Add a Jump to Menu action below the Submit Pet ID as Found action’s Failure path and select the Main Menu.
  5. Add a Previous Menu action below the Submit Pet ID as Found action’s Timeout path.
  6. Add a Disconnect action to end the task.
  7. Save your work.

Lesson 2: Create the initial flow and add menus :Previous Suggested Article Next Suggested Article: Lesson 4: Create a reusable task for pet tracking services