Table of Contents

Configuration

If you have not read it yet, start with Introduction.

SMS is configured entirely through the Settings module. Operators use the Admin Panel to enable SMS, choose a provider, enter credentials, and edit message templates. Values are stored with the rest of Settings (not in client appsettings.json).

Provider

Today DevKit supports Twilio as the SMS provider. The Settings model is ready for additional providers later; when more are added, you will select them here the same way. Settings — Tutorials: SMS walks through creating a Twilio account and mapping Account SID, Auth token, and From phone number into the UI.

Templates and built-in modules

Some prebuilt modules use the built-in SMS service to notify users by text. For example, Identity sends SMS for flows such as two-factor authentication, and Payment can send SMS such as order confirmations. Those modules do not embed fixed message text in code for those notifications; they resolve content from SMS templates you maintain in the Settings module.

In the Admin Panel, open Settings and use the SMS section. There you configure SMS-related options and edit the templates those modules use when they send a message. Adjust wording, placeholders, and any template-specific fields so notifications match your product and tone.

Templates and provider fields are maintained per language (culture)—pick the language in the Admin Panel, edit SMS for that culture, then repeat for each language you support so messages match what your users expect.

See also