HexaVox is built for transactional and operational communication.
This policy explains how HexaVox expects its messaging workflows to be used, where recipients come from, what message types are supported, and which practices are prohibited.
How recipient addresses and numbers must be collected
Prohibited behavior
HexaVox should not be used for unsolicited bulk promotions, lead-list blasting, deceptive traffic generation, phishing, malware delivery, or any workflow that intentionally hides sender identity or consent status.
Opt-out and suppression
Where message type requires opt-out support, tenants are expected to honor it. Invalid recipients, hard bounces, and complaint-driven suppressions should not continue to receive traffic.
Auditability
HexaVox is structured so domain setup, mailbox access, API keys, tenant administration, and workflow controls can be explained and operated with accountable ownership.
HexaVox takes a quality-over-volume approach.
The product is built for real customer communication: service flows, authentication, reminders, support, routing, and follow-up. That posture is reflected in our public site, application, domain setup guidance, and messaging policy.