sms compliance

Sent logo
Sent TeamMay 3, 2025 / sms compliance / Article

Fiji SMS Best Practices, Compliance, and Features

Complete guide to sending SMS messages to Fiji, including compliance requirements, sender ID options, and API integration examples

Fiji SMS Best Practices, Compliance, and Features

Fiji SMS Market Overview

Sending SMS messages to Fiji requires understanding local carrier infrastructure, regulatory requirements, and technical capabilities. This guide covers everything developers and businesses need to know about SMS messaging in Fiji (FJ), including compliance guidelines, sender ID options, and API integration examples.

Locale name:Fiji
ISO code:FJ
RegionOceania
Mobile country code (MCC)542
Dialing Code+679

Market Conditions: Fiji's mobile market is dominated by two major operators – Vodafone Fiji Limited (VFL) with approximately 85% market share (~850,000 subscribers) and Digicel Fiji with 15% market share. SMS remains a crucial communication channel, particularly for business notifications and authentication services. While OTT messaging apps like WhatsApp and Viber are gaining popularity, SMS maintains its position as a reliable channel for critical communications due to its universal reach and network independence.

SMS Features and Technical Capabilities in Fiji

Fiji supports standard SMS features with some limitations, primarily offering one-way messaging capabilities with support for concatenated messages and URL-based media sharing.

Two-Way SMS Support in Fiji

Two-way SMS is not supported in Fiji through standard API providers. If you need interactive messaging, consider alternative communication channels (WhatsApp, RCS) or work directly with local carriers for custom implementations.

Concatenated SMS Messages (Long SMS)

Support: Yes, concatenation is supported, though availability may vary by sender ID type.

Message length rules:

  • GSM-7 encoding: 153 characters per segment (max 3 segments, 459 total)
  • Unicode: 67 characters per segment (max 3 segments, 201 total)

Why these limits? Standard SMS messages use 160 characters (GSM-7) or 70 characters (Unicode). When messages exceed these limits, concatenation headers (User Data Header, UDH) consume 7 characters per segment (153 for GSM-7) or 3 characters (67 for Unicode), allowing the receiving device to reassemble the message in the correct order.

Billing: Each segment is billed as a separate SMS. A 300-character GSM-7 message counts as 2 SMS messages (153 + 147 characters).

Encoding considerations: Use GSM-7 for standard English messages and Unicode (UCS-2) for iTaukei or Hindi content.

MMS Support in Fiji

MMS messages are automatically converted to SMS with an embedded URL link. Shorten your URLs and optimize landing pages for mobile devices.

Fiji Phone Number Compatibility

Mobile Number Portability in Fiji

Number portability is not available in Fiji. This means phone numbers remain tied to their original carrier, simplifying message routing and delivery.

Can You Send SMS to Fiji Landline Numbers?

Sending SMS to landline numbers is not supported in Fiji. Messages to landline numbers will fail with error code 21614 (400), and you won't be charged.

SMS Compliance and Regulatory Requirements in Fiji

The Telecommunications Authority of Fiji (TAF) oversees SMS communications and establishes guidelines to protect consumers. All SMS marketing activities must comply with the Fiji Telecommunications Act and associated regulations.

Explicit Consent Requirements:

  • Obtain and document clear, explicit opt-in consent before sending any marketing messages
  • Maintain detailed consent records for a minimum of 7 years
  • Include clear terms and conditions during the opt-in process
  • Provide transparent information about message frequency and content type

Best Practices for Consent Collection:

  • Use double opt-in verification for marketing lists
  • Document consent source, timestamp, and IP address
  • Maintain an auditable trail of consent records
  • Regularly validate your consent database

Mandatory HELP/STOP Keywords

  • All marketing messages must include clear opt-out instructions
  • Support standard keywords: STOP, CANCEL, UNSUBSCRIBE, HELP
  • Process opt-out requests within 24 hours
  • Support both English and local language commands (iTaukei and Hindi)
  • Respond to HELP requests with service information and support contact details

