--- title: "Fall '25 Twilio" slug: "fall-25-twilio" tags: ["Admin", "Expanded Content", "TMS Admin", "Twilio", "Fall '25"] updated: 2026-02-24T15:53:04Z published: 2026-03-03T14:14:34Z canonical: "documents.revenova.com/fall-25-twilio" --- > ## Documentation Index > Fetch the complete documentation index at: https://documents.revenova.com/llms.txt > Use this file to discover all available pages before exploring further. # Fall '25 Twilio The Twilio integration provides the ability to scale the sending of emails when requesting Carrier quotes and performing other TMS actions. This integration provides additional email sends when routinely reaching the Salesforce cap. ## Setup ### **Enter Credentials** Enable the Twilio integration by completing the following steps. 1. Navigate to **TMS Admin**. 2. Select **Credentials**. 3. Select the **Global Services** tab. 4. Find Twilio in the list and open the card. 5. Check the **Enabled** box. 6. Enter the **User ID** into the text field. This is the single verified email address from Twilio. 7. Click the **Save** button when finished. Valid credentials are required from a Twilio subscription. See examples in the table below. | User ID | Password 1 | Password 2 | Customer Number | | --- | --- | --- | --- | | Email Address | API Key generated on the Twilio portal. | | | > [!NOTE] > If Domain Authentication setup was completed, the User ID is "Revenova" instead of the email address. ### **Remote Site Settings** Upgrading from previous versions of the TMS may have outdated information. Check that the Remote Site Settings for the Twilio integration URL are up to date. 1. Click the **Setup** gear icon in the top right corner. 2. From the drop-down, click **Setup**. 3. In the Quick Find Toolbar type *Remote Site Settings* and click the link. 4. From the list of remote sites find *Twilio* and click the **Edit** link. 5. Update the Remote Site URL to match the *Service URL* below. Service URL: https://api.sendgrid.com Test Service URL: https://api.sendgrid.com > [!WARNING] > The Twilio integration requires a file extension for all attached documents. Uploading files into the TMS with any Revenova components maintains the file extension. Uploading documents with Salesforce components removes the file extension. Salesforce components for uploading documents are described [here](https://help.salesforce.com/s/articleView?id=sf.collab_files_uploading.htm&type=5). ## Org-Wide Email Addresses The logic controlling the Twilio integration when [Org-Wide Email Addresses](/previous-releases/docs/fall-25-organization-wide-email-address) are enabled works as follows. - Confirm permissions are configured properly to send org-wide emails with the Twilio integration. - Org-Wide Email Addresses must have the **Allow All Profiles to Use this From Address** option selected to send messages with Twilio. - Before sending email messages with Twilio, the User must have access to the User lookup field on the Load or Trip Plan objects. - The assigned OWEA is used instead of the User lookup when the User does not have the lookup permission. - If no OWEA is assigned, no error is generated and no email is sent. - The **User ID** field on the Twilio credentials card is used. - If the **User ID** field is not a valid email address, the sender’s name and email address is used instead. The [Document Options](/previous-releases/docs/fall-25-document-options-settings#email-templates) Email Template type settings control the logic for each email type sent by Twilio. - The Twilio **User ID** from the [credentials](/previous-releases/docs/fall-25-credentials#global-services) card is displayed in the **From** email address. - The **Reply-To** email address follows the Document Options settings. - The **Reply-To** email is the **Reply To** email address, when populated. - If no **Reply To** email address is set, the **Reply To User** lookup is used when populated. - If no **Reply To** email and **Reply To User** fields are set, the Org-Wide Email Address is used. - The **Sender Display Name** follows the same logic as the Reply-To email address. - If the **Reply-To** email populated, the display name is the current user’s name. - If no **Reply To** email address is set, the **Reply To User** lookup is used for when populated. - The display name is the User’s name. - If no **Reply To** email and **Reply To User** fields are set, the Org-Wide Email Address display name is used. ## Integration Call The Twilio integration is called when one of the four actions below are completed in the TMS. Twilio returns either a success message or an error payload containing information describing why the request failed. ### **Mail Send** Four TMS actions call the Twilio integration for email send. - [Send Email LWC](/previous-releases/docs/fall-25-send-email#send-email) - [Rate Entry Upload Job](/previous-releases/docs/fall-25-rfp-banner#rfp-banner) - Carrier Request for Quote Emails ([CarrierBulkRFQEmailJob](/previous-releases/docs/fall-25-batch-processes)) - [EDIWatcherJob](/previous-releases/docs/fall-25-batch-processes) | **TMS Operation** | **Twilio Endpoint** | **Request Type** | **Response** | | --- | --- | --- | --- | | Email Send | Mail Send | POST | 200: OK | Sample **Mail Send** Request Payload ```json {  "personalizations": [    {      "to": [        {          "email": "email@test.com"        }      ]    }  ],  "from": {    "email": "support@revenova.com",    "name": "Org Wide Email"  },  "reply_to": {    "email": "test@revenova.com"  },  "subject": "Quote Request for Load L-12",  "content": [    {      "type": "text/html",      "value": "\n \n \n \n
\n \n \n \n
\n \n \n \n
\n \n \n \n
\n \n \n \n
\"\"
\n \n \n \n
\n \n \n \n
\n \n \n \n
Request for Load Quote
L-12
\n \n \n \n
If you would like to price this load, please click Submit Quote. 
\n \n \n \n
Load Information
\n \n \n \n
\n \n \n \n
\n \n \n \n
Pickup Date
7/18/2025

