Sinch Community

Click here to learn how to create a sole proprietor brand for 10DLC. ... View more

RCS for Business offers a modernized, verified, branded, and secure messaging experience compared to traditional SMS. Here is a clear overview of how RCS secures messages and protects business-to-consumer communications.     Data Encryption     RCS for Business message are encrypted in transit and at rest, but not end-to-end. RCS employs multi-layered encryption to protect message data during transmission and storage:  Encryption in Transit:  Messages sent via RCS are encrypted while traveling across network boundaries—specifically between the end-user’s device (both Android and iOS), Google’s servers, and messaging platforms (such as Sinch).   Encryption at Rest: Messages stored temporarily on server infrastructure (like Google’s servers) are encrypted while resting on the disk.   On-Device Storage: Messages stored locally on the recipient's phone rely on the device’s native operating system security (for example, device passcode, storage encryption).     Business Verification & Fraud Prevention   Unlike standard SMS, which is vulnerable to spoofing and "smishing" (SMS phishing), RCS for Business introduces strict identity verification features:    Security Feature  Benefit  Verified Sender Identity  Businesses undergo carrier and partner verification before sending messages, making it harder for scammers to impersonate trusted brands.  Branded Profile  Verified business profiles display company logos, brand colors, and official contact information directly within the messaging interface.  Trust Badges  Visual verification badges confirm to the recipient that the message originated from an authenticated business entity.      Summary       By combining in-transit and at-rest encryption with verified business identities, RCS significantly reduces the risk of phishing attacks, protects sensitive interaction data, and provides consumers with a trusted messaging channel.    Read the Sinch Blog post for the latest RCS Security information.    For more information on RCS, visit the Sinch RCS product page. ... View more

This article explains the benefits of vetting your brand and describes the vetting process. The primary benefit of vetting is the potential to increase your daily messaging limits, gain access to special use cases, and improve your quality of service where applicable.    Vetting is not mandatory and is generally only needed if you require high-volume messaging throughput.    There are two levels of vetting to consider:    Standard Vetting  This is a basic credit check performed on a brand during the 10DLC registration process. It assesses a brand's general legitimacy. Think of it as your messaging credit score. The higher the score the better the benefits:  Increased Message Throughput: A higher score directly translates to the ability to send more messages per second, minute, and day. This is critical for time-sensitive campaigns and large-scale outreach.  Improved Deliverability: Vetted brands experience fewer blocked messages, which means more of your messages reach their intended recipients. 



  Reduced Filtering: Messages from brands with high vetting scores are less likely to be flagged as spam by mobile carriers, ensuring your communications are not unnecessarily filtered. 



  Access to Special Use Cases: Vetting is a prerequisite for certain "special" use cases that can provide even higher throughput and potentially lower messaging fees.  Enhanced Brand Reputation: A high score signals to carriers that your brand is a legitimate and trusted sender, which can lead to better overall treatment and priority of your messaging traffic. 



  Improved Customer Engagement: When customers reliably receive your messages, it builds trust and can lead to higher engagement and open rates.  Risk Mitigation: By going through the vetting process, you are actively working to ensure compliance with carrier guidelines and industry regulations, which reduces the risk of penalties or being blacklisted  Better ROI: By improving deliverability and reducing filtering, a high vetting score can lead to a better return on investment for messaging campaigns.  Enhanced Vetting  This involves a more detailed investigation of your brand. While this may result in a higher vetting score and improved throughput, it is not guaranteed.    During the 10DLC registration process, you may have opted to skip Brand Vetting to accelerate time to market. Skipping vetting introduces a key risk: as your messaging volume grows, you may exceed your permitted throughput and encounter carrier restrictions.   This article outlines your options:   If you have not completed Brand Vetting but now need to: 
