Concerns

Client concerns tracked to resolution, not lost in texts

The complaint you lose is the client you lose. Concerns give every complaint a record, an assignee, and a state, link it to the visit and its photos, and make the resolution touch billing and scheduling correctly.

The complaint has a home now

The concerns queue shows what is open, who owns it, and how long it has been waiting. The owner sees the same list, so accountability is built in.

  • Proof is one tap away. The linked visit carries the before and after photos that settle most disputes.
  • The fix is real. Credits and redo visits happen in billing and scheduling, from the concern itself.

Everything in concerns

One queue for every complaint

Missed area, gate left open, billing question. However it arrives, it becomes a concern with an owner-visible state instead of a text that scrolls away.

Linked to the visit and its photos

A concern attaches to the specific visit, so the completion photos are right there. Most missed-yard calls end at the photo.

Assigned, worked, resolved

Every concern has an assignee and a state. The owner dashboard flags anything open, so nothing quietly ages out.

Resolutions that touch billing correctly

If the resolution is a credit or a redo visit, it happens through billing and scheduling directly from the concern, not as a side promise.

Patterns you can act on

Concerns per tech, per zone, and per reason feed reporting. Three gate complaints on one route is a coaching conversation, not a coincidence.

The blog has the script

How to handle the missed-yard call calmly and keep it from repeating is written up on the blog, from the operators who take these calls.

Put it on a truck this week

HoundStack is available now. Start today with a 14 day free trial, no credit card, and your first 3 teammates included.

14 day free trial · No credit card · Cancel anytime