An email notification is not a workflow.
A homeowner submits a service request, an email goes out, and from that moment the request exists only in whichever inboxes happened to receive it. Nobody owns it. Nothing shows it is still open. If the person who usually handles them is out, it waits — and the first anyone hears about it is the follow-up phone call asking why nobody responded.
Requests submitted through the customer portal land on a board instead. Each one has a state you can see across the whole queue, so an open request cannot quietly become a forgotten one. Existing requests that predated the board were backfilled onto it rather than left behind in email.
The portal side is the other half. A homeowner who has an active portal account shows as one on their customer record, so office staff know whether the person they are talking to can see their own history. Portal accounts are managed by your own team, scoped to your company, with a warning before an account tied to an open balance is removed.
What it does, point by point
- Portal-submitted requests land on a board with a visible state
- Requests that predated the board were backfilled, not abandoned
- Notifications open the request itself, not a general screen
- Active portal users are flagged on the customer record
- Portal accounts managed by your own team, scoped to your company
- A warning before removing an account attached to an open balance
- Receipts and visit records reachable from the same portal the request came from