Messaging policy

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.

Allowed use cases

What HexaVox is meant to send

One-time passwords, verification links, password resets, and account access messages. Appointment confirmations, reminders, workflow updates, and operational notifications. Customer support replies, case updates, callback follow-up, voicemail notices, and service coordination. Messages triggered by authenticated application activity or authorized tenant workflows.
Recipient sourcing

How recipient addresses and numbers must be collected

Recipients should be first-party users, customers, or contacts obtained through direct business relationships and real service interactions. Authorized tenant users may enter recipients when the communication is necessary for service delivery or customer support. HexaVox is not intended for purchased, rented, harvested, or scraped recipient lists.
NO

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.

OP

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.

AU

Auditability

HexaVox is structured so domain setup, mailbox access, API keys, tenant administration, and workflow controls can be explained and operated with accountable ownership.

Platform posture

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.

Questions about this policy or a specific messaging workflow can be directed through the HexaVox team using the details on the contact page.