Send OTP codes and SMS campaigns via SMSPortal

How it works

SMSPortal is one of two natively supported SMS gateways in Powerlynx, the other being Twilio. To connect, create an account at SMSPortal, navigate to Settings → API Keys, and create a new key with type set to REST. Copy the Client ID and API Key, then add a new SMS gateway in Powerlynx under Config → SMS, selecting SMSPortal as the type.

Once connected, Powerlynx routes all outbound SMS through SMSPortal — OTP codes for phone number verification at the captive portal, mass SMS campaigns, voucher code delivery, and 1:1 messages sent from customer profiles. All sent messages are logged under Logs / SMS Logs with per-message delivery status and timestamps.

Fallback configuration

Powerlynx supports multiple SMS gateways simultaneously. The gateway at the top of the list is used as primary, any additional enabled gateway acts as fallback if the primary fails. Gateways can be reordered by drag and drop. SMSPortal can act as primary with Twilio as fallback, or as fallback to Twilio, depending on the order configured.

What this integration provides

• OTP SMS delivery for phone number verification at the captive portal.
• Mass SMS campaigns — service announcements, promotions, bulk notifications.
• Voucher code delivery via SMS for offline redemption.
• 1:1 SMS from customer profiles in Powerlynx.
• Primary or fallback gateway.
• Full delivery status and audit trail under Logs / SMS Logs.
• Balance monitoring with email and dashboard alerts.

Credentials required

Client ID and API Key from Settings → API Keys in your SMSPortal account (type: REST).

Requirements

• SMSPortal account.
• Client ID and API Key (REST type).
• OTP verification for the splash page is optional — enabled or disabled per splash page in Powerlynx.

How to connect SMSPortal to Powerlynx and configure it as your primary or fallback SMS gateway — step-by-step guide.