Exits

The Exits tab enables you to route the call to new or pre-configured components, depending on the following scenarios:

Reply command exits: Different reply commands can be set up to contemplate the many ways in which the patient may reply. Following our example above: The “Exit name” defined is "confirm" (“Reply Command #1”). So, in case the answer is affirmative, an SMS notification is sent to the patient confirming the appointment.

No Match: In this section, you must select where to send the call if the SMS command does not match any keyword.

SMS Error: Select a component that will be executed in case there’s an error, such as a network issue.

Invalid Number: Choose where to route the call if the destination number is invalid. This will happen if the external device is switched off, has no reception, if the number is deactivated, or in the wrong format. In our example, we’ve decided to use the “End flow” component, which will terminate the flow if the notification sent through our API request cannot reach the destination phone number.

Timeout: In the “Timeout” section, add the maximum number of hours the system will wait for the patient to reply. Note: The minimum value for the timeout is one hour and the maximum is 24 hours. In case the user inserts a number outside this range, the system will trigger an error.

Error handling: This section is available in most Studio components. You can use it to define the behavior for unexpected failure during the execution of a component. For more information on this section, please refer to the "Error handling" documentation.