System Center Orchestrator provides the Send Email activity straight out the box to deliver messages over SMTP. Sometimes additional methods of communication may be helpful, e.g. having critical alerts trigger a phone call to operations staff after-hours to maximize the chance of notification being delivered (who doesn’t like being woken up at 3 AM?). You might want to send an SMS text reminder like “Don’t forget to bring your required documents” to a new employee two hours before they’re scheduled to start on their first day. The runbooks described below can provide a supplement to email notifications by providing automated SMS text messages and voice phone calls as alternative communication channels.

This method provides arguably the least expensive means to implement SMS and voice integration (without maintaining mobile carrier aliases for every recipient). It requires only an Internet connection and a Twilio account, which can be operated in trial mode for free, or for very low cost with a full-featured account (less than $0.01 per message). If you don’t require the robust features of third party enterprise notification services like those from Derdack (see their video demo), this is a simple and cheap option.

**                                            **
NOTE: The runbooks and required files mentioned in this article are freely available for download here along with video tutorials.
**                                            **

What It Does

These example runbooks allow System Center Orchestrator notifications to be sent via SMS text messages or voice phone calls by integrating with the internet-based Twilio messaging service (no modem or mobile service required). It can send provided message content either as text in an SMS message, or machine-read as speech in a voice call. The runbooks show how to send using a known phone number or a username lookup in Active Directory, and could be used from any existing runbook in your environment that needs to send a notification using SMS text or voice.

System Center Orchestrator SMS Text Integration with TwilioIt even works with flip phones!

How it Works

The core runbook, “Send Twilio Message”, executes a PowerShell script that integrates with the Twilio service API to send the provided message to one or more recipients. It can be invoked from any runbook that needs to send such a message. Simply provide the message content, type and recipient phone number(s), and the runbook completes the message delivery in a few seconds. The below sections explain additional aspects.

Twilio Integration

Twilio provides the message delivery. The runbook’s PowerShell script uses the Twilio API to connect to the service via HTTP and requests delivery of the message to a given recipient. Therefore, a Twilio account must be available and configured for the script to use. Note that this means an Internet connection is required for message delivery.

Delivery Methods

Messages can be delivered by SMS text message or voice phone call. The method is determined by the “Message Type” parameter used when invoking the runbook (“SMS” or “Voice”). Messages are truncated to fit within the SMS 160 character limit. For voice calls, the message text is read aloud by an awkwardly charming robot voice.


The runbook references several configuration values stored in Orchestrator’s global configuration as variables. These variables define the Twilio account credentials and API files directory. Because the account credentials can be used to manipulate the account (whether accidentally or maliciously), it is recommended to enable the encryption option for the “Auth Token” variable and use Orchestrator best practices to limit access to trusted administrators.

Implementing In Your Environment

This section describes how to get the runbook working. A step-by-step installation video is also available.


We’ll assume the following is in place before getting started:

  • System Center Orchestrator 2012 or above installed
    • System Center Integration Pack for Active Directory (if sending messages by username)
    • Latest integration packs can be downloaded here
  • PowerShell 3.0 or above installed on Orchestrator runbook server(s)
  • Solution files downloaded from this page on
  • You have sufficient enthusiasm and attention span to last at least 5 minutes but not necessarily longer than 20

Twilio Setup

First you’ll want to set up a Twilio account. We won’t go into all of the details of this awesome service here as there is plenty of information on the web about that. For now, creating a free trial account is sufficient.

  1. Go to and follow the signup process. You’ll choose a phone number here.
  2. When signup is done, you should find yourself on the getting started page. Here, locate your Twilio number and the API credentials for the account.
  3. Trial accounts can only contact phone numbers that are pre-verified in your account. To add numbers you want to call or text while testing, add them under Numbers > Verified Caller IDs.

That’s it. Leave the page up to grab the account info in a later step.

Files Setup

Next, you’ll set up the API files directory. This is just a folder on the runbook server(s) with two DLL files needed by the runbook script. Create an equivalent folder on all runbook servers.

  1. Unzip the downloaded solution files into a directory of your choice that is accessible to the Orchestrator service account. For example: C:\OrchestratorFiles\Twilio
  2. Ensure the API library files are present: Twilio.Api.dll and RestSharp.dll.
  3. Optional: if wanting to obtain the above files independently for security or to use the latest version, perform the following steps to download. A zip utility like 7-zip may need to be installed. For a demo of this step, see the installation video for this related example.
    1. Open in a browser. This should trigger the download of a “nupkg” file, which is a Nuget package for the .Net Twilio API.
    2. Open the file with your zip utility and locate Twilio.Api.dll within lib\3.5. Copy this to the script folder configured above.
    3. Open in a browser. This should trigger the download of a “nupkg” file, which is a Nuget package for the .Net REST API.
    4. Open the file with your zip utility and locate RestSharp.dll within lib\net4. Copy this to the script folder configured above.

Importing the Runbooks

