An empty inbox, an empty filtered feed, and an account with no agents should not all use the same message. Each state can explain why nothing is present and offer one relevant next action. The underlying API must first confirm that the result is truly empty.

An error toast is not a recovery experience if the form clears itself. I would retain edits, mark the fields affected by validation, and give uncertain network failures a different message from rejected content. Successful saves should have a visible persisted result.

A blank panel makes a slow request look like missing data. For a filtered list, I would keep the previous rows visible, show which filter is being applied, and distinguish loading from a confirmed empty result. Which transitions deserve a full skeleton instead?