Arqora CMP as an operational system
An experiment note on shaping Arqora CMP around inbound messages, ticket history, and operational control.
Quick Summary
Arqora CMP is being explored as a practical system for handling inbound communication and support workflows.
The important parts are tickets, message history, reply state, routing, and auditability.
The project is still experimental, so the design favors clarity over feature volume.
What CMP means here
In Arqora, CMP is not only a customer table. It is an operational layer for handling messages, tickets, replies, and workflow state.
The system needs to make inbound communication easier to track without becoming too large too early.
Core workflow
A useful first version needs ticket IDs, message threads, contact context, reply records, and basic status changes. These pieces create enough structure for real use.
More advanced features can come later, but the foundation should already respect ownership and history.
Why it is still an experiment
The project is still discovering the right product shape. Calling it experimental keeps the scope honest while the workflow is being tested.
That also makes it easier to remove weak ideas and keep only the parts that make the system clearer.