Product / Task routing
The right department gets it. Without a phone call.
Routing rules map each type of request to a department, a priority and a deadline.
“A pillow please, and the tap in 407 is dripping.”
HOUSEKEEPING
Room 407 · Extra pillow
SLA 10 min (example)
MAINTENANCE
Room 407 · Dripping tap
SLA 15 min (example)
Simulated product UI. Sample data, not customer results.
The problem
Front-desk staff act as human routers, relaying requests by phone and radio. Some get lost on the way.
How Atithi solves it
Atithi reads the request, identifies the department and creates the task there directly, with a timer already running.
Key capabilities
What it does.
Department identification
Housekeeping, maintenance, dining, front desk and more.
Configurable rules
You define the departments and mapping.
Priority and deadline
Each task starts with a target time.
Assignment
Tasks land in the department workspace.
Reassignment
Staff can move a task when it was misrouted.
Routing history
Every routing decision is recorded.
Operational workflow
How a request moves.
- 01
Request understood
- 02
Department identified
- 03
Task created
- 04
Deadline set
- 05
Task appears in workspace
- 06
Completion recorded
Hotel use case
A mixed message
A guest asks for a pillow and reports a dripping tap. Atithi creates two tasks, one for each department.
Illustrative scenario, not a customer case study.
Related Atithi capabilities
Works with the rest of the loop.
FAQ
Task routing: questions
Can we define our own departments?
Yes. Departments and routing rules are configured during onboarding.
What if a task is routed wrongly?
Staff can reassign it and the change is logged.
A better way to care for every request
See Atithi on your property.
A walkthrough built around your departments, your timings and your escalation rules.
Illustrative hotel workflowFrom a guest request to the right team
- 01 Guest asks
- 02 Atithi routes
- 03 Team responds