Togo SMS Best Practices, Compliance, and Features

SMS Market Overview in Togo

Market Conditions: Togo has a growing mobile telecommunications market regulated by the Autorité de Régulation des Communications Électroniques et des Postes (ARCEP) ¹. The country operates two major mobile network operators: Togocel (state-owned incumbent) and Moov Africa Togo (formerly Moov Togo, part of Maroc Telecom Group). As of 2024, Togo's mobile market continues to expand with increasing smartphone adoption and data usage ².

SMS remains a critical communication channel for business notifications, mobile banking, and alerts due to its universal reach across all device types. While Over-The-Top (OTT) messaging applications like WhatsApp are gaining traction in urban areas, SMS maintains strong penetration in rural regions and among feature phone users. The country uses GSM networks operating on 900 MHz and 1800 MHz bands, with expanding 3G and 4G coverage in major cities including Lomé, Sokodé, and Kara ¹.

Mobile Number Format: Togolese mobile numbers are 8 digits long (excluding the country code +228). Mobile numbers typically begin with prefixes 90 – 99 for various operators ³.

SMS Features and Capabilities for Togo

Togo supports basic SMS functionality including concatenated messages and alphanumeric sender IDs. Two-way SMS is not available.

Two-Way SMS Support in Togo

Two-way SMS is not supported in Togo. Send messages one-way from your business to consumers, making it suitable for notifications and alerts but not for interactive messaging campaigns.

Concatenated Messages (Segmented SMS)

Support: Yes, concatenation is supported for most sender ID types. Message length rules: Standard SMS length of 160 characters for GSM-7 encoding, or 70 characters for Unicode (UCS-2) encoding before splitting occurs. Encoding considerations: Both GSM-7 and UCS-2 encodings are supported. Messages automatically split and rejoin based on the character encoding you use.

MMS Support

MMS messages are not directly supported in Togo. When you attempt to send MMS, the message converts automatically to SMS with an embedded URL link where recipients can view the multimedia content. This ensures message delivery while providing access to rich media content.

Recipient Phone Number Compatibility

Number Portability

Number portability is not available in Togo. Mobile numbers remain tied to their original carrier, which helps ensure consistent message routing and delivery.

Sending SMS to Landlines

You cannot send SMS to landline numbers in Togo. Attempts to send messages to landline numbers will result in failed delivery and an error response (400 error code 21614). These messages will not appear in logs, and your account will not be charged for failed attempts.

SMS Compliance and Regulatory Guidelines for Togo

Togo's telecommunications sector is regulated by ARCEP (Autorité de Régulation des Communications Électroniques et des Postes), which oversees mobile network operators and ensures compliance with telecommunications standards ¹. While Togo does not have comprehensive SMS-specific marketing regulations comparable to GDPR or TCPA, businesses must adhere to general telecommunications guidelines and contractual obligations with mobile operators ⁴.

Regulatory Framework: As of 2025, Togo's telecommunications law focuses primarily on network infrastructure, spectrum allocation, and operator licensing rather than detailed content or marketing message regulations. However, businesses are strongly advised to follow international best practices for SMS communications, particularly regarding consent, opt-out mechanisms, and transparent sender identification ⁴.

Data Protection Considerations: While Togo is developing its data protection framework, businesses handling personal data (including mobile phone numbers) should implement reasonable security measures and obtain appropriate consent before sending commercial messages. Align practices with international standards such as those recommended by the International Telecommunication Union (ITU) ².

Consent and Opt-In

Explicit Consent Requirements:

• Obtain clear, documented opt-in consent before sending marketing messages
• Maintain records of how and when you obtained consent
• Include your business name and purpose in consent requests
• Provide clear terms and conditions regarding message frequency and content

HELP/STOP and Other Commands

• Support standard STOP commands for opt-outs
• Include HELP keyword support for user assistance
• Consider both French (primary) and English language commands:
  • STOP/ARRÊTER
  • AIDE/HELP
