Skip to main content

Complaint Management Q&A Breakout (10/20/2026)

Originally recorded October 20, 2026 at the Kadince Virtual User Conference

Summary

In this Virtual User Conference Q&A breakout room, complaint management professionals brought their questions to the Kadince team and learned from each other along the way.



Key Takeaways

  • Good reporting starts with good intake. Use required fields, drop-downs instead of open text, and help text with examples on the fields that cause confusion. Customers shared that requiring more fields didn’t lower their submission numbers, and a quick quality review of call center complaints helped fill in missing details.

  • Collect everything, but route it differently. Minor complaints like branch decor can go straight to a branch manager through a workflow instead of compliance, and you can leave them out of your trend reports. You can also set up separate forms for different groups, like a public website form and a staff form, each with its own review process.

  • Use keyword workflows to escalate serious complaints. A workflow can check the description for words like “lawsuit” and send those complaints for extra review, even if the submitter didn’t flag them. For approvers who fall behind, New Task Engine can send overdue notifications, and task reports show who has overdue tasks.

  • Export a backup before any import or mass update. Kadince doesn’t have an undo button, so use the data tool to export your current records first. If something goes wrong, you can use that file to restore the records in bulk instead of fixing them one at a time.

  • Test changes safely in your live instance. Clone a form or workflow, label it as a test, and limit the test workflow to that form so it doesn’t affect real complaints. Getting feedback from a small group of the people who will fill out the form helps catch confusing fields early.


Related Content

Did this answer your question?