← Back to Deployment Guide
Support · Troubleshooting · v1.0
Opportunity Insights
FAQ & Troubleshooting
Answers to the most common questions and issues that arise during Opportunity Insights deployment. Search by category or scan the full list.
Table shows zero rows
Most common cause: the filter combination is too restrictive for this customer's data. The Stalled Detection table filters for engagement < 50 AND zero meetings in 30 days — if the customer has limited data, try relaxing the engagement threshold. To test: remove all filters and re-run to verify the API returns data, then add filters back one at a time.
Script says "Not logged in"
The script checks your Backstory session. You must be on app.people.ai and logged in BEFORE running the script. Navigate to app.people.ai, verify you see the dashboard, then open DevTools and run the script.
Bookmarklet does nothing when clicked
Some browsers truncate long bookmark URLs. Use the console script instead — click "Show console script" and copy/paste into DevTools. Console scripts are recommended for all tables.
Table created but columns are empty
The metric may not be enabled for this customer's instance. OOTB metrics should all be available, but some require activity capture to have been running for at least 7 days. Check with Backstory support if core metrics like engagement_level show as blank.
I see duplicate tables
Each script run creates a new table. If you ran it twice, you'll have two. Delete the duplicate from EDB (Explore Data Builder) in Backstory.
Hidden Opportunity table shows opportunities instead of accounts
Make sure you ran the correct script (Table 3). This table is account-level, not opportunity-level. If it shows opportunities, you may have run one of the other table scripts by mistake.
Custom metric shows null/blank values
Custom FormulaMetrics take up to 24 hours to populate after creation. If still blank after 24 hours, verify the metric definition was saved correctly in the Admin Console.
Where do I create custom metrics?
Navigate to
Backstory Admin → Custom Metrics → Metric Builder. See the
Custom Metrics Guide for full JSON definitions.
Do I need custom metrics to use OI?
No. The 4 OOTB tables work without any custom metrics. Custom metrics power the 4 Enhanced tables (Tables 5-8) which add computed signals like email responsiveness ratio and stakeholder breadth.
Signal not appearing on opportunity records
Signals run on a schedule (2-3x per week). After activation, wait for the next scheduled run. Check SalesAI settings in Admin to verify the signal is active.
Signal output is generic or unhelpful
The signal quality depends on available activity data. Opportunities with very little activity will get less specific insights. Ensure the opportunity has at least 2 weeks of captured meetings and emails for meaningful analysis.
Can I customize which metrics the signal uses?
Yes. The signal prompt specifies which OOTB metrics to include as context. See the
SalesAI Signals Guide for the full prompt with all configurable metrics.
/oi command says "failed because the app did not respond"
Check that the n8n workflow is active and the webhook URL is correct. Common issue: another Slack app may have claimed the same slash command name. Try renaming the command.
Slack bot runs but nothing posts back
Check n8n execution logs for which node failed. Most common causes: Backstory auth token expired (re-check client_id/client_secret) or the response_url from Slack has expired (Slack URLs expire after 30 minutes).
Results take too long
The bot runs Claude AI analysis on each flagged deal, which takes 1-3 minutes. This is expected. Results are cached for the day, so subsequent runs are instant.
What data does Opportunity Insights use?
100% OOTB Backstory metrics — engagement level, meeting counts, email counts, days in stage, close dates, executive engagement. No custom fields, no org-specific fields, no SalesAI dependency for the base product.
Does this work for any Backstory customer?
Yes. All metrics use the ootb_ prefix and are core platform metrics available on every instance. The only requirement is that activity capture is running and engagement scores are populating.
How long does the full deployment take?
~15 minutes for the 4 OOTB tables + board. Add ~20 minutes if deploying custom metrics and enhanced tables. SalesAI signals are a separate ~20 minute configuration.