Remote contractors/hires lack basic async communication etiquette, forcing managers into constant hand-holding or firing them

Summary

Managers of remote/distributed workers are burning significant time on a problem that has nothing to do with skills or output: the person simply never learned how to communicate in a remote environment. They post DM-only content in public channels, open DMs with a bare "Hi." and no actual question, send redundant 'reminder' pings days after an agreed deadline (even screenshotting the agreement to prove it), and generally create a stream of low-signal interruptions. The manager's only options today are to ignore the messages, correct the behavior case-by-case forever, or replace an otherwise cheap, reliable, competent worker — a real loss. Crucially, this is NOT solved by Slack/Teams, which provide zero norms enforcement, zero onboarding on how this specific team communicates, and zero feedback loop for the offender. There is no lightweight product that (a) onboards a new remote contractor onto a team's communication protocol (where to post, what a complete message looks like, when to follow up and how often), (b) passively flags channel/DM misuse or content-free pings at the point of sending, and (c) gives the manager a non-confrontational, automated way to correct it instead of hand-holding. Existing 'team handbook' docs are static, unenforced, and never read. The pain scales directly with how distributed and async the team is, and it silently erodes the manager's willingness to keep good remote talent.