Learn how to initiate and complete the vetting process.   If you have already completed Brand Vetting but need higher throughput: 
Understand the available paths to qualify for a higher carrier throughput tier.   Below, we walk through each scenario and the steps required to help you avoid blocking due to Brand quota limitations.     The vetting process is managed through The Campaign Registry (TCR) and can be initiated on your behalf by a Customer Service Provider (CSP) through external vetting partners. Depending on your business type and use case, you will be assigned a vetting score ranging from 1-100. 
    Learn How to Initiate & Complete the Brand Vetting Process via The Campaign Registry (For CSP Customers):     Steps for Vetting your Brand:     Access The Campaign Registry (TCR) or get your CSP to do this on your behalf: Log in to your TCR account. Ensure the brand you intend to vet is already registered.  Navigate to the "Brand Details" Page: Select the specific brand and proceed to its "Brand Details" page:  Initiate Vetting: On this page, you scroll down and will find the Apply for Vetting option: Select Vetting Partner and Level: Choose an external vetting partner from the available options and decide between "Standard" (similar to a basic credit check) or "Enhanced" (a more detailed investigation) vetting:  Selecting "Standard": Costs $41.50 and typically takes up to 3 business days.  Selecting "Enhanced”: Costs $101.50 and takes up to 5 business days, however time may vary.  Click Submit. Follow the prompts to submit your vetting request, providing any additional required brand information and/or documentation.  Monitor Status: Track the progress of your vetting request within TCR. Once completed, your brand's vetting score will be displayed on the "Brand Details" page.  One critical last step:  After your Brand has been vetted and the Brand score has been established or updated, you must go back to any campaigns currently in production and associated with the Brand, and "resubmit" the campaign in order for the daily caps to get updated on T-Mobile. Daily limits do not automatically get updated. You must resubmit the campaign to get them updates. Resubmitting the campaign does not resubmit it to the DCA, or update any billing mechanisms.    Understand the Available Paths to Qualify for a Higher Carrier Throughput Tier -Brand Vetting Requests (For Sinch Direct Customers):    You can contact your Account Manager, or you can create a ticket directly into our ticketing system at support.sinch.com to request Brand Vetting. Technically, you don’t need to create a login to create a ticket. A login is recommended, though, so that you can manage your current tickets and/or track any past tickets.     Additional Remedies for Increasing Throughput:    1) Optimizing Your Sending Practices    For better deliverability and to ensure compliance with daily messaging limits, we recommend adjusting your sending strategy from large, single-day "blasts" to a more distributed cadence.    Recommendation:  Instead of sending all your messages at once, pace your campaigns by spreading the total volume across multiple days. For example, if your daily cap is 10,000 messages and you need to send 16,000, schedule the campaign to send 8,000 messages on two consecutive days.    Key Insights & Benefits:  Avoids Exceeding Daily Caps: This is the most direct way to stay within your daily carrier-allotted message limit and prevent service disruptions.    Suggestion:  Utilize message scheduling tools to automate this process. By planning your campaigns to run over several days, you can maintain a steady sending rhythm, ensuring compliance and maximizing the successful delivery of your messages, while complying with brand daily sending allotments.     2) Upgrading Your Campaign for Higher Throughput    If you are currently using a "UCaaS LOW" campaign and find its 2,000-message daily limit restrictive, the most effective solution is to upgrade to a "UCaaS HIGH" campaign.    Recommendation:  To qualify for a UCaaS HIGH campaign, your brand must first undergo the vetting process. We recommend initiating this process as soon as you anticipate needing higher volume. This strategic upgrade will most likely move you beyond the 2,000-message cap.    Key Insights & Benefits:  Unlocks Higher Volume: The UCaaS HIGH campaign type is specifically designed for vetted brands requiring greater messaging capacity.  Improves Brand Reputation: Successfully completing the vetting process demonstrates your brand's legitimacy to carriers, which can lead to improved message deliverability and a better sender reputation.    Suggestion:  When initially registering your brand, don’t necessarily look for the lowest cost option. Review what your needs are and consider the future requirements. If you think you will need more than 2,000 messages towards T-Mobile, consider using the UCaaS HIGH use case, but remember, you would also need to perform brand vetting to get a brand score which will hopefully give you a higher tier towards T-Mobile.     Visit the Sinch 10DLC Product Page to learn more about Sinch 10DLC or if you need more help with 10DLC or have any questions, contact Sinch, who will be happy help!  ... View more

