Skip to content

Commit ecdc72c

Browse files
committed
Updates based on review
1 parent 7ec9875 commit ecdc72c

File tree

1 file changed

+6
-6
lines changed

1 file changed

+6
-6
lines changed

src/content/docs/authenticate/authentication-methods/sms-deliverability.mdx

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -10,15 +10,15 @@ relatedArticles:
1010

1111
Kinde encourages customers to configure their own SMS sender, so that verification, country registrations, sender IDs, and deliverability metrics are controlled and managed by you.
1212

13-
When SMS messages are sent via Kinde, we will use our shared service provider in the region to deliver the message as best effort only. Due to Kinde being a service provider, there are some limitations with applying for dedicated short codes or sender IDs in countries that have strict SMS sending regulations.
13+
When SMS messages are sent via Kinde, we use our regional shared service provider and attempt delivery on a best-effort basis. As Kinde is a service provider, there are limitations when applying for dedicated short codes or sender IDs in countries with strict SMS-sending regulations.
1414

1515
This topic describes SMS delivery via Kinde, deliverability factors, and some common reasons why delivery can fail.
1616

1717
## Manage your own SMS sender
1818

19-
By default, when you first start using Kinde, all SMS are sent from Kinde's shared service provider. It is recommended to configure your own SMS sender so that users receive authentication SMS that are branded by your business.
19+
By default, when you first start using Kinde, all SMS messages are sent from Kinde's shared service provider. We recommend configuring your own SMS sender so that users receive authentication messages branded with your business.
2020

21-
You’ll want to configure this before your production environment goes live. All you need is to add SMS details in Kinde settings. See [Set up phone or SMS authentication](/authenticate/authentication-methods/phone-authentication/).
21+
Configure this before your production environment goes live. Simply add your SMS details in Kinde settings. See [Set up phone or SMS authentication](/authenticate/authentication-methods/phone-authentication/) for step-by-step instructions.
2222

2323
## Deliverability factors when using Kinde's default SMS shared service provider
2424

@@ -51,15 +51,15 @@ The following countries have known bad delivery rates.
5151

5252
## Sender ID
5353

54-
Kinde has setup a shared SenderID for all customers using the default SMS shared service provider. This cannot be changed.
54+
Kinde has set up a shared Sender ID for all customers using the default SMS shared service provider. This cannot be changed.
5555

56-
Sender ID = ```KindeAuth```
56+
**Sender ID:** `KindeAuth`
5757

5858
To brand the Sender ID to your business, you will need to configure your own SMS delivery provider. See [Set up phone or SMS authentication](/authenticate/authentication-methods/phone-authentication/).
5959

6060
## SMS content
6161

62-
The content of the SMS is not editable due to strict one-time passcode requirements and recommendations from industry best practice.
62+
The content of the SMS is not editable due to strict one-time passcode requirements and industry best practices.
6363

6464
An example of the SMS content is below.
6565

0 commit comments

Comments
 (0)