Feedback on an edit rarely comes in organized: a voice note here, an email there, a comment on a story. The real cost isn't the number of notes, it's the time spent gathering them and guessing which exact timecode they point to.
One channel, set from the moment you deliver
Say where you want feedback the moment you send the edit, and hold that line. A client who knows where to reply won't scatter notes across three different channels out of habit.
The timecode, non-negotiable
A note with no precise timecode ("somewhere in the middle", "near the end") forces you to rewatch the whole edit just to understand it. Ask for an exact timecode every time, even if it's only rough to the second.
On xFer, the revision request happens right on the delivery page while the client watches the video, with the option to leave a voice note: the feedback arrives already in context, with no reconstruction on your end.
Batch it, don't work note by note
If several people sign off on the edit on the client's side, resist the urge to fix things the moment the first note lands. Wait for a single, coherent compilation, or you risk undoing one change to make another that contradicts it.
In short
One channel set in advance, a timecode every time, and feedback compiled before you touch it rather than handled note by note. The edit isn't any longer to fix, it's just faster to understand.