Build with Paydirt
Build customer feedback into your iOS app
Install Paydirt with a coding agent, collect voice and text feedback, and read exact customer conversations through MCP. Start with a concrete iOS use case.
What you are building with
Paydirt is an iOS 15+ feedback SDK and a feedback backend with an MCP interface. Your app chooses where a form appears. Customers answer by voice or text, follow-up questions explore their answers, and completed conversations can go to Slack. Agents can read authorized responses for product research.
Use it for optional product feedback and cancellation research. Keep required account fields, purchase logic, and entitlement decisions in your app. Paydirt at paydirt.ai is separate from the time-tracking product at paydirtapp.com.
From agent connection to a real test answer
1. Connect your coding agent
Choose the command for your host and complete Paydirt authorization in the browser. The hosted MCP endpoint uses OAuth with PKCE S256.
# Codex codex mcp add paydirt --url https://mcp.paydirt.ai/mcp # Claude Code claude mcp add --transport http paydirt https://mcp.paydirt.ai/mcpOther MCP hosts and the local stdio fallback: connection guide. Host support and workspace settings determine availability.
2. Give the agent the placement and scope
Add Paydirt to this iOS app. Add a Suggest a Feature button in Settings. Let people answer by text or voice. Keep responses in Paydirt for agent review. Build and launch the app so I can submit a test answer.The agent needs the app repository and Xcode to edit and verify an iOS integration. A remote chat connection alone cannot build the app.
3. Verify the experience and destination
Open the real form, submit a test answer, and confirm the saved response through
paydirt_wait_for_response. If you choose Slack, authorize the workspace, confirm channel routing, and verify the completed conversation arrives.
Choose what to build
Onboarding feedback
Ask an optional question after onboarding completes, while the first-run experience is still fresh. Keep the feedback conversation separate from required setup.
Read the implementation guide →Feature requests
Let iOS customers describe the outcome they need by voice or text, then ask follow-up questions that give developers enough context to evaluate the request.
Read the implementation guide →Post-action feedback
Collect context after an export, completed session, or other successful action so people can describe the experience they just had.
Read the implementation guide →Trial cancellation feedback
Keep free-trial cancellation feedback separate from paid subscriber research, with the subscription context and exact customer answers together.
Read the implementation guide →Slack customer feedback
Send the exact questions and accepted answers to a chosen Slack channel when a customer finishes a Paydirt conversation.
Read the implementation guide →AI agent feedback analysis
Use Paydirt’s read-only response tools to inspect exact customer conversations, identify themes, and propose changes for developer review.
Read the implementation guide →