• Acknowledge opt-out requests within 24 hours

Do Not Call / Do Not Disturb Registries

While Togo doesn't maintain an official Do Not Call registry, follow these practices:

• Maintain your own suppression lists
• Honor opt-out requests immediately
• Document all opt-out requests and actions you take
• Regularly clean contact lists to remove unsubscribed numbers

Time Zone Sensitivity

Togo operates in the Greenwich Mean Time (GMT/UTC+0) zone year-round, with no daylight saving time adjustments ⁵. This places Togo in the same time zone as countries like Ghana, Senegal, and Mali.

Sending Time Best Practices:

• Send commercial messages between 8:00 AM and 8:00 PM GMT (local time)
• Avoid messages during major religious holidays including Eid al-Fitr, Eid al-Adha, and Christian holidays (Christmas, Easter, Good Friday)
• Respect Togo's Independence Day (April 27) and other national celebrations
• Limit urgent or transactional messages outside business hours to genuine emergencies (account security alerts, delivery notifications)
• Consider that Friday prayers (12:00 PM - 2:00 PM) may affect engagement in predominantly Muslim areas

SMS Sender ID Types and Phone Number Options in Togo

Alphanumeric Sender ID for Togo SMS

Operator network capability: Supported Registration requirements: Pre-registration not required, dynamic usage supported Sender ID preservation: Yes, sender IDs are preserved and displayed as sent

Long Codes

Domestic vs. International: Both domestic and international long codes supported Sender ID preservation: Yes, original sender ID is preserved Provisioning time: Typically 1-2 business days Use cases: Ideal for transactional messages, alerts, and notifications

Short Codes

Support: Not currently supported in Togo Provisioning time: N/A Use cases: N/A

SMS Content Restrictions and Industry Regulations in Togo

Restricted Industries and Content:

• Gambling and betting services
• Adult content or services
• Unauthorized financial services
• Political campaign messages without proper authorization
• Cryptocurrency and unauthorized investment schemes

Content Filtering

Carrier Filtering Rules:

• Messages containing certain keywords may be blocked
• URLs may be subject to additional scrutiny
• High-volume sending patterns may trigger spam filters

Best Practices to Avoid Filtering:

• Avoid excessive punctuation and all-caps text
• Use clear, professional language
• Limit URL usage in messages
• Maintain consistent sending patterns
• Keep message content relevant and expected

SMS Best Practices for Togo: Delivery and Engagement

Messaging Strategy

• Keep messages under 160 characters when possible
• Include clear calls-to-action
• Personalize messages with recipient names when appropriate
• Maintain consistent branding across messages

Sending Frequency and Timing

• Limit marketing messages to 2 – 4 per month per recipient
• Space out messages to avoid overwhelming recipients
• Consider Togolese holidays and cultural events
• Avoid sending during major religious observances

Localization

• Primary language: French
• Consider including both French and English for international businesses
• Use local date and time formats
• Respect cultural sensitivities in message content

Opt-Out Management

• Process opt-outs within 24 hours
• Maintain accurate opt-out records
• Include clear opt-out instructions in messages
• Conduct regular audits of opt-out list compliance

Testing and Monitoring

• Test messages across both major carriers: Togocel (state-owned) and Moov Africa Togo (private operator)
• Monitor delivery rates by carrier to identify network-specific issues
• Track engagement metrics including click-through rates for messages with URLs
• Regular review of failed delivery reasons and error codes
• Test message rendering on popular device types (Android feature phones and smartphones predominate in Togo)
• Verify sender ID display across different handset models and carriers
• Monitor concatenated message reassembly on various devices

Carrier-Specific Testing Recommendations:

• Togocel: Test with various mobile prefixes assigned to the state operator
• Moov Africa Togo: Validate delivery across Moov's network infrastructure
• Cross-carrier testing: Ensure consistent delivery performance across both networks

SMS API Integration for Togo: Provider Comparison

