Sinch Community

Sinch offers several options to service your existing numbers: Hosted Messaging Porting Imported Numbers (local numbers only) To learn more click here.  ... View more

Sinch offers the following options to service your existing local or toll-free numbers: Porting Hosted Messaging Imported Numbers   Porting If you would like to use Sinch as your voice service provider (instead of your existing provider), then you need to port your numbers to Sinch. Porting your numbers will enable you to use Sinch voice service and, if desired, text service for the ported numbers.   To port your local number to Sinch, complete the Sinch Letter of Authorization for Local Number Porting and send to your Sinch Account Manager. To port your toll-free number to Sinch, complete the Sinch Letter of Authorization for Toll-Free Numbers Porting and send to your Sinch Account manager.    Note: If you want to port your number to Sinch for voice, and migrate your existing messaging service to Sinch, it is recommended to migrate messaging first, then port your number. This is because some providers will release a number for messaging if it has been ported for voice, which may disrupt your existing messaging service.   Hosted Messaging If you intend to keep your voice service with your existing provider, then you can host your numbers for messaging with Sinch. You can host your numbers if they are already text enabled or, if not, Sinch can enable text messaging so you can send and receive messages on your voice-enabled numbers (including landline, wireline or VoIP numbers). Hosting your numbers allows you to use Sinch text services and leave your voice services with your existing voice service provider.   To host your numbers with Sinch, we recommend you use the following automated process: Hosting SMS Numbers for US and Canada.   Note: Mobile numbers are not eligible for hosted messaging with Sinch. If you would like Sinch to provide messaging for your mobile number, you can port the number to Sinch for voice first, and then enable messaging services with Sinch.   Imported Numbers If you have a non-Sinch number that you want to enable for text messaging with Sinch as the Direct Connect Aggregator (DCA) and use your own NNID, you can import the number to Sinch. Importing is supported for local numbers in the North American Numbering Plan (NANP) only, it is not supported for toll-free numbers. For more information see Importing Numbers.   Contact Sinch if you have any questions. ... View more

E-mail 365 now supports Brand Indicators for Message Identification (BIMI).   Read the Sinch Email 365 - BIMI Support guide to learn more.    ... View more

When you create an account on the Sinch Customer Dashboard , a default project is automatically created for you with an associated ProjectID. Sinch uses projects to group contacts and apps together to manage and connect a unique set of keys and secret IDs for all your Sinch API products. Contacts are shared across apps within the same project. Note: Not all users are currently able to view and manage their projects. If you would like access to this functionality - please reach out to your Sinch Account Manager or contact our Online Team.   Depending on your requirements, you may need to create additional projects to keep contact lists separate.   Related Articles: What is a project and how to manage projects? Creating a new project What is a project ID? What is a subproject and how to manage subprojects? Sinch Account Model. ... View more

More and more customers are needing to move from P2P to A2P messaging as mobile carriers (operators) want their customers to use A2P messaging.   Sinch allows you to migrate your P2P numbers to A2P numbers with no disruption in your services. Follow the steps outlined below:   Customer Requirements   Before you, can migrate your P2P number(s) to A2P number(s) you need to have the following: P2P NNID with A2P exceptions. Note: For T-Mobile numbers this will need to be provisioned with T-Mobile. Active CampaignID that has been registered with the Campaign Registry (TCR) and approved by Sinch as the DCA (Direct Connectivity Aggregator). Testing and Processing Steps Step 1 - Update or validate the Override Service Registry (OSR) database to see there is a P2P NNID (with A2P exception) updated in the OSR database. Step 2 – Send test MO and MT to see if they work. Step 3 - If your testing is successful, import your number(s) using the Import number API or you can import number using the Sinch Customer Dashboard. Ensure you link the number(s) to an active and approved campaign where Sinch is the DCA. This step (using the API or Dashboard processes) will also update the SMS App ID as part of same process (which is a prerequisite). Step 4 – Again send test MO and MT to see if they work. Step 5 - If your testing is successful, update the OSR with the CampaignID, A2P context and change to the new A2P NNID. Note: You can use NetNumber APIs to complete this update process. Step 6 - Again send test MO and MT to see if they work. We recommend you complete these test and processing steps for several numbers to determine everything is working properly, and then you can use the simplified process below for the rest of your numbers. Simplified Process once you have completed testing Step 1 - Import your number(s) using theImport number API or you can import number using the Sinch Customer Dashboard. Ensure you link the number(s) to an active and approved campaign where Sinch is the DCA. This step (using the API or Dashboard processes) will also update the SMS App ID as part of same process (which is a prerequisite). Step 2 - Update the OSR with the CampaignID, A2P context and new A2P NNID. ... View more