Skip to main content
Vodafone Bulk Text helps you send high-volume SMS from the systems your team already uses. Use it when a message needs to reach customers, staff, or stakeholders quickly.

​
Customer notifications

Send account alerts, order updates, booking confirmations, or service changes from your CRM, commerce platform, or customer database. Typical payload fields:
  • text for the customer-facing message
  • from for the approved Sender ID
  • recipientInfo[].msisdn for the recipient number
  • recipientInfo[].notifyId for your internal record reference

​
Appointment reminders

Use scheduled sends for reminders that must arrive before a booking, collection, visit, or service window.
Appointment reminder
{
  "text": "Your appointment is tomorrow at 10:00. Reply CONFIRM or CANCEL.",
  "from": "Vodafone",
  "campaignName": "Appointment reminders",
  "recipientInfo": [
    { "msisdn": "353861234567", "notifyId": "appt-8821" }
  ],
  "sendAt": "2030-06-01T09:00Z"
}

​
Staff updates

Send operational updates to employees, contractors, or field teams. Use notifyId to match each callback to a shift, rota, incident, or workforce record.

​
Promotions and marketing campaigns

Send promotional campaigns to opted-in recipients. Include opt-out instructions where required and maintain your suppression list when you receive STOP or OPTOUT replies.
You are responsible for consent, opt-out handling, and sender registration requirements. See Compliance.

​
Time-sensitive service alerts

Use SMS for outage notifications, incident updates, delivery changes, and urgent operational messages. For high-priority workflows, store webhook and DLR callbacks so your system can reconcile message status later.

​
CRM and database integrations

Most integrations follow the same pattern:
  1. Read recipients from your CRM or customer database.
  2. Request an access token from https://auth.vodafone.com/token.
  3. Send a campaign through POST /api/v2/Campaign.
  4. Store the response and notifyId values.
  5. Receive webhooks and DLRs at your callback endpoint.
  6. Update each customer or campaign record with the final status.
See Architecture for the full system flow.
Last modified on May 6, 2026