Forecast filed Thursday. Wrong by Monday.
Stage updates rely on rep confidence, not the call, the tickets, or the activity history. The forecast is a guess.
One prompt queries your Salesforce pipeline, Gong call sentiment, and Zendesk support health as a single connected dataset. Every deal risk-scored. Every gap surfaced. Your Monday forecast, done before coffee.
Pipeline reviews run on incomplete data because the signals you need are scattered across Salesforce, Gong, and Zendesk.
Stage updates rely on rep confidence, not the call, the tickets, or the activity history. The forecast is a guess.
Salesforce stage and Gong call sentiment never compare. The last call has the truth — and it's locked in another tool.
Ticket spikes and CSAT drops live in Zendesk. The CRM account stays "Green" until the renewal is already gone.
Under The Hood
stage · amount · close date · last activity · owner
buyer sentiment · competitor mentions · next steps · economic buyer
open count · CSAT score · unresolved escalations
Every deal scored 1–10. Top three risks called out. Suggested next actions per deal.
The Context Store
Airbyte connects Salesforce, Gong, and Zendesk Support into the Context Store — a unified data layer where account IDs and structures are already matched.
Your agent queries one surface instead of three APIs. Faster responses, lower cost per query, and results that work because the relationships were built before you asked the question.
The Prompt
Two steps. Your data, your results, under 60 seconds.
I want to run a pipeline review that combines CRM, call, and support data.
SETUP
You have access to the Airbyte Agent MCP, which connects to 50+ SaaS tools and lets you query live business data through natural language.
Workflow: List available connectors > connect to Salesforce, Gong, and Zendesk > explore schemas > query and cross-reference data > analyze and deliver.
If a connector isn't linked yet, the error is self-descriptive. Follow the auth flow, then retry.
TASK: Weekly Pipeline Review Brief
Likely connectors: Salesforce, Gong, Zendesk Support.
Steps:
1. Connect to Salesforce, Gong, and Zendesk Support
2. Pull all open Opportunities closing this month from Salesforce with stage, amount, owner, close date, and last activity date
3. For each deal, find the latest Gong calls from the last 30 days. Extract: buyer sentiment, competitor mentions, whether next steps were confirmed, and if the economic buyer was on the call
4. For each deal's account, pull Zendesk tickets from the last 90 days. Calculate: open ticket count, average CSAT, and any unresolved escalations
5. Score each deal's true close probability by combining:
- CRM signals (stage, activity recency, days in stage)
- Call signals (sentiment, buyer engagement, next steps)
- Support signals (ticket volume, CSAT, escalations)
6. Flag deals where CRM stage confidence doesn't match call or support reality
7. For each at-risk deal, recommend a specific next action
8. Output a pipeline review brief: risk-ranked deal list, total pipeline at risk, and a summary I can use to run the forecast meeting
Ask me before any action that sends messages or modifies data in a connected app.The Outcome
10x
Your agent queries pre-joined data instead of making live API calls to three tools. What used to take minutes takes seconds.
90%
Pre-built data joins mean your agent uses fewer calls and less compute per query. More agents, same budget.
3 → 1
No API orchestration, no retry logic, no rate limits. The Context Store handles the complexity so your prompt stays simple.
Based on internal benchmarks comparing Context Store queries to sequential API calls across equivalent datasets.
01 · Output
Every open deal scored on CRM stage, call sentiment, and support health. Not what the rep entered. What the data says.
02 · signal
Deals where the stage tells one story but Gong calls and Zendesk tickets tell another. The gaps your forecast never catches.
03 · context
Support ticket volume, CSAT trends, and open escalations layered onto every deal. The renewal risk your AE can't see from the CRM.
04 · action
A specific recommendation for each at-risk deal: schedule a call, loop in an exec, address open tickets, or re-qualify.
05 · summary
A summary formatted to run your pipeline meeting: total pipeline, pipeline at risk, and the 5 deals that need discussion today.
How do I build a pipeline review agent with Salesforce and Gong?
What Salesforce data does the agent access?
Can I combine Salesforce, Gong, and Zendesk data in one query?
How is this different from using the Salesforce, Gong, and Zendesk APIs directly?
How long does setup take?
What AI clients work with the Airbyte Agent MCP?
Connect Salesforce, Gong, and Zendesk Support and 50+ other tools to the Airbyte Agent MCP. Build agents that actually know your business.