Note: you may want to back up your Orchestrator database before making changes (in addition to your normal scheduled backups). That makes it easy to roll back any changes.

Use the standard import functionality in Runbook Designer:

  1. Select a runbooks folder where you want the imported folder to go
  2. Right-click and choose Import
  3. Browse to the “<filename>.ois_export” file extracted from the downloaded zip file
  4. Click Finish (leave default options selected)

Once the import process finishes, you should see the following in Runbook Designer:

  • Runbooks folder “Twilio Messaging” with the example runbooks
  • Variables folder “Twilio Messaging” in Global Settings > Variables > Automys Library with several variables.
  • Placeholder configuration under Options menu
    • Active Directory: “Automys Testing  Configuration – Active Directory”

If you see runbook activities with a question mark icon, this means the required integration packs weren't installed prior to import. You’ll want to delete what you imported or roll back the database, then install the integration packs before importing again.

Configuring the Variables

Update the values for the imported variables to match your environment. Each variable has a description about what value is needed. Simply open the variable and replace the value.

The Account SID, Auth Token, and Sender Phone Number values come from your Twilio account on the Get Started page.

Configuring Active Directory Integration

In the Runbook Designer Options > Active Directory menu, update the entry “Automys Testing Configuration – Active Directory” to reflect your environment. Note: this step not required if you aren't using the runbook to send a message based on a username.

Active Directory Phone Lookup Property
Mobile Phone property required for lookup




Configuration User Name

Used to connect to domain controller. Recommend using the Orchestrator service account, e.g. DOMAIN\Username.

Configuration Password

Password for account

Configuration Domain Controller Name (FQDN)

Use simply the domain name unless not all domain controllers are reachable on the network, which would be bad

Configuration Default Parent Container

The base OU where searching should start. Can simply be DC=<yourdomain>,DC=<com> if you don’t have a more specific part of the directory where users and groups are located


Kicking the Tires

The moment of triumph is near. Several testing runbooks are provided that make it easy to run some tests. They each have the name prefix “Test – “:

  • Test - Send SMS Text Message
  • Test - Initiate Voice Call
  • Test - Send SMS Text Message By Username

To run one of the tests, just update the parameter values in the test runbook and execute:

  1. Check out the test runbook
  2. Double-click to open the “Invoke…” activity
  3. Update the existing example parameter values with your own
  4. Click Finish
  5. Check in the runbook
  6. Click Run

If the stars align, the recipient you entered should soon receive a message on their phone.


If no message is received, it’s more likely due to user error than astrology, but don’t feel bad. There are ample logs to hopefully show what went wrong. The places to check:

  • Events log in Orchestrator. View from Events tab, usually below the runbook canvas.
  • Log History for each runbook. View from Log History tab when selecting a given runbook. Double click an entry to view results of each activity, and double click activity entries to see data about each one.
  • The following details are most important on the “Execute Messaging Script” activity in the “Send Twilio Message” runbook:
    • Result Status – “Success” or “Failed” overall result of script
    • Error Message – content of any script errors that occurred. Blank if all went well.
    • Trace Log – Detailed chronology of script actions and results. Best viewed by copying the entire contents and pasting into WordPad.

If you’re still stumped, feel free to ask questions in the comments below or contact us.

Readying for Production

After testing demonstrates everything is working, remember a couple considerations before going live.

First, consider disabling the “Store activity-specific published data” logging option on each runbook. This can cause needless database growth when data isn't needed for audit or troubleshooting purposes.

Second, it is probably not advisable to use Twilio trial account past the testing phase. It’s cheap and they provide an excellent service, so pony up.

As always, please reach out if you found this helpful or have any questions. Enjoy!

Reference: The PowerShell

Here is the PowerShell used to integrate within the runbook activity, for the scripters among you:

# Set script parameters from runbook inputs and global variables

$MessageText = "{Message Text from Initialize Data}"
$MessageType = "{Message Type (SMS / Voice) from Initialize Data}"
$AccountSID = "{Twilio AccountSID}"
$AuthToken = "{Twilio Auth Token}"
$SenderPhoneNumber = "{Twilio Sender Phone Number}"
$RecipientPhoneNumbers = "{Recipient Phone Numbers from Initialize Data}"
$APIFilesPath = "{Twilio API Files Directory Path}"


# Set trace and status variables to defaults
$ResultStatus = ""
$ErrorMessage = ""
$Trace = (Get-Date).ToString() + "`t" + "Script started" + " `r`n"
# Create argument array
$argsArray = @()
$argsArray += $MessageText
$argsArray += $MessageType
$argsArray += $AccountSID
$argsArray += $AuthToken
$argsArray += $SenderPhoneNumber
$argsArray += $RecipientPhoneNumbers
$argsArray += $APIFilesPath

# Establish a new session (to localhost) to ensure 64bit PowerShell runtime
$Session = New-PSSession -ComputerName localhost

