The SMS Integration enables a secure and automated connection between your chosen SMS service provider and Taguchi.
It supports multiple messaging platforms, allowing you to send SMS and MMS messages directly from Taguchi while ensuring data security, automation, and reliability.

---

SMS Integration Setup

To create a new SMS integration, ensure your user account has the required Integration Role privileges.
You can find the integration setup page under:

Settings → Integrations

Select ‘New Integration’ to begin.

Within the setup screen, there are two main sections:

1. Details
2. Configuration

---

Available SMS Integration Options

The following messaging integrations are available in Taguchi:

• Messaging: Sinch SMS
  • Formerly known as MessageMedia.
  • Uses API key and API secret credentials.

• Messaging: Sinch SMS (Legacy)
  • Formerly known as MessageMedia.
  • Uses username and password credentials.

• Messaging: Tall Bob SMS
  • Formerly known as VidCorp SMS.
  • Uses username and password credentials.

• Messaging: Twilio Notify (Legacy)
  • Requires Account SID and Authorization Token credentials.

• Messaging: Twilio SMS/MMS
  • Requires Account SID and Authorization Token credentials.
  • Supports MMS messages and custom sender numbers.

---

Details

1. Set the integration name:
   Choose a clear, descriptive name to identify the integration.

2. Select integration type:
   Under Type, choose the relevant SMS option.
   Integration types are grouped under:

   • API
   • Import
   • Export
   • Messaging
   • Scheduled

3. Inbound Webhook URL:
   This is a callback URL where your SMS provider sends HTTP POST requests containing message or event data.
   Add this in your SMS account dashboard to enable inbound message handling.

---

Configuration: Sinch SMS

1. Credential to use: Select credentials set up earlier.
2. Unsubscribe all profiles with the same number: Ensures that all matching profiles are unsubscribed when one unsubscribes.
3. List IDs to unsubscribe from: Specify which list(s) unsubscribes apply to.
4. Sender ID: Originator name or number of the SMS.
5. Sender ID Type:
   • Alphanumeric: Up to 11 characters (A–Z, 0–9).
   • International: Standard mobile number in international format.
   • Shortcode: 4–6 digits, depending on country.
6. Tracking domain: Optional; used for link tracking and analytics.

---

Configuration: Tall Bob SMS

1. Credential to use: Select previously created credentials.
2. Sender ID: Originator name or number.
3. Unsubscribe phone number: Number for replies/unsubscribes.
4. Shorten URLs: Enables Tall Bob link shortening.
5. Unsubscribe all profiles with the same number: Global unsubscribe option.
6. List IDs to unsubscribe from: Specify applicable lists.
7. Tracking domain: Optional; use configured domain for link tracking.

---

Configuration: Twilio SMS/MMS

1. Credential to use: Select credentials set up earlier.
2. Messaging Service SID (optional): Unique Twilio identifier for message routing.
3. ‘From’ number: Sender’s phone number (ignored if Messaging Service used).
4. Enable MMS support: Allows multimedia messaging.
5. Enable link shortening: Enables Twilio’s link tracking feature.
6. Unsubscribe all profiles with the same number: Global unsubscribe.
7. List IDs to unsubscribe from: Specify list IDs.
8. Tracking domain: Optional; for link tracking and analytics.

---

Save Changes and Activate

Once your integration details and configurations are complete:

1. Save changes
2. Activate the integration

You can only activate after saving.

---

Deactivate

To stop the integration, click Deactivate.
This will disable the connection between Taguchi and your SMS provider.

---

Active Integration Status

Once activated, the integration icon changes color:

• 🟢 Green: Active / Deployed
• 🟡 Yellow: Deactivated
• 🔴 Red: Deployment failed

---

Updating an Integration

You can update integrations while active or inactive.
After editing, click Save changes — the update will take effect immediately.

---

Troubleshooting Measures

• Verify all inputs (e.g., credentials, URLs, IDs) — incorrect data may cause failures.
• If the integration fails to deploy or data doesn’t sync, double-check your credential permissions.

For further assistance, please contact Taguchi Support.

---

---