This page is an agent-readable workflow for Deck. Humans can follow along. Coding agents should treat the steps as the source of truth.

Cross-tool signal sweep — agent workflow

• Use it when: the user asks "what feedback is Deck missing?", "is everything from Slack and support in Deck?" or "compare our tools with Deck".
• Outcome: the user has a gap report. It shows which tools send feedback to Deck, which do not, which topics are missing from Deck, and the fix for each gap. Nothing changes in Deck or in the other tools.
• Needs: Deck MCP, and read access to at least one other tool in this client, for example Slack, a support desk, a CRM or a call recorder. This workflow only reads.

1. Probe Deck MCP

Call get_user_context. This must be a real tool call.

• 401 Unauthorized: tell the user to connect Deck MCP in this client (Settings → Connections). Stop.
• No Deck tools: fetch and follow https://docs.getdeck.io/docs/agents/getting-started/prompts/ai-pm.md. Stop this workflow until the tools work.

2. See what Deck receives

Make these calls at the same time:

• explore_integrations with no input. Read the state of each integration (active, needs_attention or not_connected), the last sync and the synced item count.
• list_sources with limit: 50. Read total, the newest sources and the processing summary. The type breakdown in the message counts only these 50 sources, not the organization.
• explore_workspace with view: "credits". Read the items that wait for credits.

Then make these calls at the same time:

• For each active feedback integration, call list_sources with its source: gong, slack, intercom, zendesk, custom_api, posthog or notion. Read total.
• For Intercom, Zendesk and Custom API, also call list_sources with that source and synthesized: false. This shows tickets that synced but are not processed yet.
• When Slack is active, call explore_integrations with integration_type: "SLACK" and view: "slack_channels". Read which channels Deck syncs and which need the Deck bot.

3. List the other tools

List the tools in this client that are not Deck tools. Ask the user which ones hold customer feedback, and the time window. The default is the last 30 days.

Do not sweep a tool that the user did not name.

4. Sample the signal

For each tool that the user named, read recent customer-facing items with that tool's own read tools. Examples are support tickets, call notes, channel messages and issues with a customer label.

For each item, write down the topic, a short quote, the date and a link to the source. Keep personal data out of the notes, except what the report needs.

Group the items into 5 to 15 topics. Label every count from these tools as your own sample count.

5. Check each topic in Deck

For each topic, make these calls at the same time:

• search_deck with query set to the topic keywords.
• explore_insights with query and window_days set to the sweep window (7, 30, 90, 180 or 365).
• explore_themes with query.

Mark each topic:

• Covered: Deck has insights on it in the window. Give Deck's count and a link.
• Thin: Deck has a few insights, but the other tool has many more items.
• Missing: Deck has no insights on it.

6. Find the cause of each gap

• The tool is in explore_integrations and is not_connected: an organization admin connects it in Settings → Integrations.
• The integration is needs_attention: an organization admin reconnects it in Settings → Integrations.
• A Slack channel is not synced: someone runs /invite Deck in the channel. Then an admin adds the channel in Deck.
• Items synced but Deck has not processed them yet, or they wait for credits: they show in Deck after processing. Give the counts from step 2.
• Deck has no integration for the tool: export the data as CSV and upload it in the Deck web app. See CSV import. For call or interview transcripts, see Transcript upload.
• The feedback comes from inside the product: propose Install a feedback widget.

7. Report

Show two tables.

1. Tools: tool, Deck status, Deck's synced count, gap and fix.
2. Topics: topic, your sample count with source links, Deck's count with a link, and the mark from step 5.

End with the top 3 fixes, in order of the signal that they would add.

Rules

• This workflow only reads. Do not call Deck write tools.
• Quote Deck's numbers. Do not compute your own. Label counts from other tools as your sample counts.
• No MCP tool connects an integration or uploads feedback. Uploads happen in the Deck web app. Only organization admins manage integrations.
• Never send customer feedback with submit_feedback. That tool sends feedback about Deck to the Deck team, not to your workspace.
• Do not change anything in the other tools.
• If the user has more than one Deck organization, call select_organization first and pass org_id on every call.

Done when

• Each tool that the user named has a Deck status and, for a gap, a fix.
• Each topic has a mark, Deck's count and links to its sources.
• The user has the top 3 fixes, and nothing changed in Deck or in the other tools.

See also: Slack, Intercom, Zendesk, Gong and Model Context Protocol.