Description:

The Send Voice Call workflow step sends a voice message to a specified recipient phone number using the Twilio service.

The step requires the recipient's phone number, including the country code, and the voice message that should be delivered.

The step supports:

• Sending a voice call through Twilio
• Specifying a recipient phone number with country code
• Providing a voice message
• True and False return paths

Usage:

The Send Voice Call step is typically used when a workflow needs to communicate information to a recipient through a telephone voice call.

For example, a workflow can use the step to:

• Notify a person when a workflow reaches an important stage.
• Deliver an operational alert.
• Communicate a workflow status or event.
• Provide a voice notification following a business activity.
• Contact a recipient when a process requires telephone-based communication.
• Escalate an event by placing a voice call.

The step is particularly useful for workflow events where a voice notification is more appropriate than a text-based notification.

When the workflow reaches the Send Voice Call step, FlowWright uses the configured Twilio service to send the voice call to the specified phone number.

Configure the Twilio subscription information under the FlowWright configuration settings. For more info, visit: https://www.twilio.com/ 

Typical Workflow Suggestions

Approval Notification

Use the step to notify a recipient when an approval has been completed or requires attention.

Example:

Submit Request → Approval → Send Voice Call → Continue

A voice call can be used when the approval event requires direct telephone notification.

Critical Process Alert

Use Send Voice Call when a workflow reaches an important or time-sensitive event.

Example:

Monitor Process → Critical Event → Send Voice Call → Continue

The voice message can communicate the event that requires attention.

Escalation Notification

Use the step as part of an escalation workflow when an issue requires direct notification.

Example:

Process Issue → Escalation → Send Voice Call → Resolve

This can provide an additional communication channel for workflow escalations.

Workflow Completion Notification

Use Send Voice Call to notify a recipient when an important workflow has completed.

Example:

Process Request → Complete Processing → Send Voice Call → End

The voice message can communicate the completion of the process.

Operational Alert

Use the step to deliver an operational message when a workflow detects an event that requires human attention.

Example:

Monitor Operation → Detect Event → Send Voice Call → Continue

Time-Sensitive Notification

Use a voice call when the workflow needs to communicate an event that should not rely solely on email or other text-based communication.

Example:

Detect Time-Sensitive Event → Send Voice Call → Continue Processing

Example:

Let’s build and execute the “TwilioSendCallDef” example.          

• Create a new definition called “TwilioSendCallDef” and open the definition in designer mode. 
• Drag a “twilioSendCall” step to the canvas.
• Connect the dots between the “Start” and “TwilioSendCall” steps, as shown above. 
• Select the line between the steps to configure the “Connection Properties”. The default property values are “None, Error, Evaluate, and Timeout”. Depending on the step’s purpose, additional values are available for configuration. 
• Click the "twilioSendCall" step to configure its "Required" properties. Provide a name for the step. Enter the receiver's phone number with the country code. Enter the text to be converted into voice messages. Click the Save button. Note: Click the "AI Predict" button to have the Copilot add new process steps that match your process description. 

• The “Logging” configuration is necessary for documentation and also measures workflow progress and percent complete. This is achieved by configuring the step state and percent fields individually, as shown in the images below. Configure the “Logging” using the following properties.

• Save the process definition, create a new instance, and execute it. Render the process instance. Click the process step to view its properties. The step should place a voice call to the specified mobile number. 

Tips:

• Include the country code in the recipient phone number.
• Verify that the phone number is correct before executing the workflow.
• Keep voice messages concise and clear.
• Use meaningful step names such as “Notify Manager by Phone”, “Send Critical Alert”, or “Call Customer”.
• Test the voice message with representative phone numbers before deploying the workflow to production.
• Consider the purpose of the notification when deciding whether a voice call is more appropriate than another communication method.
• Use the True and False return paths to route the workflow based on the step's result.
• Avoid placing sensitive information in voice messages unless the workflow and communication requirements have been appropriately reviewed.

Notes:

The Send Voice Call step is defined in the Twilio category with the internal name twiliosendcall and display name Send Voice Call.

The workflow step is implemented by the FlowWright.Workflow.TwilioSendCall namespace in FlowWright.Workflow.dll and is defined as a Process step. It supports 2 incoming connections and 2 outgoing connections.

The step has two configurable properties:

• Receiver phone number (With country code)
• Enter voice message

Both properties are marked as required in the XML.

The Receiver phone number property uses the string data type and the FlowWright.DataTypes.ClsTextBox implementation. 

The Enter voice message property uses the multilineTextBox data type and the FlowWright.DataTypes.ClsMultilineBox implementation. 

The XML defines two return paths: False and True.

The XML does not expose additional configuration properties for attachments, CC/BCC recipients, email addresses, or SMS content. Its configuration is limited to the recipient phone number and voice message.

Feature comparison.

Definition Sample:

You may download a sample definition when provided and import it into your FlowWright Process Definition.

Note: Verify and complete any missing configuration after importing a sample, including:

• Receiver phone number
• Country code
• Voice message
• Outgoing workflow connections
• Environment-specific Twilio configuration

After verifying the configuration, save the Process Definition before execution.

Click here to download the sample file.