Submitting feedback and tracking resolution
Last updated: June 21, 2026
Short answer
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 collection 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.
Focused articles
- Should every correction go through feedback?
- What happens after feedback is submitted?
- Can customers track whether feedback was actioned?
- What if the same issue affects many records?