Wiacom delivers transactional messages as a built-in platform capability. This covers registration confirmation, email verification, WiFi credential delivery, OTP / PIN for phone sign-up, and re-engagement communications (e.g. campaigns).
Two delivery options are available for each deployment.
Wiacom provides managed transactional email and SMS delivery through own channels, configured and operated on the backend.
Email is available by default for all deployments, covering:
- Registration confirmation and email verification
- WiFi credential delivery (WiFi Pass passphrases, Key Access passwords)
- Campaign and re-engagement communications
- Guest self-service privacy page links
Sender labelling — by default on Wiacom-owned registered domains, or with a custom sender name and reply-to address — is configurable per deployment.
SMS and messaging is available across a broad range of geographies. Wiacom supports major global SMS destinations as well as a number of regional carriers, making coverage available in most major markets. In addition to standard SMS, the following messaging channels are supported:
- RCS (Rich Communication Services)
- WhatsApp
Messaging delivery covers OTP / PIN for phone-based registration and credential delivery where a messaging channel is configured.
The list of supported destinations and geographies is extensive and restrictions may apply. Contact the Wiacom team to confirm coverage and channel availability for your target region before enabling phone registration flows.
Option 2 — Customer-Provided Services
Customers can connect their own email or SMS/RCS/WhatsApp delivery services instead of, or alongside, Wiacom default channels. This is supported through:
- API integration — connect any provider that exposes a standard delivery API
- Custom service integration — for customers operating their own internal email or messaging infrastructure
Wiacom already has integrations in place for a large number of major and regional providers. If you are using an established service, there is a good chance it is already supported — contact the Wiacom team to confirm.
When using customer-provided services, the customer is responsible for API credentials, delivery configuration, rate limits, and compliance obligations including sender identification and unsubscribe handling.
Billing
The platform is billing-ready. Messaging consumption is tracked per deployment and can be managed through prepaid (top-up) or postpaid arrangements. Payment gateway integration is available for deployments where monetised access or paid plan workflows are required. Billing configuration is handled at the account level by the Wiacom team. 
