profile backed feedback
profile backed feedback ties each useful highlight to evidence from the voice profile, writing samples, and learned lessons instead of treating the draft as generic text.
quick answer
use this when a user asks why the app knows a line does or does not sound like them.
use this for
- explaining evidence behind a highlight
- debugging weak feedback
- teaching agents how to cite the profile instead of guessing
steps
- open a document with a saved profile.
- run a voice check.
- open the highlighted line or feedback card.
- read the source detail beside the signal.
- edit the profile or add samples if the evidence is thin.
details to know
- feedback can come from profile text, saved samples, and accepted lessons.
- stronger profile readiness gives the app more concrete evidence to compare against.
- green feedback matters too because it shows what the draft should keep.
limits and edge cases
- generic profile text creates generic explanations.
- agents should not invent profile evidence that is not present in the response.
- if evidence is weak, the right action is to improve the profile, not argue with the highlight.
ready to use the product instead of reading about it?
open app