Structured request
A need, location, priority, and customer context.
Industry solutions
Organise the request, appointment, delivery, and collection
The services package brings together request, customer, location, appointment, owner, delivery result, and collection so work is not lost across calls, messages, and separate schedules.
ARMADATurn scattered calls into owned work
Clear scheduling
A team, time, and state that can be followed.
Recorded result
A known completion or exception before collection.
Applications that complete the service journey
Service Operations
Request, location, appointment, owner, state, and delivery result.
Sales
Proposal, order, and commercial lines connected to the requested service.
Accounting
A collection document and financial effect tied to delivered work.
Reports
Read requests, appointments, delivery, and exceptions by branch and team.
The service journey from request to collection
- 1
Receive
Capture the request without losing context.
- 2
Assign
Set an owner, time, and priority.
- 3
Deliver
Update work through an authorised person.
- 4
Collect
Connect the result to its commercial document.
Data and responsibility that prevent lost requests
Customer context
Customer, location, service, priority, appointment, and necessary notes.
Work owner
Team, technician, follow-up owner, and clear authority for each transition.
Reviewable result
Completion, exception, or revisit with a reason, time, and owner.
Configure service around the way you work
- 1
Map request types
Services, areas, priorities, time windows, contracts, and roles.
- 2
Confirm assignment rules
Who receives the request, how time is set, and when an exception escalates.
- 3
Test the full day
Receive, assign, postpone, complete, revisit, and collect.
- 4
Train and hand over
Train office, field, and management teams on the same operating cycle.
Frequently asked questions
Clear answers before you decide
Does it cover both on-site and field work?
The scope is defined by service locations, roles, required devices, and state updates. Office and field journeys are then tested together.
How are recurring services handled?
Contract cycle, appointments, recurrence, assignment ownership, and collection are stated in the proposal so recurring service does not become unowned work.
What happens when a technician cannot complete the work?
The exception, reason, and time are recorded. The request then follows a known rule for rescheduling, escalation, or cancellation.