A reply is not a resolution.

The speed metric that masks operational failure

A coordinator replies within twelve minutes: "Thank you for contacting us, we are looking into this." The inbox dashboard marks it "responded." But the water heater is still dripping, the vendor hasn't been dispatched, and no committed update time exists.

The disappearing act

Because a reply went out, the message leaves the primary queue. The coordinator assumes the property manager approved the bid; the manager assumes the vendor scheduled the visit; the vendor assumes someone will call back. Three days later, the client emails in anger, pulling leadership into rescue mode.

The operational standard

A reply sits at Message. Resolution only occurs at Close. Every message requiring work must establish two states: a fast communication touch, and an active commitment with one named owner, an exact next action, and a promised update time.

The Five "Handled" Audit

At your next standup, pull up five threads from yesterday marked "Handled" or "Closed." For each, ask:

1. Was work required after the reply?
2. Who was explicitly assigned to complete it?
3. Did the client know exactly when to expect the next update?
4. Is there verifiable proof in AppFolio or email that the loop closed?
5. Did anyone have to send a second "checking in" message?

Find your team’s next move.

If your team struggles with the gap between answering messages and closing loops, diagnose it in four quick questions.

External replies require human review.