# Invoke-Command used to run the script contents in the new session
$ReturnArray = @()
$ReturnArray = Invoke-Command -Session $Session -Argumentlist $argsArray -ScriptBlock {

        [string]$MessageType = "SMS",






    # Define function to add entry to trace log variable
    function AppendLog ([string]$Message)
        $global:CurrentAction = $Message
        $global:TraceLog += ((Get-Date).ToString() + "`t" + $Message + " `r`n")

    # Set new session trace and status variables to defaults
    $ResultStatus = ""
    $ErrorMessage = ""
    $global:TraceLog = ""

        AppendLog -Message "Script executing in child PowerShell session"
        AppendLog -Message "Running as user [$([Environment]::UserDomainName)\$([Environment]::UserName)]"
        AppendLog -Message "MessageText=[$MessageText]; MessageType=[$MessageType]; AccountSID=[$AccountSID]; AuthToken=[$($AuthToken -replace ".", "*")]; SenderPhoneNumber=[$SenderPhoneNumber]; APIFilesPath=[$APIFilesPath];"

        # Check for Twilio API library files
        AppendLog -Message "Loading Twilio API library"
        $libraryFilesPath = $APIFilesPath.TrimEnd('\')
        $libraryFileList = "Twilio.Api.dll","RestSharp.dll"
        foreach($fileName in $libraryFileList)
            $filePath = $libraryFilesPath + "\" + $fileName
            if((Test-Path $filePath) -eq $false)
                throw "Required API file $fileName not found at expected path $libraryFilesPath"

        # Load Twilio .NET API library
        Add-Type -Path ($libraryFilesPath + "\" + "Twilio.Api.dll")

        # Create Twilio client object
        $twilioClient = New-Object Twilio.TwilioRestClient($AccountSID, $AuthToken)

        # Verify access to account
        AppendLog -Message "Validating Twilio account"
        $accountTest = $twilioClient.GetAccount()
        if($accountTest -eq  $null -or $accountTest.Sid.Length -eq 0)
            $errorMessage = "Failed to access Twilio account. Validate the configured account SID and auth token match the API Credentials shown at"
            if($accountTest.RestException -ne $null -and $accountTest.RestException.Message.Length -gt 0)
                $errorMessage += " Details: " + $accountTest.RestException.Message
            throw $errorMessage

        # Get list of recipients from comma-separated RecipientPhoneNumbers parameter
        $recipientList = $RecipientPhoneNumbers -split ","
        AppendLog -Message "Specified recipients: [$RecipientPhoneNumbers]"

        # Truncate message to fit within SMS limit
        if($MessageText.Length -gt ($MESSAGE_CHARACTER_LIMIT - 3))
            $MessageText = $MessageText.Substring(0, $MESSAGE_CHARACTER_LIMIT - 3) + "..."

        # Send message(s) via the specified method
        AppendLog -Message "Sending messages"
        $errorList = @()
        foreach($recipient in $recipientList)
                "SMS" {
                    # Send SMS message using supplied message text
                    $sendResult = $twilioClient.SendSmsMessage($SenderPhoneNumber, $recipient, $MessageText)
                "Voice" {
                    # Build voice message URL
                    [Reflection.Assembly]::LoadWithPartialName("System.Web") | Out-Null
                    $encodedText = [System.Web.HttpUtility]::UrlEncode($MessageText)
                    $messageURL = "" + $encodedText

                    # Send voice message using supplied message text
                    $sendResult = $twilioClient.InitiateOutboundCall($SenderPhoneNumber, $recipient, $messageURL)

            # Check results
            if($sendResult -eq $null -or $sendResult.Status.Length -eq 0)
                $errorMessage = "Failed to send message."
                if($sendResult.RestException -ne $null -and $sendResult.RestException.Message.Length -gt 0)
                    $errorMessage += " Exception details: Status=[" + $sendResult.RestException.Status + "], Message=[" + $sendResult.RestException.Message + "]"
                $errorList += $errorMessage
                AppendLog -Message "Successfully sent message to [$recipient]"

        # Validate results
        if($errorList.Count -gt 0)
           $errorString = $errorList -join ";"
           throw "Encountered $($errorList.Count) failures while sending messages. Details: [$errorString]"
            AppendLog -Message "Completing sending for all recipients"
            $ResultStatus = "Success"
        $ResultStatus = "Failed"
        $ErrorMessage = $error[0].Exception.Message
        AppendLog -Message "Exception caught during action [$Script:CurrentAction]: $ErrorMessage"
        if($ErrorMessage.Length -gt 0)
            AppendLog -Message "Exiting child session with result [$ResultStatus] and error message [$ErrorMessage]"
            AppendLog -Message "Exiting child session with result [$ResultStatus]"

    return  @($ResultStatus, $ErrorMessage, $global:TraceLog)   
}#End Invoke-Command

Remove-PSSession $Session

# Get properties from child session return
$ResultStatus = $ReturnArray[0]
$ErrorMessage = $ReturnArray[1]
$Trace += $ReturnArray[2]
$Trace += (Get-Date).ToString() + "`t" + "Script finished" + " `r`n"