Draft friendly replies from docs and ticket history | Copy-Paste AI Recipe

Name: Draft friendly replies from docs and ticket history
Prep time: 10 min
Ingredients: Postgres AI system; Slack AI system

NextFlows Contributors

doi:nextflows.ai/recipes/draft-friendly-replies-from-docs-and-ticket-history

⚡ TL;DR

✓ Reduce handoff friction with clear ticket status, open risks, owners, and recommended next responses
✓ 10 minutes to first success
✓ Read-only
✓ Uses Postgres MCP, Slack MCP

Before you start

0/4

Claude Desktop installedPostgres MCP access configuredSlack MCP access configuredPermission for Postgres read access, Slack read access

Setup (10 min)

0/5

1Connect Postgres MCP in your MCP client and confirm the server shows as available.

2Connect Slack MCP so the assistant can combine context.

3Grant the minimum read scopes needed for this escalations workflow.

4Open the workspace, channel, repository, database, or account you want the assistant to use.

5Paste the prompt from this recipe into your AI client.

The prompt

You are helping a Support teammate with this workflow: Draft friendly replies from docs and ticket history.
Use the connected Postgres MCP, Slack MCP tools to gather only the information needed for escalations.
Create a concise result with: summary, important details, recommended next actions, owners, and links to sources.
Flag anything uncertain, stale, sensitive, or missing instead of guessing.
Do not make changes without asking me to confirm the final draft.

Paste into Claude Desktop. It will use your connected AI servers: Postgres MCP, Slack MCP.

Expected outcome

Reduce handoff friction with clear ticket status, open risks, owners, and recommended next responses

Success checklist

0/4

The output explains the escalations context in plain English.Every recommendation includes a source, owner, or next action.Sensitive data is summarized only at the level needed for the task.Support teammates can use the result without asking for extra background.

Troubleshooting

MCP server is not available in the client

Cause

The server config was not saved, the client was not restarted, or Node.js cannot run npx.

Solution

Run Postgres MCP manually with its install command, then restart your MCP client.

The assistant cannot find the expected records

Cause

The connected account lacks access to the workspace, channel, repo, database, or page.

Solution

Grant the missing read scope and test with one known record before running the full recipe.

The result is too broad or includes stale context

Cause

The prompt did not limit the date range, source, account, or project clearly enough.

Solution

Add the relevant team, date range, channel, repo, account, or page name to the prompt.