Work Order Router
BetaReads each service request, routes it to the right team or vendor, and watches the SLA.
- Asks approval for
- Dispatching to an outside vendor.
Solutions · With REX
BetaCoordinate service requests.
A request comes in. REX reads it, sends it to the team or vendor that owns it, watches the clock, and tells the tenant when it is done.
How REX does it
The work, step by step.
-
01
Read the request
REX reads what the tenant wrote, the space it came from, and the history of that space.
-
02
Route it
It sends the request to the team that owns the category, or drafts the dispatch to the vendor for your approval.
-
03
Watch the clock
It tracks the SLA and nudges the owner before the deadline, not after.
-
04
Close the loop
When the work is marked done, it drafts the note back to the tenant.
The agents involved
Who does the work, and what it asks you first.
Every agent drafts, logs, and waits for approval before anything moves. The label says whether it runs today.
Answers
NowAnswers questions across the portfolio; every answer traces to its record.
- Asks approval for
- Nothing. Answers are read-only.
Where it works
Inside the products your team already opens.
An illustrative scenario
A tenant on 14 reports the AHU is loud. REX routes it to engineering, sees the same unit was serviced twice this quarter, attaches both tickets, and drafts a vendor dispatch for the chief engineer to approve.
More with REX
The other work REX takes on.
See REX do it on your building.
Bring a request queue, a booking calendar, or a rent roll. We'll show you what REX drafts, and what it asks you first.