Use this guide to set up AGRIS SMS text messaging with Twilio and enable batch text delivery through the AGRIS notification queue.

Scope: This page covers the AGRIS-side setup needed for SMS texting, the Twilio prerequisites, the notification import format, and the basic workflow for sending and reviewing messages.

Prerequisite: AGRIS SMS texting assumes your Twilio integration is already configured in AGRIS Web Service. SMS delivery also depends on recipients having the correct phone contact type configured in the Name/Address system.

Before you begin

Confirm you have access to AGRIS Communications and AGRIS Web Service configuration.
Confirm your organization has a Twilio account.
Make sure the Twilio account is upgraded if you plan to send live messages.
Verify you have an active Twilio phone number.
Complete Twilio number verification and any required A2P 10DLC or toll-free registration steps.
Confirm SYS Extended Option #28, Notification Service, is activated for the Twilio integration scenario.

Step 1: Set up Twilio

AGRIS uses Twilio as the SMS delivery provider. Start in the Twilio console and prepare the account before configuring AGRIS.

Create or sign in to your Twilio account.
If needed, use the Twilio setup flow to get a phone number.
Upgrade the account from trial to paid if you need to send production messages.
Verify the phone number.
Complete toll-free verification or A2P 10DLC registration, depending on the number type and use case.
Record the account information and phone number from the Twilio console for AGRIS configuration.

Twilio trial accounts are useful for testing, but production sending generally requires an upgraded account and completed registration for the sending number.

Step 2: Configure the AGRIS Web Service integration for SMS

In AGRIS, configure a new integration for Twilio under the Communications area.

Open CFT > Communications > AGRIS Web Service.
Add a new integration.
Set Output Option to 3 - Transaction Server Queue.
Set Use CFT Service URL? to Y.
Set Transaction Integration to 80 - Twilio.
Open Credentials and enter the Twilio account details.
Save the integration and select the desired transactions and filters.

For notification processing, both Contact Type and Earliest Business Date filters must be entered on the integration.

For transaction-based notifications such as commodity tickets and invoices, configure the communication options and customize the message content for each desired transaction type.

Step 3: Prepare recipient phone numbers in Name/Address

AGRIS looks up recipient phone numbers from the Name/Address system using the configured contact type.

Open the customer records in the Name/Address system.
Add or confirm each recipient phone number.
Use the same Contact Type that the Twilio integration and import file will reference.
Save the customer records.

If a customer does not have a valid phone number for the selected contact type, that customer’s SMS notification import will be rejected.

Step 4: Create the SMS notification import file

AGRIS supports importing SMS notifications from a CSV file into the notification queue. The import layout is available under Maintenance > File Layouts For Imports.

Column	Purpose	Required value

Column	Purpose	Required value
A	Record type	Always `CFTN0`
B	Twilio integration number	The integration number from CFT > Communications > AGRIS Web Service
C	Customer identifier	Customer Name ID
D	Phone contact type	The Name/Address contact type used for SMS
E	Package	Any valid package such as `NAM`, `GRN`, `ACP`, or `ACR`
F	Location	Optional location value
G	Notification type	Any user-defined 5-character code
H	Notification description	Any user-defined description up to 30 characters
I	Document number	Optional document reference
J	Text message	The SMS message body

Build the file in Excel or another spreadsheet tool, then save it as CSV.

Example use case: send the same service alert to all customers, or generate customer-specific messages such as outstanding A/R balance reminders.

Step 5: Import the CSV into AGRIS

Open Reports > Import Procedures.
Select the SMS notification import file.
Run the import.
Review any rejected rows and correct missing or invalid data.

The most common reject condition described in the source material is a missing TXT phone number for the customer in Name/Address.

Step 6: Review sent messages

After import, AGRIS sends the notifications through the configured Twilio integration. You can review activity in Communication Inquiry.

Go to CFT > Communications > AGRIS Web Service > Communication Inquiry.
Locate the notification record in the inquiry grid.
Select a line to review message details.
Click Details to view the actual text that was sent.

Optional report-driven ways to generate SMS imports

AGRIS also includes report-based approaches that can help generate import-ready CSV files.

Option 1: Create SMS import from Name/Address data

Run NAM > Report Manager > Name/Address Reports > Print Standard Reports > Name/Address Detail Spreadsheet to generate a customer CSV file.
Run CFT > Communication Reports > Print Standard Reports > Create SMS Text Import From NAME-IDS.CSV to convert that file into notification import format.
Edit the generated CSV to add the text message content.
Import the file through Reports > Import Procedures.

Option 2: Create SMS import from monthly statements

Run CFT > Communication Reports > Print Standard Reports > Create SMS Text Import From Statements.
Review the generated CSV file.
Import the file through Reports > Import Procedures.

These standard reports can be used as templates for user-defined reports, allowing you to pull AGRIS data and generate recurring or one-time text campaigns with less manual editing.

Troubleshooting tips

If texts are not sending, confirm the Twilio integration credentials and phone number are correct.
Make sure the integration uses 80 - Twilio and 3 - Transaction Server Queue.
Verify the customer has the expected SMS contact type and phone number in Name/Address.
Check that the integration filters include the required Contact Type and Earliest Business Date.
Confirm the Twilio account is upgraded and the sending number is verified and registered for the intended messaging use case.
Use Communication Inquiry to confirm whether the message was created and what content was sent.

Do I need Twilio before setting up AGRIS SMS? Yes. The AGRIS SMS feature depends on a Twilio integration being configured first. Can I send the same text to many customers at once? Yes. The CSV import feature supports batch sending to many customers in one import. Can messages be customized per customer? Yes. Column J in the import file can contain a different message for each customer. Where do I review what was sent? Use CFT > Communications > AGRIS Web Service > Communication Inquiry, then open the message details.

AGRIS SMS Text Messaging Installation Instructions