Service desk
One queue for staff, tenants, customers, engineers, and imported demand.
- Find requests and keep context in view
- Service shortlist for the agent to confirm
- Priority and routing on the record
Features
CAFM that changes with the work.
Rules your team can maintain, one auditable work record, and AI that stays under oversight when you use it — not another bolt-on chatbot or consultancy rewrite.
01Operating model
Four ideas, not forty modules.
The old CAFM pattern hid business rules inside custom objects, scripts, integrations, and consultancy change requests. AJAEX keeps the rules visible so the platform can move as the operation changes.
01
Model the work
Sites, spaces, assets, services, permits, documents, contractors, and requests sit on one live record model.
02
Define the controls
Teams configure statuses, SLAs, evidence rules, approvals, access, and escalation paths without burying logic in custom code.
03
Keep AI inside the rules
Where AI assists, it stays scoped to the record, the allowed capabilities, and rules your team approve — not a free chatbot.
04
Review and prove
Low-confidence or risky outcomes go to people. Every input, output, model, confidence score, route, and correction is retained.
02Platform capabilities
The important parts, grouped clearly.
Instead of listing every setting, the platform is easier to understand as eight connected capability groups.
Guided request intake
Start with who or where; structure the request before it enters the queue.
- Person- or place-first logging
- Structured read-back before submit
- Demonstration data in product captures
Assets and PPM
Estate, asset, schedule, job history, and compliance state connected.
- Site-to-asset hierarchy
- Planned maintenance schedules
- Asset-linked evidence
Permits and RAMS
High-risk work controlled by permit rules, evidence checks, and review gates.
- Permit-to-Work on the platform
- RAMS and method statements on the record
- Review before work starts
Documents and evidence
Documents become structured records instead of files people have to chase.
- Documents on the work record
- Certificate and due-date fields
- Linked to assets and jobs
Workflow and rules
Business logic stays visible, configurable, and auditable.
- Status-driven workflow
- Approval and segregation rules
- Notifications and handovers
Data and integrations
Bring legacy data in and push clean operational updates back out.
- CSV and API import paths
- Sync and integration hooks on the platform
- Reporting from live records
Despatch and routing
Assign field work with skills, windows, and day routes in mind.
- Skills and window-aware assignment
- Full-day route planning across jobs
- Less wasted drive time between visits
03Despatch
Plan the day, not just the next job.
Field teams get work assigned with skills, time windows, and routes in mind. The film shows the despatch capability we are building: planning a full day of visits instead of chasing the next ticket alone.
04Guided intake
Good service starts with context.
Guided request logging can start with who or where — person, place, then problem — with a structured read-back before the request enters the queue. The film is actual product UI with demonstration data.
05Service desk
Bring the work into focus.
Find a request in the queue and keep context beside it, then open the full record with status in view. The film is actual product capture with demonstration data — not a claim of live enterprise load or parity with another platform.
06AI suggestions
AI suggests. Your team decides.
Practical help at the service desk — AI can suggest options while human review stays in the flow. In the film, the AI workflow beat is labelled illustrative because that live task was unavailable; product screens use demonstration data.
Governed AI
AI with oversight, not a chatbot.
Users are not left chatting with a model. AJAEX loads the right record, context, rules, and response schema for the task. The AI checks the work, returns structured output, and the workflow decides whether it can proceed or needs human review.
Shortlist a request
The desk uses site, contract, location and available services to shortlist options. The agent confirms — nothing auto-applies without a person.
Process a certificate
Document handling can extract key fields and link evidence to assets or work. Low-confidence or unclear results stay with people for review.
Support a RAMS review
Method statements sit with the permit record so reviewers can check hazards, site rules and controls before work progresses.
AI transaction record
No memory. No broad API access. The record shows what was sent, what came back, and what happened next.
- 01Scope the record, user, site, and allowed capabilities.
- 02Load the approved rules for this exact action.
- 03Send bounded context to the selected AI capability.
- 04Store input, output, model, route, and confidence.
- 05Write back only through review, workflow, or approval controls.
Human oversight stays in the loop.
Low-confidence, incomplete, or risky outcomes can be stopped for review before they affect live records.
07Operation lines
Switch on what you run.
AJAEX covers the common CAFM backbone, then lets each customer switch on the lines that match their operational risk.
Facilities Management
Sites, buildings, spaces, assets, and work orders in one work record.
Planned Maintenance
Maintenance schedules, job cards, and asset health.
Asset & Estate Management
A full register over a hierarchical estate, site to asset.
Service Desk
One queue for every kind of request.
08Guardrails
The controls are part of the product.
Audit, access, residency, and AI transparency are not separate consultancy workstreams.
Audit trail
Every record, comment, document, status change, AI transaction, and correction has a traceable history.
AI transparency
Inputs, model, route, output, confidence, and review outcome are visible on the transaction record.
Data residency
Starter and Professional tiers run on AWS eu-west-2 (London). Enterprise can pin to a chosen AWS region.
Controlled access
Users only see the records, sites, services, and capabilities available to their role and context.
See the operating model on your scenarios.
Bring one messy workflow: a permit, inspection pack, contractor handoff, or service request. We will show how it becomes rules, transactions, review, and evidence.