Do Not Call / Do Not Disturb Registries

While Fiji does not maintain a centralized Do Not Call registry, businesses must:

  • Maintain their own suppression lists
  • Honor opt-out requests immediately
  • Keep records of opted-out numbers for at least 2 years
  • Implement proper filtering systems to prevent messaging to opted-out numbers

Fiji Time Zone and Sending Hours

Messaging Hours:

  • Restrict marketing messages to 8 AM – 6 PM FJT (UTC+12)
  • Avoid messaging during public holidays and weekends
  • Emergency notifications may be sent outside these hours
  • Implement 48-hour cooling-off periods between campaigns

Daylight Saving Time: Fiji does not currently observe Daylight Saving Time (DST). Fiji Time (FJT) remains at UTC+12 year-round. DST was last observed in January 2021 and was subsequently abolished. Use the fixed UTC+12 offset when scheduling messages.

SMS Sender ID Types for Fiji

Alphanumeric Sender IDs in Fiji

Operator network capability: Supported with dynamic usage

Registration requirements: No pre-registration required

Character limits: Maximum 11 characters; minimum varies by carrier (typically 3–6 characters)

Allowed characters: Letters (A-Z, a-z), numbers (0-9), and space character (ASCII 32). No special characters or symbols.

Sender ID preservation: Sender IDs are generally preserved, but avoid generic terms like "InfoSMS" or "Verify" to prevent delivery failures

Long Code Phone Numbers

Domestic vs. International: International long codes supported; domestic long codes not available

Sender ID preservation: Original sender ID preserved for international numbers

Provisioning time: Immediate for international numbers

Use cases: Transactional messages, alerts, and notifications

SMS Short Codes

Support: Not currently supported in Fiji

Provisioning time: N/A

Use cases: N/A

Prohibited Content and Industry Restrictions

Restricted Industries and Content:

  • Gambling and betting services
  • Adult content or services
  • Cryptocurrency promotions
  • Unauthorized financial services
  • Political messaging without proper authorization

SMS Content Filtering Rules

Carrier Filtering Rules:

  • Messages containing restricted keywords are blocked
  • URLs must be from approved domains
  • High-frequency messaging triggers automatic filtering
  • Spam-like content patterns face increased scrutiny

Best Practices to Avoid Filtering:

  • Avoid excessive punctuation and all-caps text
  • Use approved URL shorteners
  • Maintain consistent sending patterns
  • Include clear business identification
  • Avoid common spam trigger words

Best Practices for SMS Marketing in Fiji

Effective SMS Messaging Strategy

  • Keep messages under 160 characters when possible
  • Include a clear call-to-action
  • Use personalization tokens thoughtfully
  • Maintain a consistent sender ID across campaigns

Optimal SMS Frequency and Timing

  • Send no more than 4–5 messages per month per recipient
  • Respect local holidays and cultural events
  • Implement frequency capping
  • Allow minimum 24-hour gaps between marketing messages

SMS Localization for Fiji Markets

  • Support English, iTaukei, and Hindi languages
  • Use appropriate character encoding for local languages: GSM-7 for English, UCS-2 (Unicode) for iTaukei and Hindi
  • Consider cultural sensitivities in message content
  • Offer language preference selection during opt-in

Opt-Out Management

  • Process opt-outs in real-time
  • Send a confirmation message for opt-out requests
  • Maintain a centralized opt-out database
  • Regularly audit opt-out list compliance

Testing and Monitoring

  • Test messages across both major carriers
  • Monitor delivery rates by carrier
  • Track engagement metrics
  • Regularly test opt-out functionality
  • Monitor and analyze failure patterns

SMS API Integration Examples for Fiji

Twilio SMS API for Fiji

Twilio provides reliable SMS delivery to Fiji through their Sydney edge location. Integration requires your Account SID and Auth Token from the Twilio Console.

typescript
import { Twilio } from 'twilio';

// Initialize client with Sydney region for optimal routing to Fiji
const client = new Twilio(process.env.TWILIO_ACCOUNT_SID, process.env.TWILIO_AUTH_TOKEN, {
  region: 'sydney',
  edge: 'sydney'
});