Twilio SMS API for Togo

Twilio provides a robust SMS API for sending messages to Togo. Integration requires your Account SID and Auth Token from the Twilio Console. Learn more about 10DLC registration for US-based sending.

import { Twilio } from 'twilio';

// Initialize Twilio client with your credentials
const client = new Twilio(
  process.env.TWILIO_ACCOUNT_SID,
  process.env.TWILIO_AUTH_TOKEN
);

// Function to send SMS to Togo
async function sendSMSToTogo(
  to: string,
  message: string,
  senderId: string
): Promise<void&gt; {
  try {
    // Format phone number for Togo (add +228 if not present)
    const formattedNumber = to.startsWith('+228') ? to : `+228${to}`;

    // Send message
    const response = await client.messages.create({
      body: message,
      from: senderId, // Alphanumeric sender ID or Twilio number
      to: formattedNumber,
    });

    console.log(`Message sent successfully! SID: ${response.sid}`);
  } catch (error) {
    console.error('Error sending message:', error);
    throw error;
  }
}

Sinch SMS API for Togo

Sinch offers SMS capabilities for Togo through their REST API. Authentication uses Bearer token.

import axios from 'axios';

interface SinchSMSConfig {
  serviceId: string;
  apiToken: string;
  senderId: string;
}

class SinchSMSService {
  private readonly baseUrl: string;
  private readonly config: SinchSMSConfig;

  constructor(config: SinchSMSConfig) {
    this.config = config;
    this.baseUrl = 'https://sms.api.sinch.com/xms/v1';
  }

  async sendSMS(to: string, message: string): Promise<void&gt; {
    try {
      const response = await axios.post(
        `${this.baseUrl}/${this.config.serviceId}/batches`,
        {
          from: this.config.senderId,
          to: [to],
          body: message
        },
        {
          headers: {
            'Authorization': `Bearer ${this.config.apiToken}`,
            'Content-Type': 'application/json'
          }
        }
      );

      console.log('Message sent:', response.data.id);
    } catch (error) {
      console.error('Sinch SMS error:', error);
      throw error;
    }
  }
}

MessageBird SMS API for Togo

MessageBird provides SMS API access for Togo with straightforward integration.

import messagebird from 'messagebird';

class MessageBirdService {
  private client: any;

  constructor(apiKey: string) {
    this.client = messagebird(apiKey);
  }

  sendSMS(to: string, message: string, senderId: string): Promise<void&gt; {
    return new Promise((resolve, reject) =&gt; {
      // Ensure proper formatting for Togo numbers
      const formattedNumber = to.startsWith('+228') ? to : `+228${to}`;

      const params = {
        originator: senderId,
        recipients: [formattedNumber],
        body: message
      };

      this.client.messages.create(params, (err: any, response: any) =&gt; {
        if (err) {
          console.error('MessageBird error:', err);
          reject(err);
        } else {
          console.log('Message sent:', response.id);
          resolve();
        }
      });
    });
  }
}

Plivo SMS API for Togo

Plivo's SMS API supports messaging to Togo with reliable delivery.

import plivo from 'plivo';

class PlivoSMSService {
  private client: any;

  constructor(authId: string, authToken: string) {
    this.client = new plivo.Client(authId, authToken);
  }

