Submitting feedback and tracking resolution
Last updated: June 22, 2026
Use feedback for data corrections. Use support for broken workflows, access issues, failed syncs, or urgent production blockers.
Good feedback includes the account, field, current value, expected value, and evidence.
Use this section when
A customer wants to correct a Kernel value.
Feedback status or outcome is unclear.
The same issue appears across many records.
A team is deciding whether to use feedback or support.