// Send SMS to Fiji number
async function sendSMSToFiji() {
  try {
    const message = await client.messages.create({
      body: 'Hello from Fiji!', // Message content
      from: process.env.TWILIO_PHONE_NUMBER, // Your Twilio number
      to: '+679XXXXXXXX' // Fiji number in E.164 format
    });
    console.log(`Message sent successfully: ${message.sid}`);
  } catch (error) {
    console.error('Error sending message:', error);
  }
}

Sinch SMS API for Fiji

Sinch offers SMS capabilities to Fiji through their global messaging infrastructure. Authentication uses your Service Plan ID and API Token.

typescript
import axios from 'axios';

const SINCH_SERVICE_PLAN_ID = 'your_service_plan_id';
const SINCH_API_TOKEN = 'your_api_token';

async function sendSMSViaSinch() {
  const url = `https://sms.api.sinch.com/xms/v1/${SINCH_SERVICE_PLAN_ID}/batches`;

  try {
    const response = await axios.post(url, {
      from: 'YourSenderID',
      to: ['+679XXXXXXXX'],
      body: 'Hello from Fiji!'
    }, {
      headers: {
        'Authorization': `Bearer ${SINCH_API_TOKEN}`,
        'Content-Type': 'application/json'
      }
    });
    console.log('Message sent:', response.data);
  } catch (error) {
    console.error('Error:', error.response?.data || error.message);
  }
}

MessageBird SMS API for Fiji

MessageBird provides SMS access to Fiji through their REST API. Setup requires an API key from your MessageBird dashboard.

typescript
import messagebird from 'messagebird';

const messagebirdClient = messagebird('YOUR_API_KEY');

function sendSMSViaMessageBird() {
  const params = {
    originator: 'YourCompany',
    recipients: ['+679XXXXXXXX'],
    body: 'Hello from Fiji!',
    datacoding: 'auto' // Automatically handles character encoding
  };

  messagebirdClient.messages.create(params, (err, response) => {
    if (err) {
      console.error('Error:', err);
      return;
    }
    console.log('Message sent:', response);
  });
}

Plivo SMS API for Fiji

Plivo offers SMS connectivity to Fiji with straightforward REST API integration. Authentication requires Auth ID and Auth Token.

typescript
import plivo from 'plivo';

const client = new plivo.Client(
  process.env.PLIVO_AUTH_ID,
  process.env.PLIVO_AUTH_TOKEN
);

async function sendSMSViaPlivo() {
  try {
    const message = await client.messages.create({
      src: 'YourSenderID', // Your sender ID
      dst: '+679XXXXXXXX', // Destination Fiji number
      text: 'Hello from Fiji!',
      url_strip_query_params: false // Preserve URL parameters if included
    });
    console.log('Message sent:', message);
  } catch (error) {
    console.error('Error:', error);
  }
}

API Rate Limits and Throughput

  • Default rate limits vary by provider (typically 1–10 messages per second)
  • Implement exponential backoff for retry logic
  • Use batch APIs for bulk sending
  • Consider queue implementation for high-volume sending:
typescript
import Queue from 'bull';

const smsQueue = new Queue('sms-queue');

// Add messages to queue
smsQueue.add({
  to: '+679XXXXXXXX',
  message: 'Hello from Fiji!'
}, {
  attempts: 3,
  backoff: {
    type: 'exponential',
    delay: 2000
  }
});

Error Handling and Reporting

typescript
// Example error handling implementation
interface SMSError {
  code: string;
  message: string;
  timestamp: Date;
  recipient: string;
}

class SMSLogger {
  static logError(error: SMSError) {
    console.error(`SMS Error [${error.code}]: ${error.message}`);
    // Implement your error logging logic here
  }

  static async retryFailedMessages(errors: SMSError[]) {
    // Implement retry logic for failed messages
  }
}

Recap and Additional Resources

