Skip to main content

Signals FAQ

Common questions about Signals — why they may not appear, sync timing, and how call-to-account matching works.

My Signals look stuck or haven't updated

The Detected tab only shows Signals that match an Account already imported into Cora. If Cora has been analyzing new activity but the companies involved aren't in your Accounts list, those Signals won't appear.

To fix this:

  • Broaden your CRM import filter (e.g., include Opportunity or SQL stages, not just Customer) so more companies become Accounts in Cora

  • Or manually add specific Accounts for companies you want tracked

New activity just happened but no Signal appeared yet

Data from connected sources (Gong, Gmail, Slack, etc.) can take anywhere from a few minutes to a few hours to become available, depending on the integration. Cora's detection then runs on a regular cycle after that. In most cases, expect new Signals to appear within a few hours of the underlying activity.

Activity with a known customer didn't generate a Signal

Cora matches activity to Accounts by checking whether the participants (call attendees, email recipients, Slack users, etc.) are linked to a company record in your CRM. If the contacts involved aren't associated with the correct company in HubSpot or Salesforce, the activity won't match — even if the company itself is already an Account in Cora.

To fix this, associate the relevant contacts with the company record in your CRM. Future activity involving those participants will then match automatically.

Why does Cora use contact-based matching instead of domain matching?

We've seen many CRM setups where company domains are incorrect, or participants use personal or mismatched email addresses. Matching via contact-to-company associations in your CRM is the most reliable way to attribute activity to the right customer.

Did this answer your question?