Tenant Request Triage

Challenges Tenant Request Triage addresses

Done by hand, tenant services means gathering inbound tenant request, working through 5 separate passes over the same material, then producing classification, assessment and risks and obligations. None of it is difficult and all of it is exacting, which is the combination people are worst at holding. The errors that matter are the ones a tired reader does not notice, and they surface later — in a reconciliation, or in somebody’s reply. It starts whenever something arrives, which means someone has to be watching for it to start at all. As volume grows the work does not get harder, only longer, and the first thing to go is the checking.

Tenant Request Triage runs that same sequence end to end and returns the result as structured artefacts. What it cannot settle it hands over rather than guesses at, and your correction is kept: it asks “Would you have raised this the same way?” after every run, and those answers become the set it is measured against. Nothing that moves money, alters a contract or reaches a customer executes without human approval, and every action is written to an audit log. The gain is in the volume that no longer has to be read, not in removing the judgement.

How it works

Step 1: Classifying the request

First of 5. It works from inbound tenant request and feeds the step after it.

Key Tasks:

• Reading each item on its own terms: Classification is from the content rather than from a keyword list, so items phrased in a way nobody anticipated still reach the right tenant services bucket.
• Applying the same boundaries every time: The definitions do not drift between runs, which is what makes a count from this month comparable to one from last.
• Keeping the confidence: A borderline item is assigned with its confidence recorded rather than filed away as certain.

Outcome:

• Confidently classified: The item is grouped and counted, and moves on without review.
• Below the confidence threshold: It is held for a person rather than placed in the closest bucket — the wrong bucket is worse than an unfilled one, because it disappears into a count.

Step 2: Checking the service standards

Step 2 of 5. It takes what step 1 produced and hands its result to step 3.

Key Tasks:

• Running the checks in order: Every rule for tenant services is applied to every record, in the same order each run. A record is not skipped because it looks routine.
• Recording evidence, not verdicts: Each check stores what was expected and what was found, so a failure can be understood without re-running anything.
• Separating clear from unclear: A check the agent cannot settle is marked unresolved rather than passed, which keeps "checked" meaning checked.

Outcome:

• All checks pass: The record clears with its evidence attached, available if anyone asks later.
• A check fails: The record is held with the failing checks named and the rest shown as passed, so a reviewer sees the scope of the problem rather than only that there is one.

Step 3: Deciding how to respond

Step 3 of 5. It takes what step 2 produced and hands its result to step 4.

Key Tasks:

• Working from the run so far: This step takes what step 2 produced and carries it toward step 4.
• Following the same rules each time: The behaviour is configuration rather than judgement made fresh per run, so tenant services is handled the same way every time.
• Surfacing what it cannot settle: Anything ambiguous is passed on as ambiguous rather than resolved silently.

Outcome:

• Passed on: The result passes to the next step, with anything unresolved carried forward as an open item rather than dropped.

Step 4: Preparing the reply for approval

Step 4 of 5. It takes what step 3 produced and hands its result to step 5.

Key Tasks:

• Writing from the run, not from a template: The text is built from what this run actually found, so two tenant services outputs differ where the underlying records differ.
• Leading with what needs a decision: The exceptions come first and the routine detail follows, because the reader is deciding rather than reading.
• Staying inside the evidence: Nothing appears in the text that is not supported by a record the run examined. Gaps are stated as gaps.

Outcome:

• Draft ready: It is held for approval. Nothing reaches a customer, a calendar or a channel until a person releases it.
• Not enough to write from: It says so instead of producing something plausible from thin evidence, which is the failure that is hardest to catch on review.

Step 5: Building the work order

Last of 5. It takes what step 4 produced and produces classification and assessment.

Key Tasks:

• Producing the work order: What this step assembles is the work order, in the form the reader actually uses it in rather than as a general summary of the run.
• Keeping it traceable: Each claim stays linked to the record behind it, so a reviewer can check a line instead of accepting the whole.
• Writing from the run, not from a template: The text is built from what this run actually found, so two tenant services outputs differ where the underlying records differ.

Outcome:

• Held for release: It is complete and waiting on a person. Nothing reaches a customer, a calendar or a channel until someone approves it.
• Insufficient evidence: It says so rather than assembling something plausible from thin material, which is the failure hardest to catch on review.

Step 6: Your review, and what it changes

The run ends with a person, not with a result being filed.

Key Tasks:

• Asking a specific question: It asks “Would you have raised this the same way?” rather than for a rating. A question about this run is answerable; a score out of five is not.
• Keeping the correction: What you change is recorded against the case that produced it, so the disagreement is retrievable rather than absorbed.
• Building the evaluation set: Those cases become what the agent is measured on. It is scored against your judgement rather than against a general benchmark.

Outcome:

• A measured agent, not an assumed one: The cases Tenant Request Triage handles well and the cases it does not are both visible, and the second list is the one that decides what changes. Nothing is retrained silently on the back of a single correction.

Why use Tenant Request Triage?

• Answers from your own material: It retrieves from a knowledge base you populate — your policies, contracts and reference documents — so its decisions follow how your business actually operates rather than a general model’s assumptions. Sources are cited alongside the result.
• Nothing leaves without approval: Draft reply is drafted and held. A person releases them, so the agent's reach ends at your own review step.
• Every statement cites its source: Findings come back with the records behind them, so a reviewer can check a claim instead of deciding whether to trust it. An assertion with no source is the expensive kind to discover late.
• Machine-readable for whatever comes next: One of the artefacts is a structured payload, so this agent can sit in the middle of a pipeline rather than only at the end of one.
• Works from the message itself: The body and its attachments are the input, so a request does not have to be transcribed into a form before anything can happen to it.