# 3. SMS Integration

User Type: **Super Administrator**
Source: *Mi Digital Academy - Education CRM Features Document*

---

## 3. SMS Integration

### 3.1 OTP for Login Verification
**What it does:** Sends the OTP for the login verification: the OTP (the OTP, the user, the phone, the code, the expiry) is sent to the user's phone, so the login is verified (the OTP is the verification). The Super Administrator sends the OTP for the login verification (the OTP, the user, the phone, the code, the expiry) so the OTP is structured and the verification is explicit.

**Sub-features:**
- OTP: the OTP (the OTP, the user, the phone, the code, the expiry)
- User: the user (the user, the phone, the OTP)
- Phone number: the phone (the phone number of the user, the format)
- OTP code: the code (the code of the OTP, the digits)
- OTP expiry: the expiry (the expiry of the OTP, the duration)
- OTP status: the status (the sent, the verified, the expired)
- OTP resend: the resend (the resend of the OTP, the limit, the cooldown)
- Audit logging of the OTP sending

**Super Administrator User Journey:**
1. Super Admin sends the OTP for the login verification: the OTP (the OTP, the user, the phone, the code, the expiry), the user (the user, the phone, the OTP), and the phone (the phone number of the user, the format); the OTP is explicit.
2. Selects the user: the user (the user, the phone, the OTP); the user is the recipient.
3. Verifies the phone number: the phone (the phone number of the user, the format); the phone is the channel.
4. Generates the OTP code: the code (the code of the OTP, the digits); the code is the secret.
5. Sets the OTP expiry: the expiry (the expiry of the OTP, the duration); the expiry is the limit.
6. Sends the OTP: the send (the send of the OTP, the time, the status); the send is the action.
7. Views the OTP status: the status (the sent, the verified, the expired); the status is the state.
8. The OTP is sent: the OTPs, the users, the phones, the codes, so the verification is complete.
9. The OTP sending is audit-logged with the OTP, the user, and the timestamp.

**Rules & Edge Cases:**
- The OTP is the verification (the OTP, the user, the phone, the code, the expiry); the OTP is the proof.
- The user is the recipient (the user, the phone, the OTP); the user is the target.
- The phone number is the channel (the phone number of the user, the format); the phone is the medium.
- The OTP expiry is the limit (the expiry of the OTP, the duration); the expiry is the control.
- The OTP is sent (the OTPs, the users, the phones, the codes); the verification is managed.
- OTP sending is audit-logged with the OTP, user, and timestamp.

### 3.2 Important Alerts via SMS
**What it does:** Sends the important alerts via SMS: the alert (the alert, the user, the content, the date) is sent via SMS to the user, so the user is alerted (the alert is the notification). The Super Administrator sends the important alerts via SMS (the alert, the user, the content, the date) so the alert is structured and the notification is explicit.

**Sub-features:**
- Alert: the alert (the alert, the user, the content, the date)
- User: the user (the user, the phone, the alert)
- Alert content: the content (the content of the alert, the text, the type)
- Alert type: the type (the type of the alert, e.g., the payment, the expiry, the security)
- Alert date: the date (the date of the alert, the time)
- Alert status: the status (the sent, the delivered, the read)
- Alert view: the view (the alerts, the users, the content, the dates)
- Audit logging of the alert sending

**Super Administrator User Journey:**
1. Super Admin sends the important alert via SMS: the alert (the alert, the user, the content, the date), the user (the user, the phone, the alert), and the content (the content of the alert, the text, the type); the alert is explicit.
2. Selects the user: the user (the user, the phone, the alert); the user is the recipient.
3. Creates the alert content: the content (the content of the alert, the text, the type); the content is the message.
4. Sets the alert type: the type (the type of the alert, e.g., the payment, the expiry, the security); the type is the category.
5. Sets the alert date: the date (the date of the alert, the time); the date is the moment.
6. Sends the alert: the send (the send of the alert, the time, the status); the send is the action.
7. Views the alert status: the status (the sent, the delivered, the read); the status is the state.
8. The alert is sent: the alerts, the users, the content, the dates, so the notification is complete.
9. The alert sending is audit-logged with the alert, the user, and the timestamp.

**Rules & Edge Cases:**
- The alert is the notification (the alert, the user, the content, the date); the alert is the message.
- The user is the recipient (the user, the phone, the alert); the user is the target.
- The alert content is the message (the content of the alert, the text, the type); the content is the payload.
- The alert type is the category (the type of the alert, e.g., the payment, the expiry, the security); the type is the segment.
- The alert is sent (the alerts, the users, the content, the dates); the notification is managed.
- Alert sending is audit-logged with the alert, user, and timestamp.