Key Takeaways:

  • Use Sydney region endpoints for optimal latency
  • Implement proper error handling and retry logic
  • Follow local time restrictions (8 AM – 6 PM FJT)
  • Maintain proper opt-out handling

Next Steps:

  1. Review the Telecommunications Authority of Fiji Guidelines
  2. Implement proper consent management using SMS compliance best practices
  3. Set up monitoring and reporting systems
  4. Explore international SMS guides for multi-country campaigns

Additional Resources:

Frequently Asked Questions

How to send SMS messages in Fiji?

Use a reputable SMS API provider like Twilio, Sinch, MessageBird, or Plivo, ensuring your integration is configured for the Sydney region for optimal delivery. Remember to format recipient numbers in E.164 format (+679XXXXXXXX) and adhere to Fiji's SMS guidelines.

What is the best time to send SMS in Fiji?

The optimal time for marketing SMS in Fiji is between 8 AM and 6 PM Fiji Time (UTC+12), avoiding weekends and public holidays. Emergency notifications are exempt from these restrictions.

Why does Fiji not support two-way SMS?

Standard API providers do not facilitate two-way SMS in Fiji. Businesses seeking interactive messaging should consider alternative channels or collaborate directly with local carriers like Vodafone Fiji or Digicel.

What are the character limits for SMS in Fiji?

Fiji supports concatenated SMS. GSM-7 encoding allows 153 characters per segment (up to 3 segments, 459 total), while Unicode allows 67 characters per segment (up to 3 segments, 201 total).

When should I use Unicode encoding for SMS in Fiji?

Use Unicode (UCS-2) encoding for messages containing iTaukei or Hindi characters. Use GSM-7 encoding for standard English messages to maximize character limits per segment.

Can I send SMS to landlines in Fiji?

No, SMS to landline numbers is not supported in Fiji. Attempts to do so will result in a failed delivery and an error response from the API, specifically a 400 error code 21614.

What are the SMS compliance regulations in Fiji?

The Telecommunications Authority of Fiji (TAF) regulates SMS communications. Key requirements include explicit opt-in consent for marketing messages, clear opt-out instructions (STOP, CANCEL, etc.), and adherence to messaging time restrictions.

How to handle SMS opt-outs in Fiji?

Process opt-out requests promptly (within 24 hours), send a confirmation message, maintain a centralized opt-out database, and ensure your systems filter opted-out numbers from future campaigns. Support both English and local language opt-out keywords.

What is the process for sending marketing SMS in Fiji?

Obtain explicit opt-in consent, adhere to message content and timing restrictions, and provide clear opt-out instructions. Respect local languages and cultural sensitivities. Monitor delivery rates and engagement for optimal campaign performance.

What SMS sender IDs are supported in Fiji?

Alphanumeric sender IDs are supported dynamically without pre-registration, while international long codes are available for transactional messages. Short codes are not currently supported in Fiji.

What content is restricted in SMS messages in Fiji?

Gambling, adult content, cryptocurrency promotions, unauthorized financial services, and political messaging without proper authorization are restricted. Content filtering is in place to block messages with prohibited keywords or URLs.

How to avoid SMS filtering in Fiji?

Avoid excessive punctuation, all-caps, and common spam trigger words. Use approved URL shorteners, maintain consistent sending patterns, include clear business identification in your messages.

What are the best practices for SMS messaging strategy in Fiji?

Keep messages concise (under 160 characters), include a clear call-to-action, personalize thoughtfully, maintain consistent sender ID, and localize content by supporting English, iTaukei, and Hindi languages.

What are the recommended API rate limits for SMS in Fiji?

Default rate limits vary by provider. Implement exponential backoff for retry logic and use batch APIs for bulk sending. Consider using a queue implementation for high-volume messaging to manage throughput.

What are some important SMS API integration considerations for Fiji?

Utilize the Sydney edge location for optimal latency, implement thorough error handling and retry mechanisms, and ensure compliance with local time restrictions. Consider using libraries like 'bull' for queue management and maintain proper logging for error reporting.