How Arqora handles public contact routes
A note on separating public contact paths for general messages, security, legal, support, and partnerships.
Quick Summary
Arqora separates public contact routes so different kinds of messages do not collapse into one inbox.
Clear addresses make security, legal, support, and partnership messages easier to triage.
The routing is simple today, but it leaves room for future ticketing and operational workflows.
Why separate routes
A single public inbox becomes messy quickly. Security reports, legal questions, general messages, and support requests all need different handling.
Arqora uses separate contact paths so the message type is visible before any automation exists.
Simple first layer
The first layer does not need to be complex. Clear addresses and predictable forwarding already improve how inbound messages are handled.
This also makes future systems easier to build because the routing intent is already reflected in the address structure.
Connection to CMP
Arqora CMP can later use these routes as input for tickets, labels, and workflows. The email address becomes a useful signal instead of just a destination.
Designing this early keeps operational work from becoming an afterthought.