Locale Summary
| Locale name | Guinea |
|---|---|
| ISO code | GN |
| Region | Middle East & Africa |
| Mobile country code | 611 |
| Dialing code | +224 |
Guidelines
| Two-way SMS supported | No |
|---|---|
| Message length | ----- |
| Twilio MMS support | Converted to SMS with embedded URL |
| Sending SMS to landline numbers | You cannot send SMS to a landline destination number: the Twilio REST API will throw a 400 response with error code 21614, the message will not appear in the logs, and the account will not be charged. |
| Compliance considerations | Twilio strongly encourages customers to review proposed use cases with qualified legal counsel to make sure that they comply with all applicable laws. The following are some general best practices:
|
Phone Numbers & Sender ID
| Alphanumeric | Long Code | Short Code | |||
|---|---|---|---|---|---|
| Pre-registration | Dynamic | Domestic | International | ||
| Operator network capability | Required | --- | --- | Not Supported | Supported |
| Twilio supported |
Required
Learn more | --- | Not Supported | Supported | Not Supported |
| Sender ID preserved | Yes | --- | --- | --- | --- |
| Provisioning time | 3 weeks | None | --- | --- | --- |
| UCS-2 support | Supported | --- | --- | --- | --- |
| Use case restrictions | For MTN network specifically, Alphanumeric Sender IDs are only supported through pre-registration. | --- | --- | Numeric International sender ID is not supported to the MTN network in Guinea. Messages submitted with numeric would result in delivery failure. Send only with alphanumeric sender ID to this network. | --- |
| Best practices | Please refrain from using generic sender IDs like InfoSMS, INFO, Verify, Notify etc to avoid being blocked by network operators. | --- | --- | --- | --- |
| Alphanumeric - Pre-registration | |
|---|---|
| Operator network capability | Required |
| Twilio supported |
Required
Learn more |
| Sender ID preserved | Yes |
| Provisioning time | 3 weeks |
| UCS-2 support | Supported |
| Use case restrictions | For MTN network specifically, Alphanumeric Sender IDs are only supported through pre-registration. |
| Best practices | Please refrain from using generic sender IDs like InfoSMS, INFO, Verify, Notify etc to avoid being blocked by network operators. |
| Alphanumeric - Dynamic | |
|---|---|
| Operator network capability | --- |
| Twilio supported | --- |
| Sender ID preserved | --- |
| Provisioning time | None |
| UCS-2 support | --- |
| Use case restrictions | --- |
| Best practices | --- |
| Long Code - Domestic | |
|---|---|
| Operator network capability | --- |
| Twilio supported | Not Supported |
| Sender ID preserved | --- |
| Provisioning time | --- |
| UCS-2 support | --- |
| Use case restrictions | --- |
| Best practices | --- |
| Long Code - International | |
|---|---|
| Operator network capability | Not Supported |
| Twilio supported | Supported |
| Sender ID preserved | --- |
| Provisioning time | --- |
| UCS-2 support | --- |
| Use case restrictions | Numeric International sender ID is not supported to the MTN network in Guinea. Messages submitted with numeric would result in delivery failure. Send only with alphanumeric sender ID to this network. |
| Best practices | --- |
| Short Code | |
|---|---|
| Operator network capability | Supported |
| Twilio supported | Not Supported |
| Sender ID preserved | --- |
| Provisioning time | --- |
| UCS-2 support | --- |
| Use case restrictions | --- |
| Best practices | --- |
For the benefit of all our customers, these guidelines are provided to help you comply with applicable requirements and to help ensure Twilio's platform remains compliant with global telecommunications ecosystem requirements. These guidelines represent our current understanding of common compliance requirements generally applicable to Twilio and its customers, and do not constitute legal advice. By posting these guidelines, Twilio makes no assurances regarding the legal compliance of your application built using our APIs. You are expected to understand and abide by all compliance obligations applicable to your specific application. You should check these pages regularly for updates as telecommunications ecosystem requirements continue to evolve and change, and the information below may be updated or changed without notice.