Built to run reliably, and built to answer for how it runs.
One platform sits behind every channel and Solution on Horizon Dit. This page explains what that means for how it is built and how it is operated, then points to the two pages that cover each in full.
Two different questions sit behind the word trust for an enterprise buyer. Can the platform hold up as volume grows. Is it operated in a way that stays accountable, with the access and records to prove it. Horizon Dit answers each on its own page, built for exactly that question.
Infrastructure
The architecture behind every send lives here: how the platform is architected to handle growth, and how its own team keeps watch while it runs.
Responsible messaging is covered here too, from a different angle: the personal data involved, the basis for sending, and the access and records that keep it accountable across the markets Horizon Dit operates in.
Five platform capabilities sit behind what Infrastructure and Compliance each describe from their own angle.
01
Role-Based Access
Access can be scoped by role, so a team only sees or manages what its work actually requires.
02
Messaging History
What was sent, and when, is kept as a record rather than pieced together after the fact.
03
Delivery Records
Delivery status – delivered, failed or pending – is tracked and stays available to look up, rather than needing to be reconstructed from memory.
04
Account Activity Logging
Account activity can be logged, so actions are traceable back to a specific user rather than left to memory, where an account's setup supports it.
05
Traffic Monitoring
Messaging traffic is monitored for unusual or abusive sending patterns.
[Across the Platform]
Not Limited to This Page
Infrastructure and Compliance each connect to the rest of what Horizon Dit runs, not just to each other.
Solutions
Omnichannel Messaging, Smart Routing and Customer Verification are each built on the infrastructure Infrastructure describes.
Channels
Each channel Horizon Dit supports has its own page, since not everything described here applies to every channel in exactly the same way.
Developers
The access and reporting capabilities described here are also reachable through Horizon Dit's API, covered in full under Developers.
[FAQ]
Frequently Asked Questions
They answer separate questions about the same platform. Infrastructure explains what keeps messaging running reliably as it scales. Compliance explains what keeps it accountable once it is running. Each one is covered in full on its own page.
Role-based access, delivery visibility, account activity logging and traffic monitoring together make up what keeps the platform accountable day to day. Infrastructure and Compliance each go into a different half of that in more detail.
Not identically. The capabilities described here are part of the shared platform, but how something like sender identification or consent applies can differ by channel. Each channel's own page covers the specifics.
[See It in Practice]
The Next Step Depends on Your Question
Infrastructure and Compliance go into the detail. For a specific requirement, an active security review, or a question that lands between the two, our team can walk through it directly.
Enter your email address to receive a new password.
Please check your email inbox
Contact Sales
Get expert guidance on channels, setup, and messaging strategy.
This website uses cookies
We use necessary cookies to make our website and web-based interface work. To get more information about these cookies, how and why we use them and how you can change your settings, check our Cookie Preferences.
