Salesforce can't answer it solo.
Typeform (NPS responses) in Salesforce is only one input; the renewal stalls without route detractors to CS with full CRM context alongside it.
Build a NPS-to-Action Routing Agent withSalesforce, Zendesk Support, and Slack
Process NPS responses shouldn't take a morning of tab-switching across Salesforce, Zendesk Support, and Slack. A detractor response is a churn signal.
Three tools, three tabs, and nothing reconciles typeform (NPS responses).
Now your agent can fix it.
Now your agent can fix it.
The Zendesk Support side stays separate.
Route detractors to CS with full CRM context from Zendesk Support sits in its own tab while Salesforce carries typeform (nps responses). Nobody joins them.
Slack knows before you do.
Create support tickets for complaints lands in Slack hours early. Too far from Salesforce to change the renewal in time.
Under The Hood
Three sources, one query: nps-to-action routing pulls Salesforce, Zendesk Support, and Slack pre-wired. Already connected.
01
Fetch process NPS responses from Salesforce (system of record)
Typeform (NPS responses)
02
Check route detractors to CS with full CRM context from Zendesk Support (support desk)
Salesforce/HubSpot (accounts)
03
Query create support tickets for complaints from Slack (comms layer)
Zendesk Support (tickets)
output
Agent-ready output
NPS-to-Action Routing's worklist: Process NPS responses, route detractors to CS with full CRM context, create support tickets for complaints, alert on declining account scores. Sorted by what needs you first.
The Context Store
Typeform (NPS responses) and the rest of Salesforce, Zendesk Support, and Slack, already one record.
Before the prompt runs, the Context Store has matched typeform (NPS responses), Salesforce/HubSpot (accounts), Zendesk Support (tickets), Slack (alerts) from Salesforce, Zendesk Support, and Slack and 2 more onto one account record. Nps-to-action routing just reads it, no ID-stitching.
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.
ACCOUNT-LEVEL JOINSSUPPORT SCHEMANO GLUE CODE
The Prompt
Copy. Paste.
a NPS-to-Action Routing Agent
Two steps. Your data, your results, under 60 seconds.
01install
Connect the Airbyte Agent MCP02copy and run
Help me turn Salesforce, Zendesk Support, and Slack into a single renewal I can act on.
SETUP
Airbyte's MCP exposes 5+ of your tools as one queryable layer.
WORKFLOW
connect Salesforce, Zendesk Support, and Slack -> read typeform (NPS responses), Salesforce/HubSpot (accounts), Zendesk Support (tickets), Slack (alerts) -> merge into one account view -> rank and explain. Each unconnected source is a one-time browser auth away.
TASK
Process NPS responses, route detractors to CS with full CRM context, create support tickets for complaints, alert on declining account scores and surface the worklist: highest-risk accounts first, each with a recommended next step.The Outcome
NPS-to-Action Routing in a single pass. No 2-hour tab marathon. Now your agent can fix it.
10x
Faster
10x. 2 hours to process NPS responses becomes one run of nps-to-action routing.
90%
Cheaper to run
~90% cheaper: zero new infra and no seats added to process NPS responses.
3 -> 1
Tools, one query
3 tabs into 1: Salesforce, Zendesk Support, and Slack collapse to one view to process NPS responses.
Based on internal benchmarks comparing Context Store queries to sequential API calls across equivalent datasets.
01 · Output
Ranked, not dumped
NPS-to-Action Routing ranks each account by risk, not by name. The top of the list is where to start.
02 · Signal
Where the tools disagree
Any conflict between Salesforce and your support desk on typeform (NPS responses) is raised for review rather than silently smoothed over.
03 · Context
The why, attached
Each line carries its evidence. Route detractors to CS with full CRM context pulled from Zendesk Support and Slack. Right where you read it.
04 · Action
Tells you what to do
Every row ends in a move: nps-to-action routing tells you the owner and the move.
05 · Brief
Worklist-ready
A worklist you can drop into the renewal: ranked, sourced from Salesforce, Zendesk Support, and Slack, scoped to typeform (NPS responses).
Other support agents on the same connectors
view All use casesMulti-Product Support Router Agent
The data for your renewal already exists in Jira / Salesforce / Freshdesk. The problem is no one view joins it. Multi-product companies misroute 30% of tickets.
Train AI models with ticketing data
Your renewal is only as fresh as the slowest tab. Support AI learns from historical ticket patterns. Yet the inputs sit split across Jira + Intercom + Zendesk Support.
Customer Trust AI Agent
Your renewal is only as fresh as the slowest tab. Trust issues escalate quickly. Yet the inputs sit split across Freshdesk, Zendesk Support, and Intercom.
Common questions
Didn't find your answer? Please don't hesitate to reach out.
How do I trust the renewal?
NPS-to-Action Routing cites a source per line. Typeform (NPS responses) from Salesforce, the rest from Zendesk Support and Slack. So any figure traces back.
What does NPS-to-Action Routing cost to run?
It rides the 5 connectors you already license. No seats, no glue code, no infra to process NPS responses.
What Salesforce data does NPS-to-Action Routing touch?
Just typeform (NPS responses), plus Salesforce/HubSpot (accounts), Zendesk Support (tickets), Slack (alerts), via Salesforce's scoped permissions. Nps-to-action routing copies nothing outside your stack.
Can NPS-to-Action Routing run on a schedule?
Yes, schedule it and the worklist arrives before the renewal starts, so process NPS responses happens hands-free.
Your support data already lives in Salesforce, Zendesk Support, and Slack. Let nps-to-action routing use it.
Wire Salesforce, Zendesk Support, and Slack and 50+ sources into the Agent MCP and build nps-to-action routing on data you already own.
