Spaces

First-reply checklist for tenant and site fault reports

This checklist shows what the first reply to a tenant, site manager or contractor message should include, so a fault can be logged properly in one go. It is made for facilities teams and their AI agent.

Runs in your browser. Nothing you enter is sent anywhere or saved.

Before you start

Nearly every message a facilities team receives starts with something that is already wrong: a dead light, a jammed door, a pallet at the wrong dock. The sender wants to know that someone has heard them. A first reply that only says "we are looking into it" leaves you chasing the missing details all afternoon.

Read each point and tick the ones your team, or your AI agent, already covers. Every gap is a question that someone on your desk will have to ask later by phone. Pin the finished list near the helpdesk, or hand it to whoever sets up your agent.

Tick each one as you go. 0 of 10 done.

[ ] Say sorry for the problem in half a sentence, then move on.
[ ] Ask which building, floor and room or area it is.
[ ] Ask whether anyone is at risk right now.
[ ] Ask for a photo if the fault can be seen.
[ ] Ask what exactly is happening and since when.
[ ] Check whether it is yours to fix or the landlord or tenant to fix.
[ ] Give a ticket reference as soon as the job is logged.
[ ] State the normal response time for that kind of fault.
[ ] Ask for the best contact name and number on site.
[ ] Finish with what happens next and who will be in touch.

What a good fault reply looks like

Imagine a tenant writes that a corridor light keeps flickering. A strong reply reads: Sorry about that. Which building and floor is it, and is there any burning smell or sparking? Once you answer, I will log it and give you a ticket number.

It is short, it asks the two things a dispatcher needs, and it checks safety before anything else. Then a second message confirms the ticket and the target response time from your own service list.

Slips that slow down a helpdesk

These habits turn a five-minute job into a day of calls.

  • Logging "light broken, Building C" with no floor or photo.
  • Promising a visit time that the contractor has not agreed.
  • Skipping the safety question when the message sounds minor.
  • Replying only with a phone number and leaving the sender to start again.

FAQ

How many questions should the first reply ask?

Two or three at most. Location and safety come first, then a photo. Asking everything at once makes busy site staff give up and call your phone line instead.

Can the agent promise when an engineer will arrive?

It can quote your normal response target for that fault type, but it should not name an exact arrival time unless your rota or work-order system confirms it.

What if the sender will not give the floor or room?

Log what you have, mark the location as unconfirmed and ask once more later. A person on your team can phone the site contact if the fault looks urgent.

More free tools for facilities support teams

Read the guide: Answer site and tenant requests for facilities teams around the clock.