RELATED IDEAS
Make contact email optional for feedback automation rules
What is the challenge?
Today, the new automation-based feedback collector requires that the contact email is passed through the webhook. Without this, feedback will not be created.
What is the impact?
For teams aggregating feedback for multiple sources, or teams not heavily relying on the contact record in Aha!, this can be an unneeded extra step.
Proxy votes in Aha! today can be added without a contact listed, though the organization is required. It should be optional to pass the contact through the automation as well.
Describe your idea.
Set the automation rules to review and add contact details if they are provided, but do not make this required.
-
-
- +1
© 2026 Aha! Labs Inc.•All rights reserved
I assume the email address was made required so feedback can be tied to a contact, which can then be associated with an organization for proxy voting. However, this dependency on contact email makes the feedback automation rules unusable for us in their current form.
Our organizations are created in Aha! through a Salesforce integration, where the unique Salesforce Account ID is passed through. We do not maintain email domains as a separate field in either Aha! or Salesforce because they are not reliable unique identifiers. For example, different departments within the same company may have separate customer accounts with us.
It would be much more helpful if feedback automation rules could accept other unique organization identifiers, such as the Aha! reference ID or, in the case of Salesforce integrations, the Salesforce Account ID. This could still support proxy voting while creating a much more streamlined and reliable identification process, rather than requiring Aha! to infer a match based on email domain. That is especially important in cases where multiple organizations may share the same email domain.