### 3.3 Bulk SMS for Promotions
**What it does:** Sends the bulk SMS for the promotions: the bulk SMS (the SMS, the audience, the content, the date) is sent to the audience, so the promotion is broadcast (the bulk is the broadcast). The Super Administrator sends the bulk SMS for the promotions (the SMS, the audience, the content, the date) so the bulk is structured and the broadcast is explicit.

**Sub-features:**
- Bulk SMS: the SMS (the SMS, the audience, the content, the date)
- Audience: the audience (the audience of the SMS, the segment, the count)
- SMS content: the content (the content of the SMS, the text, the offer)
- Send date: the date (the date of the send, the time)
- Send status: the status (the scheduled, the sent, the completed)
- Delivery rate: the rate (the rate of the deliveries, the percentage)
- SMS view: the view (the SMSs, the audiences, the content, the dates)
- Audit logging of the bulk SMS sending

**Super Administrator User Journey:**
1. Super Admin sends the bulk SMS for the promotion: the SMS (the SMS, the audience, the content, the date), the audience (the audience of the SMS, the segment, the count), and the content (the content of the SMS, the text, the offer); the bulk is explicit.
2. Selects the audience: the audience (the audience of the SMS, the segment, the count); the audience is the target.
3. Creates the SMS content: the content (the content of the SMS, the text, the offer); the content is the message.
4. Sets the send date: the date (the date of the send, the time); the date is the moment.
5. Sends the SMS: the send (the send of the SMS, the time, the status); the send is the action.
6. Views the delivery rate: the rate (the rate of the deliveries, the percentage); the rate is the measure.
7. The bulk is sent: the SMSs, the audiences, the content, the dates, so the broadcast is complete.
8. The bulk SMS sending is audit-logged with the SMS, the audience, and the timestamp.

**Rules & Edge Cases:**
- The bulk SMS is the broadcast (the SMS, the audience, the content, the date); the SMS is the message.
- The audience is the target (the audience of the SMS, the segment, the count); the audience is the recipient.
- The SMS content is the message (the content of the SMS, the text, the offer); the content is the payload.
- The delivery rate is the measure (the rate of the deliveries, the percentage); the rate is the engagement.
- The bulk is sent (the SMSs, the audiences, the content, the dates); the broadcast is managed.
- Bulk SMS sending is audit-logged with the SMS, audience, and timestamp.

### 3.4 Regional Language Support
**What it does:** Supports the regional languages for the SMS: the language (the language, the region, the SMS) is supported for the SMS, so the SMS is in the regional language (the language is the localization). The Super Administrator supports the regional languages for the SMS (the language, the region, the SMS) so the language is structured and the localization is explicit.

**Sub-features:**
- Language: the language (the language, the region, the SMS)
- Region: the region (the region of the language, e.g., the state, the country)
- SMS content: the content (the content of the SMS, the text, the language)
- Language selection: the selection (the selection of the language, the user, the region)
- Language status: the status (the active, the inactive)
- Language view: the view (the languages, the regions, the content)
- Language export: the export (the languages, the format, the region)
- Audit logging of the language configuration

**Super Administrator User Journey:**
1. Super Admin supports the regional language for the SMS: the language (the language, the region, the SMS), the region (the region of the language, e.g., the state, the country), and the content (the content of the SMS, the text, the language); the language is explicit.
2. Selects the language: the language (the language, the region, the SMS); the language is the medium.
3. Selects the region: the region (the region of the language, e.g., the state, the country); the region is the location.
4. Creates the SMS content: the content (the content of the SMS, the text, the language); the content is the message.
5. Sets the language selection: the selection (the selection of the language, the user, the region); the selection is the control.
6. Views the language status: the status (the active, the inactive); the status is the state.
7. The language is supported: the languages, the regions, the content, so the localization is complete.
8. The language configuration is audit-logged with the language, the region, and the timestamp.

**Rules & Edge Cases:**
- The language is the medium (the language, the region, the SMS); the language is the localization.
- The region is the location (the region of the language, e.g., the state, the country); the region is the geography.
- The SMS content is the message (the content of the SMS, the text, the language); the content is the payload.
- The language selection is the control (the selection of the language, the user, the region); the selection is the choice.
- The language is supported (the languages, the regions, the content); the localization is managed.
- Language configuration is audit-logged with the language, region, and timestamp.