  async sendSMS(to: string, message: string, senderId: string): Promise<void&gt; {
    try {
      const response = await this.client.messages.create({
        src: senderId,
        dst: to.startsWith('+228') ? to : `+228${to}`,
        text: message,
      });

      console.log('Message sent:', response.messageUuid[0]);
    } catch (error) {
      console.error('Plivo error:', error);
      throw 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 queuing systems (Redis, RabbitMQ) for high-volume sending
• Batch messages when possible to optimize throughput

Error Handling and Reporting

• Implement comprehensive error logging
• Monitor delivery receipts (DLRs)
• Track common error codes:
  • Invalid number format
  • Network errors
  • Rate limit exceeded
• Store message metadata for troubleshooting

Recap and Additional Resources

Key Takeaways

1. Compliance Priorities

   • Obtain explicit consent
   • Honor opt-out requests
   • Respect sending hours (8 AM – 8 PM)
   • Maintain proper records

2. Technical Considerations

   • Format numbers with +228 prefix
   • Support both French and English
   • Monitor delivery rates
   • Implement proper error handling

3. Best Practices

   • Keep messages concise
   • Use appropriate sender IDs
   • Regular testing across carriers
   • Maintain clean contact lists

Frequently Asked Questions About Sending SMS to Togo

What mobile operators provide SMS services in Togo?

Togo has two major mobile network operators: Togocel (the state-owned incumbent operator) and Moov Africa Togo (formerly Moov Togo, operated by Maroc Telecom Group). Both operators support SMS delivery across their networks using GSM 900 MHz and 1800 MHz bands, with expanding 3G and 4G coverage in urban areas. Test your SMS campaigns across both carriers to ensure consistent delivery performance, as network coverage and message routing can vary between operators.

Is two-way SMS supported in Togo?

No, two-way SMS is not supported in Togo. You can only send one-way messages from your business to consumers, making SMS suitable for notifications, alerts, transactional messages, and marketing campaigns that don't require recipient responses. If you need interactive communication, consider alternative channels like WhatsApp Business API for two-way conversations, or design your SMS campaigns to direct users to web forms, phone numbers, or mobile apps for engagement.

What are the SMS character limits and encoding requirements for Togo?

Togo supports standard SMS character limits: 160 characters per message segment for GSM-7 encoding (standard Latin characters, numbers, and common symbols) or 70 characters per segment for UCS-2 encoding (Unicode characters including emojis, accented French characters beyond GSM-7, and non-Latin scripts). Messages exceeding these limits automatically split into concatenated segments, with each segment billed separately. To optimize costs and ensure delivery, keep messages under 160 characters using GSM-7 encoding whenever possible.

Do I need to register sender IDs for SMS in Togo?

No, pre-registration is not required for alphanumeric sender IDs in Togo. You can use dynamic alphanumeric sender IDs (up to 11 characters, letters and numbers only, no spaces) without prior approval from carriers or regulatory authorities. Sender IDs are preserved and displayed as sent to recipients. However, using a consistent, recognizable sender ID helps build trust with recipients and improves message engagement. Avoid frequently changing sender IDs, as this may trigger spam filters.

What time zone does Togo use and when should I send SMS messages?

Togo operates in Greenwich Mean Time (GMT/UTC+0) year-round with no daylight saving time adjustments. Send commercial SMS messages between 8:00 AM and 8:00 PM GMT (local time) to respect recipients' personal time. Avoid sending during major religious holidays (Eid al-Fitr, Eid al-Adha, Christmas, Easter, Good Friday) and national celebrations like Independence Day (April 27). Consider that Friday prayers (12:00 PM – 2:00 PM) may affect engagement in predominantly Muslim areas. Limit urgent or transactional messages outside business hours to genuine emergencies like account security alerts or critical delivery notifications.

Can I send SMS to landline numbers in Togo?

No, you cannot send SMS to landline numbers in Togo. Attempts to send messages to landline numbers result in failed delivery with error code 21614 (HTTP 400 error). These failed messages won't appear in your delivery logs, and your account won't be charged for the attempts. Before sending campaigns, validate that all recipient numbers are mobile numbers (8 digits with prefixes 90 – 99, plus country code +228) to avoid delivery failures and ensure accurate campaign metrics.

What compliance regulations govern SMS marketing in Togo?

Togo's telecommunications sector is regulated by ARCEP (Autorité de Régulation des Communications Électroniques et des Postes), which oversees mobile operators and network infrastructure. While Togo doesn't have comprehensive SMS-specific marketing regulations comparable to GDPR or TCPA, follow international best practices: obtain explicit opt-in consent before sending marketing messages, honor opt-out requests within 24 hours, provide clear unsubscribe instructions (STOP/ARRÊTER keywords), identify your business as the sender, and maintain records of consent and opt-outs for compliance audits.

Is MMS supported for sending multimedia content in Togo?

MMS (Multimedia Messaging Service) is not directly supported in Togo. When you attempt to send MMS, the message automatically converts to SMS with an embedded URL link where recipients can view multimedia content (images, videos, audio files). This conversion ensures message delivery while providing access to rich media through a web-based viewer. For campaigns requiring visual content, consider this URL-based approach or use alternative channels like WhatsApp Business API, which natively supports image, video, and document sharing with higher engagement rates.

How much does it cost to send SMS in Togo?

SMS pricing for Togo varies by provider and volume. International SMS API providers like Twilio, Plivo, Sinch, and Infobip offer pay-as-you-go pricing typically ranging from $0.04 to $0.12 per message segment, with volume discounts for high-volume senders. Costs depend on factors including message encoding (GSM-7 vs. UCS-2), message length (single vs. concatenated segments), sender ID type (alphanumeric vs. long code), and delivery success rates. Contact providers directly for current pricing and negotiate volume discounts if sending more than 10,000 messages per month.

Can mobile subscribers port their numbers between carriers in Togo?

No, number portability is not available in Togo. Mobile numbers remain permanently tied to their original carrier (Togocel or Moov Africa Togo), meaning subscribers cannot switch operators while keeping the same phone number. This simplifies message routing since number prefixes reliably indicate the destination carrier, but requires you to update contact databases when subscribers change numbers due to carrier switches. The lack of portability reduces network complexity but may impact subscriber mobility between operators.

Summary

Successfully implementing SMS messaging in Togo requires understanding the market's technical capabilities, regulatory environment, and cultural considerations. Togo's mobile telecommunications market, regulated by ARCEP, operates with two major carriers (Togocel and Moov Africa Togo) serving the population through GSM networks with expanding 3G and 4G coverage.

Key technical limitations shape SMS strategies: two-way messaging is not supported, limiting use cases to one-way notifications and alerts; number portability is unavailable, keeping subscribers tied to their original carriers; and MMS converts automatically to SMS with embedded links for multimedia content. These constraints favor transactional messaging, marketing campaigns, mobile banking notifications, and alert systems over interactive conversational applications.

From a compliance perspective, while Togo lacks comprehensive SMS-specific marketing regulations, businesses should follow international best practices including obtaining explicit opt-in consent, honoring opt-out requests within 24 hours, supporting STOP/ARRÊTER and AIDE/HELP commands in French and English, respecting sending hours (8:00 AM – 8:00 PM GMT), and avoiding messages during religious holidays and national celebrations.

Technical implementation requires formatting mobile numbers correctly (+228 followed by 8 digits with prefixes 90 – 99), understanding GSM-7 (160 characters) versus UCS-2 (70 characters) encoding limits, leveraging alphanumeric sender IDs without pre-registration requirements, and testing delivery across both Togocel and Moov Africa Togo networks to ensure consistent performance.

Extension Ideas for Advanced Implementations:

1. Multi-Channel Communication Strategy: Integrate SMS with WhatsApp Business API for two-way conversations while using SMS for transactional alerts and notifications. Implement intelligent channel routing based on message type – use SMS for OTP codes, payment confirmations, and urgent alerts; use WhatsApp for customer service, order updates with images, and marketing campaigns requiring rich media or recipient responses.

2. Carrier-Specific Optimization: Build separate message queues and routing logic for Togocel and Moov Africa Togo to optimize delivery times and success rates. Monitor carrier-specific performance metrics (delivery rates, latency, error patterns) and implement automatic failover to alternative routing when one carrier experiences issues. Maintain carrier-specific contact lists for targeted testing and troubleshooting.

3. French Language Localization Engine: Develop SMS templates optimized for French language character limits and cultural nuances. Create a character encoding validator that detects UCS-2 triggers (accented characters beyond GSM-7 like ê, à, ç) and suggests GSM-7 alternatives to avoid doubling message costs. Implement date/time formatting that matches Togolese conventions (DD/MM/YYYY format, 24-hour time).

4. Compliance Automation System: Build automated consent management tracking when and how opt-ins were obtained, storing IP addresses and timestamps for audit trails. Implement automatic opt-out processing that removes numbers from all campaign lists within 24 hours, supports STOP/ARRÊTER/AIDE/HELP keyword detection in both French and English, and generates compliance reports showing consent rates, opt-out volumes, and message frequency per recipient.

5. Time Zone Aware Scheduling: Create intelligent message scheduling that respects GMT/UTC+0 sending windows (8:00 AM – 8:00 PM local time), automatically delays messages sent outside appropriate hours, blocks sending during religious holidays (Eid al-Fitr, Eid al-Adha, Christmas, Easter) and Independence Day (April 27), and reduces frequency during Friday prayer times (12:00 PM – 2:00 PM) in predominantly Muslim areas.

6. Delivery Analytics Dashboard: Implement comprehensive tracking of delivery rates by carrier (Togocel vs. Moov Africa Togo), device type (feature phones vs. smartphones), message encoding (GSM-7 vs. UCS-2), sender ID type (alphanumeric vs. long code), time of day, and day of week. Use this data to optimize sending strategies, identify problematic number ranges, and predict delivery success rates before launching campaigns.

7. Cost Optimization Engine: Build a system that calculates real-time message costs based on character count, encoding type, and concatenation requirements. Implement pre-send cost estimates for campaigns, suggest message rewording to reduce segments (e.g., shortening 161-character messages to fit 160-character limit), track cost-per-conversion metrics, and set budget alerts when campaigns approach spending thresholds.

8. Regional Expansion Framework: Prepare for growth across West Africa by researching telecommunications regulations in neighboring WAEMU/UEMOA countries (Benin, Burkina Faso, Côte d'Ivoire, Mali, Niger, Senegal). Develop reusable compliance frameworks, create multi-country routing infrastructure, implement currency conversion for cross-border pricing, and build country-specific sender ID management while maintaining centralized campaign orchestration.

Start testing with both Togocel and Moov Africa Togo carriers, validate your compliance processes with sample campaigns of 100 – 500 messages, monitor delivery metrics closely during the first 30 days, and scale gradually while maintaining opt-out rates below 2% and delivery success rates above 95%.

Next Steps

1. Review ARCEP regulations for telecommunications
2. Consult legal counsel for compliance review
3. Set up test accounts with preferred SMS providers
4. Implement proper monitoring and logging

Additional Information

• ARCEP Togo: Official regulatory authority website - https://arcep.tg/
• ITU Telecommunications Statistics: Global ICT data and standards - https://www.itu.int/en/ITU-D/Statistics/
• GSMA Mobile Economy: Regional mobile market reports - https://www.gsma.com/
• Twilio Togo Guidelines: Provider-specific compliance information - https://www.twilio.com/en-us/guidelines/tg

Important Considerations for Togo:

• Number portability is not available, meaning subscribers cannot change carriers while keeping their mobile numbers. This simplifies routing but requires database updates when users switch carriers.
• Two-way SMS is not supported, limiting interactive use cases such as surveys, chatbots, or customer service replies.
• Test thoroughly with both Togocel and Moov Africa Togo to ensure consistent delivery across the market.
• Maintain compliance with ARCEP guidelines even as regulations evolve.

Regional Context: Togo is part of the West African Economic and Monetary Union (WAEMU/UEMOA), sharing economic ties with neighboring countries. Consider similar regulatory approaches in Benin, Burkina Faso, and other WAEMU member states when planning regional campaigns.