Explore SMS best practices for French Guiana (GF), an overseas region of France. Understand compliance with ARCEP/CNIL, consent rules, & time zone restrictions (GMT-3). Learn about alphanumeric sender IDs, supported encodings (GSM-7/UCS-2), and error code 21614 for landline attempts.
Market Conditions: French Guiana, as an overseas department of France, follows French telecommunications standards and regulations. The mobile market is dominated by major French operators including Orange, SFR, and Digicel. While OTT messaging apps are popular, SMS remains a crucial communication channel, particularly for business and authentication purposes. The market shows a mix of Android and iOS usage, with Android having a slight edge in market share.
Key SMS Features and Capabilities in French Guiana
French Guiana supports standard SMS messaging capabilities with some limitations on advanced features like two-way messaging and concatenation.
Two-way SMS Support
Two-way SMS is not supported in French Guiana through standard A2P messaging channels.
Messages can only be sent one-way from businesses to consumers.
Concatenated Messages (Segmented SMS)
Support: Concatenated messages are not supported in French Guiana. Message length rules: Messages must fit within standard SMS character limits. Encoding considerations: Both GSM-7 and UCS-2 encoding are supported, with GSM-7 allowing up to 160 characters and UCS-2 allowing up to 70 characters per message.
MMS Support
MMS messages are automatically converted to SMS with an embedded URL link to view the multimedia content. Best Practice: When sending media content, ensure the URL is shortened and clearly labeled for recipient trust.
Recipient Phone Number Compatibility
Number Portability
Number portability is not available in French Guiana.
This means phone numbers remain tied to their original carrier, simplifying message routing and delivery.
Sending SMS to Landlines
Sending SMS to landline numbers is not possible in French Guiana.
Attempts to send SMS to landline numbers will result in a 400 response with error code 21614, and no message delivery will occur or charges applied.
Compliance and Regulatory Guidelines for SMS in French Guiana (France)
As an overseas department of France, French Guiana follows French telecommunications regulations and GDPR requirements. The primary regulatory bodies are ARCEP (Autorit?? de R??gulation des Communications ??lectroniques et des Postes) and CNIL (Commission Nationale de l'Informatique et des Libert??s).
Consent and Opt-In
Explicit Consent Requirements:
Written consent must be obtained before sending marketing messages
Consent must be freely given, specific, informed, and unambiguous
Documentation of consent must be maintained and readily available
Separate consent required for different types of communications
Best Practices for Consent Collection:
Use clear opt-in checkboxes (no pre-checked boxes)
Maintain detailed records of when and how consent was obtained
Include clear terms and conditions during opt-in
Provide immediate confirmation of subscription
HELP/STOP and Other Commands
All marketing messages must include "STOP" functionality
Standard format: "STOP au 36179" at the end of messages
Both French and English commands must be supported
Common keywords: STOP, ARRETER, AIDE, HELP
Response to STOP commands must be immediate and in French
Do Not Call / Do Not Disturb Registries
France maintains the Bloctel list, which applies to French Guiana
Businesses must screen numbers against Bloctel before sending marketing messages
Maintain internal suppression lists for opted-out numbers
Process opt-outs within 24 hours
Regular database cleaning recommended to remove invalid numbers
Time Zone Sensitivity
Marketing messages restricted to Monday-Saturday, 8 AM to 10 PM local time
Messages outside these hours will be queued for next available window
Sunday and public holiday messages are blocked
Transactional messages can be sent 24/7
Time zone: French Guiana (GMT-3)
Phone Numbers Options and SMS Sender Types for in French Guiana (France)
Alphanumeric Sender ID
Operator network capability: Supported Registration requirements: No pre-registration required, dynamic usage supported Sender ID preservation: Yes, sender IDs are preserved as displayed
Long Codes
Domestic vs. International:
Domestic long codes not supported
International long codes supported but sender ID may be overwritten
Sender ID preservation: No, international numbers are typically overwritten Provisioning time: Immediate for international numbers Use cases: Transactional messages, alerts, notifications
Short Codes
Support: Not supported in French Guiana Provisioning time: N/A Use cases: N/A
Restricted SMS Content, Industries, and Use Cases
Restricted Industries and Content:
Gambling and betting services
Adult content and services
Unauthorized pharmaceutical products
Political messaging without proper disclaimers
Financial services without proper licensing
Cryptocurrency promotions
Content Filtering
Carrier Filtering Rules:
Messages containing certain keywords may be blocked
URLs must be from approved domains
Message content must be in French or English
Best Practices to Avoid Filtering:
Avoid excessive punctuation and special characters
Use approved URL shorteners
Keep content professional and clear
Avoid spam trigger words
Include clear sender identification
Best Practices for Sending SMS in French Guiana (France)
Messaging Strategy
Keep messages under 160 characters when possible
Include clear call-to-action
Use personalization tokens appropriately
Maintain consistent brand voice
Include sender identification in message
Sending Frequency and Timing
Limit to 2-3 marketing messages per week
Respect quiet hours and holidays
Space out messages to avoid overwhelming recipients
Monitor engagement rates to optimize timing
Localization
Primary language should be French
Consider including both French and English for important messages
Use proper French formatting for dates and numbers
Consider local cultural context and holidays
Opt-Out Management
Process opt-outs within 24 hours
Maintain centralized opt-out database
Confirm opt-out with one final message
Regular audit of opt-out lists
Train staff on opt-out procedures
Testing and Monitoring
Test messages across all major carriers
Monitor delivery rates by carrier
Track engagement metrics
Regular testing of opt-out functionality
Monitor for carrier filtering changes
SMS API integrations for French Guiana (France)
Twilio
Twilio provides a robust SMS API for sending messages to French Guiana. Integration requires your Account SID and Auth Token from the Twilio Console.
TypeScript
import { Twilio } from'twilio';
// Initialize the client with your credentialsconst client = newTwilio(
process.env.TWILIO_ACCOUNT_SID, // Your Account SID
process.env.TWILIO_AUTH_TOKEN// Your Auth Token
);
asyncfunctionsendSMS() {
try {
// Send message with proper French Guiana formattingconst message = await client.messages.create({
body: 'Votre code de confirmation est: 123456',
from: 'YourBrand', // Alphanumeric sender IDto: '+594XXXXXXXXX'// French Guiana number format
});
console.log(`Message sent successfully: ${message.sid}`);
} catch (error) {
console.error('Error sending message:', error);
}
}
Sinch
Sinch offers SMS capabilities with support for French Guiana through their unified SDK.
Use an SMS API provider like Twilio, Sinch, MessageBird, or Plivo. Ensure your messages comply with French Guiana's regulations, including obtaining consent and respecting time zones. Use the +594 country code for recipient numbers.
SMS messages in French Guiana are limited to 160 characters when using GSM-7 encoding and 70 characters when using UCS-2 encoding. Concatenated messages are not supported, so ensure your message fits within these limits.
French Guiana only supports one-way A2P SMS messaging, meaning businesses can send messages to consumers, but not receive replies via standard SMS channels. This is due to the telecommunications infrastructure and regulations in place.
Marketing SMS messages are allowed Monday-Saturday, 8 AM to 10 PM local time (GMT-3). Messages sent outside these hours will be queued. Sunday and public holiday messages are blocked. Transactional messages are permitted 24/7.
No, short codes are not supported in French Guiana. You can use alphanumeric sender IDs or international long codes, but the sender ID might be overwritten with the latter.
All marketing messages must include "STOP" instructions, typically "STOP au 36179". Opt-outs must be processed within 24 hours and honored immediately. Maintain a database of opted-out numbers.
The Mobile Country Code (MCC) for French Guiana is 742. This code is used for routing international SMS messages and is essential for accurate delivery.
French Guiana follows French and EU GDPR rules. Obtain explicit, documented consent for marketing messages, provide clear opt-out instructions, and ensure data security.
Restricted content includes gambling, adult material, unauthorized pharmaceuticals, political messaging without disclaimers, and cryptocurrency promotions. Avoid these topics to prevent message blocking.
MMS messages are automatically converted to SMS with a URL link to the media content. Shorten and clearly label the URL to build recipient trust and encourage clicks.
ARCEP (Autorité de Régulation des Communications Électroniques et des Postes) is the French telecom regulator, whose rules apply to French Guiana. They oversee compliance with telecommunications laws and regulations.
Typical rate limits are one message per second per destination. Implement queuing systems and batch APIs for large campaigns. Schedule messages to avoid exceeding limits.
Use the international format with the +594 country code followed by the 9-digit local number. For example, +594XXXXXXXXX. Number portability is not available in French Guiana.
The primary language is French. Using French in messages improves comprehension and engagement. Consider including English for key information, especially for tourists or international businesses.
Keep messages concise (under 160 characters), personalized, and include a clear call to action. Respect quiet hours and holidays, and monitor engagement to optimize your campaigns.
French Guiana (France) SMS Market Overview
Market Conditions: French Guiana, as an overseas department of France, follows French telecommunications standards and regulations. The mobile market is dominated by major French operators including Orange, SFR, and Digicel. While OTT messaging apps are popular, SMS remains a crucial communication channel, particularly for business and authentication purposes. The market shows a mix of Android and iOS usage, with Android having a slight edge in market share.
Key SMS Features and Capabilities in French Guiana
French Guiana supports standard SMS messaging capabilities with some limitations on advanced features like two-way messaging and concatenation.
Two-way SMS Support
Two-way SMS is not supported in French Guiana through standard A2P messaging channels.
Messages can only be sent one-way from businesses to consumers.
Concatenated Messages (Segmented SMS)
Support: Concatenated messages are not supported in French Guiana.
Message length rules: Messages must fit within standard SMS character limits.
Encoding considerations: Both GSM-7 and UCS-2 encoding are supported, with GSM-7 allowing up to 160 characters and UCS-2 allowing up to 70 characters per message.
MMS Support
MMS messages are automatically converted to SMS with an embedded URL link to view the multimedia content.
Best Practice: When sending media content, ensure the URL is shortened and clearly labeled for recipient trust.
Recipient Phone Number Compatibility
Number Portability
Number portability is not available in French Guiana.
This means phone numbers remain tied to their original carrier, simplifying message routing and delivery.
Sending SMS to Landlines
Sending SMS to landline numbers is not possible in French Guiana.
Attempts to send SMS to landline numbers will result in a 400 response with error code 21614, and no message delivery will occur or charges applied.
Compliance and Regulatory Guidelines for SMS in French Guiana (France)
As an overseas department of France, French Guiana follows French telecommunications regulations and GDPR requirements. The primary regulatory bodies are ARCEP (Autorit?? de R??gulation des Communications ??lectroniques et des Postes) and CNIL (Commission Nationale de l'Informatique et des Libert??s).
Consent and Opt-In
Explicit Consent Requirements:
Best Practices for Consent Collection:
HELP/STOP and Other Commands
Do Not Call / Do Not Disturb Registries
Time Zone Sensitivity
Phone Numbers Options and SMS Sender Types for in French Guiana (France)
Alphanumeric Sender ID
Operator network capability: Supported
Registration requirements: No pre-registration required, dynamic usage supported
Sender ID preservation: Yes, sender IDs are preserved as displayed
Long Codes
Domestic vs. International:
Sender ID preservation: No, international numbers are typically overwritten
Provisioning time: Immediate for international numbers
Use cases: Transactional messages, alerts, notifications
Short Codes
Support: Not supported in French Guiana
Provisioning time: N/A
Use cases: N/A
Restricted SMS Content, Industries, and Use Cases
Restricted Industries and Content:
Content Filtering
Carrier Filtering Rules:
Best Practices to Avoid Filtering:
Best Practices for Sending SMS in French Guiana (France)
Messaging Strategy
Sending Frequency and Timing
Localization
Opt-Out Management
Testing and Monitoring
SMS API integrations for French Guiana (France)
Twilio
Twilio provides a robust SMS API for sending messages to French Guiana. Integration requires your Account SID and Auth Token from the Twilio Console.
import { Twilio } from 'twilio'; // Initialize the client with your credentials const client = new Twilio( process.env.TWILIO_ACCOUNT_SID, // Your Account SID process.env.TWILIO_AUTH_TOKEN // Your Auth Token ); async function sendSMS() { try { // Send message with proper French Guiana formatting const message = await client.messages.create({ body: 'Votre code de confirmation est: 123456', from: 'YourBrand', // Alphanumeric sender ID to: '+594XXXXXXXXX' // French Guiana number format }); console.log(`Message sent successfully: ${message.sid}`); } catch (error) { console.error('Error sending message:', error); } }Sinch
Sinch offers SMS capabilities with support for French Guiana through their unified SDK.
import { SinchClient } from '@sinch/sdk-core'; // Initialize Sinch client const sinchClient = new SinchClient({ projectId: process.env.SINCH_PROJECT_ID, keyId: process.env.SINCH_KEY_ID, keySecret: process.env.SINCH_KEY_SECRET }); async function sendSMS() { try { const response = await sinchClient.sms.batches.send({ sendSMSRequestBody: { to: ['+594XXXXXXXXX'], from: 'YourBrand', body: 'Votre message ici' } }); console.log('Message sent:', response); } catch (error) { console.error('Sending failed:', error); } }MessageBird (Bird)
MessageBird provides SMS services with specific support for French territories.
import { MessageBirdClient } from 'messagebird'; // Initialize MessageBird client const messagebird = new MessageBirdClient(process.env.MESSAGEBIRD_API_KEY); // Function to send SMS const sendSMS = async () => { const params = { originator: 'YourBrand', recipients: ['+594XXXXXXXXX'], body: 'Votre message ici', scheduledDatetime: null // Optional scheduling }; try { const response = await messagebird.messages.create(params); console.log('Message sent:', response); } catch (error) { console.error('Error:', error); } };Plivo
Plivo's API supports SMS messaging to French Guiana with detailed delivery tracking.
import { Client } from 'plivo'; // Initialize Plivo client const client = new Client( process.env.PLIVO_AUTH_ID, process.env.PLIVO_AUTH_TOKEN ); async function sendSMS() { try { const response = await client.messages.create({ src: 'YourBrand', // Sender ID dst: '+594XXXXXXXXX', // Destination number text: 'Votre message ici', url: 'https://your-callback-url.com', // Optional delivery report URL }); console.log('Message sent:', response); } catch (error) { console.error('Error:', error); } }API Rate Limits and Throughput
Strategies for Large-Scale Sending:
Error Handling and Reporting
Recap and Additional Resources
Key Takeaways
Compliance Priorities
Technical Considerations
Best Practices
Next Steps
Regulatory Review
Technical Setup
Operational Planning
Additional Information: