How to Manage Your Pocketsflow Orders With AI

You manage Pocketsflow orders with AI by connecting Claude, ChatGPT or Cursor to Pocketsflow's MCP server and asking in plain words: "find the order for this email", "why did this payment fail?", "reset the downloads on order 3310". Pocketsflow gives the AI 20 tools for orders, customers and delivery, and every change it makes shows up in your Pocketsflow dashboard. Refunds stay in the dashboard.

The Pocketsflow tools behind order support

Pocketsflow groups its order tools into three areas. The chart counts the tools in each, read from Pocketsflow's MCP tool list.

• Orders: Pocketsflow's tools list and open orders and customers, filter by status (paid, refunded, disputed or failed) or buyer email, and show an order's payment and checkout journey.
• CRM: Pocketsflow's tools find your best customers, open a buyer profile, and add private notes and tags. The customer CRM is part of the Pocketsflow Pro plan.
• Delivery: Pocketsflow's tools read and reset a buyer's downloads on every plan. PDF stamping and limited drops need the Pocketsflow Starter plan, and download limits the Growth plan.

How to connect your AI to Pocketsflow orders

1. Create a free Pocketsflow account, or sign in to the one you sell with.
2. Add https://www.pocketsflow.com/mcp to Claude, ChatGPT, Cursor or another MCP app as a connector.
3. Sign in to Pocketsflow and click Allow access.
4. Ask: "Show me my last 10 Pocketsflow orders."

Pocketsflow creates an API key named "MCP: <app>" for each connection. Delete the key in your Pocketsflow settings to disconnect that AI.

Answer a support email in one sentence

Most order emails ask one of four things. Pocketsflow's order tools let the AI answer each from the real order.

• "I paid but got nothing." Ask: "Find the order for ana@example.com and check it was paid." The AI calls Pocketsflow's list_orders with the email, then get_order, and tells you the status. For a subscription renewal, ask for the buyer's payments instead: list_orders covers one-time purchases, and list_payments includes renewals.
• "My download stopped working." Ask: "Reset the downloads on that order." The AI calls reset_order_downloads.
• "My card was declined." Ask: "Why did the payment fail?" Pocketsflow's get_order_payment_details returns the decline reason, and get_order_journey shows how many card attempts were declined.
• "I want my money back." Ask: "Show the payment on that order." The AI reads the amount and any earlier refund with get_order_payment_details, and you issue the refund from the order in your Pocketsflow dashboard.

Money stays in your hands

Pocketsflow's MCP server never moves money. Payment refunds are issued from the order in the Pocketsflow dashboard, so a buyer is only refunded when you click. Payouts are read only in the Pocketsflow MCP server: the AI can tell you your balance and whether a payout landed, but it cannot withdraw money or change your bank details.

Spot problems before buyers write in

Pocketsflow's order tools also help you look across orders, not only one at a time.

• "List failed orders from this week and tell me the most common decline reason."
• "Show disputed orders and the risk score on each."
• "Who are my 10 best customers by lifetime value?" (Pocketsflow Pro)
• "Tag every buyer of the course bundle as VIP." (Pocketsflow Pro)

A tag set this way is a Pocketsflow CRM tag: you see it on the buyer's profile in the dashboard and can filter customers by it. CRM tags are separate from email contact tags.

What to keep in the Pocketsflow dashboard

The AI is fast for lookups and one-off fixes. For refunds and dispute responses with documents, open the order in the Pocketsflow dashboard and handle it yourself. To see every tool group, read what Pocketsflow MCP can do; to set up Claude, follow the Claude setup guide; or start at the Pocketsflow MCP page.