Onboarding for RCS is separated into two phases: RCS Agent Registration and RCS Agent Launch. Below are the country and carrier specific rules for these phases.   Review these before registering an RCS Agent to ensure the agent is set up correctly and will be approved for launch.     RCS Agent Registration   Sinch tools and platforms can be used to register (create) RCS agents. A guide to creating an RCS agent in the Sinch Build Dashboard is available here.   Provisioning API is available as a programmatic solution.   After an agent is created, test messages can be sent to RCS for Business enabled devices. Agents can be registered and tested on enabled devices in any country, even where RCS for Business is not currently available for launch. Country coverage can be viewed here. Supported countries/carriers are updated regularly, check with your Account Manager for the latest. Available markets relate to where an RCS message is terminated, not where a company is based/originating the message.   Note: Some carriers include messages on non-verified agents during testing, highlighting that the agent is not verified.       RCS Agent Launch   RCS agents must be submitted for verification and approval before live traffic can be sent. The processes and requirements for verification and launch are determined by Google and the mobile carriers.   Launch status can be found using the Provisioning API or the Build Dashboard. Updates may also be communicated by your Account Manager.     Carrier requirements and steps for launch   Note: RCS requirements and rules change periodically. Sinch continues to evolve our process to meet these changes. For up-to-date detail confirmation and answers to any questions, reach out to your Account Manager.   Carriers have varying requirements for verification and launch; most of this information is collected as part of the set up and launch process, but some steps need to be completed separately.   Timelines for launch vary by region and carrier. The best way to ensure a quick and smooth launch is to ensure all guidelines are followed, and all required information is provided in a timely manner.       Carrier/Country Specific Rules   Brazil Generic senders are not allowed – all agents must be for the brand sending the messages No multi-use agents allowed. France For Upscale the message must contain a weblink for opt-out If a paid phone number is included the rate should be indicated in the phone label (i.e. .025 €/min) Germany Generic senders are not allowed – all agents must be for the brand sending the messages T&C should be in German or include the option for a translated version If a contact number is provided, it must be a +49 number An agent name can only be used once, even by different partners (i.e. there can only be one agent called Sinch, other agents need to be called Sinch OTP, Sinch Promotions). Gambling services are permitted only for brands with an official Germany gambling license. A copy of the official license must be provided. The carriers will contact the support channel provided; you must reply to any messages they send/calls made. India No multi-use agents allowed. Additional sending rules or limitations may apply, check with your Account Manager to confirm details. UK If a contact number is provided, it must be +44 number Demo agents must have “demo” in the agent’s name The region for RCS agents must be set to EU during agent registration. The Privacy Policy and Terms must be relevant to the UK/EU market. US Generic senders are not allowed – all agents must be for the brand sending the messages The agent's description must include information about what the agent does and the service it provides (i.e. no taglines). The region for RCS agents must be set to US during agent registration. Wireframes are required for agents requesting Conversational billing. The digital assets (logos, banners) submitted for brand verification must exactly match the agent details. Brand vetting tokens expire after 12 months and must be renewed to avoid suspension.  RCS campaigns must meet the exact same compliance, opt-in, and CTA standards required for US Short Codes. Ensure campaigns align with the criteria detailed in the US Short Code Campaign Compliance Overview. In addition to the content prohibited by Google’s Acceptable Use policies, the following content is also prohibited: T-Mobile. Age-gated content (as defined in the T-Mobile Code of Conduct) Donation/Pledge Solicitation Loan Arrangement Social Media Sweepstakes/Contest. AT&T Payday loans, cash advance services No loan ads other than messages from direct lenders for secured loans No credit repair debt relief No work from home/secret shopper ads No lead gen campaigns that indicate sharing information with 3 rd parties No charitable donation campaigns (text to donate). Verizon Collections from 3 rd parties (collection agencies) Short term loan campaigns (except from direct lender) Generic job alerts (except for a company hiring for themselves) Affiliate marketing. AT&T requires wireframes for agents requesting Conversational billing.     Carrier/Country Specific Steps   Google, Sinch, the mobile carrier, or a third-party verification company might reach out to request additional information. Send documentation to your Account Manager unless otherwise specified.   The Sinch name is often included in the communication with brands for agent verification. The name can be excluded or changed on some carriers but not on all. The steps to exclude the Sinch name are listed below where it’s possible.     Country  Carrier/Country Specific Registration Steps  White-Label Launch Supported?  White-Label Special Process & Documentation  Global  Google Managed Carriers: The brand must reply to a verification email from Google.     A corporate email address matching the brand domain is required.  Emails will come from [email protected].    US only  In the US: Notify your Sinch AM before submitting for launch to ensure Google does not mention Sinch's name in the approval email sent to the brand.    Outside the US: Google will include Sinch's name in the approval email.  Austria  Submit the completed Brand Approval Letter to the carriers and your AM.  Yes  Complete the Approval letter twice. Once with the brand authorizing the partner and once for the partner authorizing Sinch.   Belgium  Provide the completed Telenet Registration letter to your AM.  Yes  No special process required  Brazil  Brand must provide explicit approval and tax details (Tax ID).     The brand must reply to an authorization email sent by ABR Telecom to complete the verification for all carriers  Yes  No special process required  Canada  Complete and submit the CTA Agent Application form to your AM.   Yes  Include the ASP and DCA details on the application form. Notify your AM that Sinch’s name should be removed from the LOA.  Czech Republic  Submit the completed T-Mobile RBM consent form to your AM.  Yes  A second copy of the Consent Form needs to be provided. Once with the brand authorizing the partner and once for the partner authorizing Sinch.  Denmark    Yes  No special process required  Finland  Submit the completed Brand Approval Form to your AM.  No    France  SIREN (Company ID number) is required.    Carriers may reach out directly to the brand via phone/email to verify that the agent contact details are active and legitimate.    The brand must reply to an email from Google to complete verification for Lycamobile and NRJ Mobile No  Both of the following documents must be fully executed and submitted:  Free Mobile Authorization letter(between Sinch and the reseller)  Authorization letter (between the brand and the reseller)  Lycamobile and NRJ Mobile  are managed by Google, and Google does not support removing the Sinch name from the brand approval email at this time.   Germany  Submit the Brand Approval Form to your Sinch Account Manager.     It must be hand-signed in blue ink and stamped (or signed via verified DocuSign).  Modified templates will not be accepted  Yes  Two letters must be submitted to your Sinch Account Manager.    One signed by the brand, to authorize the Reseller and one signed by the Reseller, to authorize Sinch.  Greece    Yes  No special process required  Hungary    Yes  No special process required  India  Complete the Bot Verification sheet and send to your Sinch Account Manager   Yes  Notify your Sinch AM before submitting for launch. Italy  For Vodafone, submit the completed Brand Verification letter to your Sinch Account Manager.   For all other carriers the brand must reply to an email from Google to complete verification.  No  Vodafone: No special process required    All other carriers are managed by Google, and Google does not support removing the Sinch name from the brand approval email at this time.  Mexico    Yes  No special process required  Netherlands  For Vodafone, KPN and Odido, complete and submit the Brand Verification letter    Note: The Google RCS Agent ID is required for this letter and can be retrieved from Sinch Build or your AM.  No    Norway    Yes  No special process required  Peru    Yes  No special process required  Poland    Yes  No special process required  Portugal The brand must reply to an email from Google in order to complete verification No All available carriers are managed by Google, and Google does not support removing the Sinch name from the brand approval email at this time. Singapore  Must submit the company's official ACRA (registration certificate) along with a completed Letter of Authorization (LOA) to your Sinch Account Manager.   The brand must reply to an email from Google to complete verification for M1, Simba Telecom and Starhub.   No  Not supported by SingTel.    All other carriers are managed by Google, and Google does not support removing the Sinch name from the brand approval email at this time.   Slovakia    Yes  No special process required  Spain  The brand must reply to an email sent from Google for the Digi network.   Yes  The brand approval email Google sends to the brand references Telefonica instead of Sinch.  Sweden   Yes No special process required. UK  The brand must copy, fill out, and send the UK Carrier Approval Email Template (see below and in Sinch Build) to the designated operator email addresses in the template.   To: [email protected]; [email protected]   Subject: [AGENT NAME] RBM brand approval   Hi,   Approval for Agent: [GOOGLE AGENT ID] I at [BRAND/COMPANY NAME] confirm that I am authorised to use the following name: [AGENT NAME], logo and images, as shown in the attached image file (s) for the RBM agent.   I hereby confirm that I give permission to Sinch to register this RBM agent and use the logo for the purpose of sending RBM messages to the users of [OPERATOR NAME] networks (s) on our behalf.   Regards [FULL NAME] [JOB TITLE] [COMPANY]     BT and Telefonica have appointed third party verification partners, who will each send an email to the brand for approval on those two networks. The brand must reply to these emails.    The brand’s company registration number (or international equivalent) is required.     UK sole traders are assessed on a case-by-case basis provided a VAT number is supplied. Review may take longer than for an established medium or large business with a moderate/large digital footprint.  Non-UK sole traders cannot be verified at this time.    The brand must reply to an email from Google to complete verification for Lycamobile and Sky Mobile.  No  Two separate authorization emails must be sent to the carriers: One from the brand authorizing the reseller, and one from the reseller authorizing Sinch.   Contact your Sinch Account Manager before submitting for launch to request the Sinch name be excluded for BT and Telefonica.   Sky Mobile and Lycamobile are managed by Google, and Google does not support removing the Sinch name from the brand approval email at this time. US  Brand Vetting: Submit the completed Brand Verification Form to your account manager. Brand vetting must be completed prior to carrier submission.   Carrier Approval: Submit the Verizon Launch form and the US Requirements Form to your Sinch Account Manager.   The brand must reply to an email from Google to complete verification for Google Fi and CSpire.  Yes  For Google Fi and CSpire: Notify your Sinch AM before submitting for launch to ensure Google does not mention Sinch's name in the approval email sent to the brand.    For all other carriers, ensure the correct partner's name is used in the required forms.      Reminder: If Google learns that an agent is in violation of Google’s Acceptable Use Policy or an agent experiences high spam reports, they may notify the carriers and Sinch and un-launch the agent. ... View more