Distance
1,017.695 miles

Mode
Truckload
\n \n \n \n
\n \n \n \n
Delivery Date
7/22/2025

Total Stops
2

Total Weight
15,750 lbs
\n \n \n \n
\n \n \n \n
\n \n \n \n
\n \n \n \n
Thank you, 

User User
test@revenova.com
Scratch2-SC-US-tmsMain/packages/tmsMain-PaulMathewson-NAMESPACE

 


"    }  ] } ``` **No Payload returns when successful.** Sample error **Mail Send** Response Payload ```json {  "errors": [    {      "message": "The from address does not match a verified Sender Identity. Mail cannot be sent until this error is resolved. Visit https://sendgrid.com/docs/for-developers/sending-email/sender-identity/ to see the Sender Identity requirements",      "field": "from",      "help": null    }  ] } ``` **No TMS Field Updates** ### Email Exceptions The Twilio integration is not used when sending the following email types from the TMS. Performing the actions below sends a single email via Salesforce functionality. - Removing a [Carrier](/previous-releases/docs/fall-25-carrier-banner#remove-carrier) from a Load. - Emails sent due to [Customer Invoice](/previous-releases/docs/fall-25-customer-invoice-batch-generation#field-batch-invoicing-email-process) generation. - Sending Load documents to a user (themselves) in the Customer Portal. - Driver Confirmation email sent from the [Trip Planner](/previous-releases/docs/fall-25-trip-planning#fleet-driver-confirmation). - Tracking requests sent to a Carrier Service with an *Email* **Status** method. Batch Status request emails follow the same rules. - Bulk Tendering to Carriers from the Load [List View](/previous-releases/docs/fall-25-load-list-view#bulk-actions). - When removing a Carrier from a Load with the Truckstop event processor. - When a Load is Tendered via the Quote Wizard in the Customer Portal. - When the Tender action is completed in the [Carrier Email Loop](/previous-releases/docs/fall-25-carrier-tender-accept-decline-setup). > [!CAUTION] > Error: > > Orgs that do not use the Twilio integration may experience issues sending emails. An example is Carriers not receiving Load Tender emails from the Email Loop. Confirm the **Enabled** field is NOT *Checked* on the Twilio credentials card.