Client approval right next to the conversation
Axis is where your team and your clients approve content, chat, open tickets and exchange files — with the history of every decision preserved. On the web and in the native Android and iOS app.
Web and native Android and iOS app · Included with any Centriu subscription
Why Axis
The client relationship is scattered everywhere
Approval on one channel, changes on another, the file on a third — and the decision with no record of who approved what. Axis brings conversation, approval, tickets and files together in one place, with roles defining who creates, approves and sees each item.
Conversation far from the work
The request comes in one way, the item is somewhere else, and the agreement gets lost in between. In Axis, the conversation sits right next to the request it resolves.
Approval with no trail
With no record of who approved, when and with what caveat, every version becomes a doubt. Axis keeps the client decision with author and date.
Everyone seeing what they should not
The client takes part in approvals, conversations, tickets and files without accessing internal operations — each role sees only what belongs to it.
Features
What the client relationship needs, in a single app
From approval to reporting, with communication always right next to the work — on desktop and on mobile.
Client approval
The client approves or rejects with a reason. The decision syncs the task in Run and notifies the service team — Axis is the external approval channel for Run and Atlas.
Real-time chat
Direct messages, groups and support, with text, image, video, audio and document, mentions and scheduled messages — the conversation right next to the work.
Tickets in two flows
Requests from the client to the team and from the team to Centriu support, with category, priority, status, owner, history and attachments.
File hub
Images, videos and documents organized in folders, by client and by organization, right next to the conversation that started them.
Notifications and push
A unified notification center with push delivery on the web and in the app, and an unread counter, so the team and the client can follow what changes.
Reports
Approvals, tickets and response time brought together in reports that aggregate Run and Atlas, with a team view and a client view.
In action
How a client approval happens
An illustrative example of the flow — the client decision is the control point. No real client, message or document.
From request to completion, step by step
IllustrativeRequest logged
The team logs the client item or request in Axis, right next to the conversation.
Conversation linked
The conversation with the client and the team stays attached to the request it resolves.
File sent
The item goes to the client for approval, with the preview next to the conversation.
Owner notified
Whoever needs to decide receives the alert in the Notification Center and by push.
Client reviews and decides
The client approves or requests changes with a reason — this is the decision control point.
History preserved
Every decision is recorded, with who decided and when.
Completion recorded
The request is completed and the decision returns to the source system — Run or Atlas.
Flow: the request is logged; the conversation is linked; the file is sent for approval; the owner is notified; the client reviews and approves or requests changes with a reason; the history is preserved; completion is recorded and returns to the source system.
Checkpoint
Logging lead outcomes, inside Axis
Checkpoint is the space where salespeople log, by hand, what happened with each lead they handled — the source the client themselves stated, the outcome and the notes. It is manual logging, done by whoever handles the lead.
Manual source logging
The salesperson notes the source the client stated during the contact and the notes from it, with no automatic capture.
Outcome tracking
Each lead gets a status — converted, lost or no response — to track the outcome of the contact.
Isolated per client, Salesperson role
The Salesperson role sees only Checkpoint, and each client company salesperson sees only their own records, isolated per client.
Checkpoint is manual logging: it does no automatic capture, does not track app messages, and uses no external QR Code or tracking scripts. The salesperson is the one who logs it.
For agencies and teams that serve clients
The agency serves the whole client through Axis
Bring conversations together, organize groups, open tickets, request approvals, receive changes and send files — with the history preserved and without mixing one client data with another.
Conversations and groups together
Direct messages, groups per client and a support channel in one place, right next to the work.
Approvals and changes
Request the client approval and receive the change with a reason, with the decision recorded.
Tickets with history
Open and follow requests from the client and the team, with priority, owner and history.
Files and notifications
Send files organized per client and follow the notifications of what changes.
You operate with your brand up front, on top of Centriu technology — "Centriu technology operated by your agency". It is not full white-label, and the Centriu presence is preserved.
Built for
Ecosystem
Where the other systems talk to the client
Axis is the inbox through which Atlas, Run and Axiom bring the alert to the client. These are the connections confirmed in code today; below, when to use Axis and not another system.
Atlas → Axis
When an Atlas deliverable goes for approval, the client is alerted in the Axis inbox and by push. Internal review happens in Atlas; the client approval, in Axis.
Learn moreConfirmed integrationRun → Axis
An item from Run sent for approval alerts the client in Axis, and the decision returns to Run. Production belongs to Run; client approval belongs to Axis.
Learn moreConfirmed integrationAxiom → Axis
When the Axiom AI needs to alert the client, the alert arrives through the Axis inbox, with push. The conversation with the client stays in Axis.
Learn moreAxis × Link
Link handles conversations from external channels with the public; Axis is the operational relationship and approval with the agency client. Axis is not an omnichannel inbox.
Axis × Run
Run handles the tasks and internal production; Axis takes the item to the client for approval and returns the decision. Use both together, each in its role.
Axis × Orbit
Orbit is the sales pipeline; Axis is the operational relationship and deliveries with the client. Axis is not a CRM or a sales hub.
The integrations above are the ones confirmed in code today. The systems share the same account and the same access, but they do not exchange data automatically among themselves — each integration is specific. The comparisons are not integration: they show when to use Axis and when to use the other system. If your operation depends on another connection, talk to us before subscribing.
How Axis reaches you
Included with any Centriu subscription
Axis is free and comes included with any Centriu subscription, at no extra cost and with no paid plans. There is no price table to choose — subscribe to any system and Axis is already part of it, for your team and your clients.
No extra cost
Free and included with any Centriu subscription. There are no paid plans and no usage charges.
Web and native app
Access through the browser and a native app for Android and iOS, with push notifications.
Roles per profile
Admin, Manager, Executor, Client and Salesperson — each role sees and does only what belongs to it in the operation.
Questions
Frequently asked questions
What is Centriu Axis?
It is the operational environment where your team and your clients communicate, approve content, open tickets and exchange files. It brings together client approval, real-time chat, tickets, the file hub, the notification center with push, reports and Checkpoint — on the web and in the native Android and iOS app. It is free and included with any Centriu subscription.
How does client approval work?
The item is sent to the client, who reviews it and approves or requests changes with a reason. The decision is recorded with author and date and returns to the source system — the task in Run changes stage, for example. Axis is the external approval channel for Run and Atlas; internal review happens in those systems, and the client decision, in Axis.
Does Axis have a mobile app?
It does. In addition to browser access, there is a native app for Android and iOS, with a unified notification center and push delivery. Notification delivery depends on each device and system, so Axis alerts you, but we do not promise guaranteed delivery on every platform.
What is Checkpoint?
It is a feature inside Axis where salespeople log, by hand, the outcome of each lead they handled: the source the client stated, the outcome (converted, lost or no response) and notes. It is manual logging — it does no automatic capture and does not track messages. The Salesperson role sees only Checkpoint, and each client-company salesperson sees only their own records, isolated per client.
How much does Axis cost?
Nothing on the side. Axis is free: it comes included with any Centriu subscription, at no extra cost. There are no paid plans and no usage charges. Subscribe to any system and Axis is already part of the package, for your team and your clients.
Does Axis replace the Client Dashboard, a CRM or WhatsApp?
No. Axis is the communication and operational approval with your clients. The platform contract, the plan and the invoices stay in the Client Dashboard — Axis does not replace that panel. And it is not a CRM, an omnichannel inbox, a support desk or WhatsApp: for the sales pipeline there is Orbit; for external channels with the public, Link.
Client approval and the conversation, in one place
See Axis in your client operation: approval, chat, tickets, files and notifications on the web and in the app — free and included with any Centriu subscription.