Surface competitive deal tips from Gong calls into Slack and Salesforce

Create the trigger types that should create guidance, silent logging, or escalation. Include direct competitor mention, pricing objection, feature comparison, security concern, migration concern, incumbent renewal, procurement pushback, discount request, buyer confusion, and roadmap comparison. Map each trigger to severity, sales stage relevance, owner, approved guidance source, and whether the rep should receive a Slack alert. Add examples of phrases that should and should not trigger an alert so the system does not flood reps with low-value mentions. This taxonomy is the control layer that keeps the engine useful instead of noisy.

Create a competitive trigger taxonomy.

Competitors:
{{competitors}}

Sales process:
{{sales_process}}

Current battlecard topics:
{{battlecard_topics}}

Deal stages:
{{deal_stages}}

Output:
1. Trigger type
2. Example buyer language
3. False-positive phrases to ignore
4. Severity
5. Sales stage relevance
6. Alert, silent log, or escalation rule
7. Guidance source
8. Owner
9. Review frequency

Optimize for useful alerts, not maximum alerts.

Set up Gong keyword or smart trackers for competitor names, common misspellings, product names, pricing phrases, procurement language, and feature comparison terms. Connect each detected signal to Salesforce context such as opportunity owner, stage, amount, close date, competitor field, industry, segment, and next meeting date. Use Zapier or your internal integration layer to move only relevant trigger events into the workflow. Add a QA sample of recent calls to check whether the trackers are catching real signals without overfiring. Tune the trigger rules before sending alerts to sales because a bad first week will hurt adoption.