Telecom Standards

SMS Delivery & Consent Policy

Last updated: October 7, 2026 · Telecom Gateway: Pahappa / EgoSMS Uganda

WedPool maintains strict operational standards to ensure all SMS communications sent to wedding contributors in Uganda are respectful, relevant, timely, and compliant with national telecommunication guidelines.

1. Transactional Nature of Messages

WedPool operates exclusively as a transactional communication engine for private wedding and matrimonial events. We strictly prohibit marketing spam, commercial advertising, financial loan promotions, or unsolicited bulk messaging.

Allowed message categories are strictly limited to:

  • Payment Receipts: Acknowledging that a contribution was received and credited to the couple's celebration.
  • Pledge Updates: Notifying a contributor of their remaining committed balance after a payment.
  • Public Transparency Links: Providing a secure link where a contributor can view the overall celebration progress.
  • Correction Notices: Clarifying any administrative record adjustments made by the committee treasurer.

2. Sender Identification (Sender ID)

All messages originate from licensed telecom aggregator routes using the pre-registered alphanumeric sender ID WedPool. This guarantees recipients can verify the authenticity of the notification on MTN Uganda and Airtel Uganda networks.

3. Respectful Quiet Hours Protocol

To avoid disturbing families and donors during late hours, WedPool enforces an automated quiet hours protocol across all campaigns:

  • Window: 21:00 (9:00 PM) to 07:00 (7:00 AM) East Africa Time (EAT).
  • Action: Any payment logged during quiet hours safely places the SMS into a Held Queue.
  • Morning Release: Held messages are automatically released and delivered once 07:00 AM arrives, ensuring respectful donor engagement.

4. Abuse Controls & Daily Send Caps

To prevent accidental message flooding and protect recipients from excessive notifications:

  • Daily Send Cap: Each campaign has a default maximum threshold (500 SMS segments per 24-hour cycle).
  • Transaction Deduplication: Every payment event is assigned a unique cryptographic deduplication key. Duplicate clicks or webhook retries will never generate duplicate SMS alerts.
  • Credit Ledger Verification: Campaigns must hold active SMS credits to dispatch messages, preventing unauthorized runaway queues.

5. Message Length & Character Encodings

SMS messages are calculated based on international GSM standards:

  • GSM 7-bit Encoding: Standard English text allows up to 160 characters per single SMS segment (or 153 characters per segment for multipart messages).
  • Unicode (UCS-2) Characters: If emojis or special characters are included, messages are formatted in UCS-2 (up to 70 characters per segment). WedPool automatically optimizes templates to maximize segment efficiency.

6. Contributor Opt-Out & Support

If a contributor prefers not to receive SMS notifications regarding their wedding contribution:

  • The committee treasurer can check “Save without SMS” when recording payments.
  • The contributor can send an email to support@wedpool.cloudcommet.com with their phone number to have their number placed on the global do-not-disturb list.

7. Inquiries & Telecom Compliance

For questions regarding our telecom aggregation partners, sender registration, or carrier delivery receipts, contact:

WedPool Telecom Relations
Email: telecom@wedpool.cloudcommet.com
Kampala, Uganda