| name | sales-fourfour |
| description | Four/Four (fourfour.ai) platform help — AI customer-research / voice-of-customer copilot that unifies conversations (calls, tickets, emails, chat) from 30+ sources into searchable Insights and Topics, with an AI Analyst for natural-language Q&A and workflows that route findings to Slack/Jira/email. Developer surface: an OData REST API (`/odata`, OAuth2 authorization-code, `api:read` scope, `@odata.nextLink` paging), a CRM Importer API (`/import/crm/{type}`, PAT bearer, CSV, async jobs), HMAC-SHA256-signed webhooks (`Signature` header, 3x retry), and an MCP server (`fourfour.ai/mcp`). Use when pulling Insights or Conversations through the OData API, importing CRM accounts/contacts, verifying signed webhooks, wiring the MCP server into Claude/Cursor, picking an AI Analyst vs AI Researcher plan, or centralizing voice-of-customer data. Do NOT use for VoC survey-program strategy across tools (use /sales-customer-feedback) or feedback-board/roadmap voting (use /sales-frill). |
| argument-hint | [describe what you need help with in Four/Four] |
| license | MIT |
| version | 1.0.0 |
| tags | ["sales","customer-feedback","voc","platform"] |
Four/Four Platform Help
Step 1 — Gather context
If references/learnings.md exists, read it first for accumulated platform knowledge.
-
What are you trying to do?
- A) Read/sync Insights, Topics, or Conversations via the OData REST API
- B) Push CRM accounts/contacts/opportunities in via the CRM Importer API
- C) Verify a signed webhook (HMAC-SHA256) and react to insight/conversation events
- D) Wire the MCP server into Claude / Cursor for natural-language Q&A
- E) Use the AI Analyst / Workflows to route insights to Slack/Jira/email
- F) Pick a plan (AI Analyst vs AI Researcher vs Enterprise) or understand usage limits
-
API or no-code? Code → OData API + CRM Importer + signed webhooks. AI assistant → MCP server. No endpoint → native connectors / Zapier / visual Workflows.
Skip-ahead rule: if the user's prompt already provides enough context, skip to Step 2.
Step 2 — Route or answer directly
| If the question is about... | Route to... |
|---|
| Voice-of-customer / survey program strategy (NPS/CSAT/CES) across tools | /sales-customer-feedback {question} |
| Feedback boards / feature voting / public roadmap | /sales-frill {question} |
| Aggregating unsolicited feedback across reviews/social/support | /sales-noisely {question} |
| Account health / churn-prevention program strategy | /sales-customer-success {question} |
| Connecting Four/Four to a CRM/PM tool generically (iPaaS) | /sales-integration {question} |
When routing, give the exact command, e.g. "This is a strategy question — run: /sales-customer-feedback design a closed-loop VoC program".
Step 3 — Four/Four platform reference
Read references/platform-guide.md for the full reference — the Discovery/Validation/AI Analyst/Workflows/Competitive-Intelligence/Customer-Success module map (what's API vs webhook vs UI), plan tiers and usage limits, the Conversations→Insights→Topics→TopicModels data model, integrations by data-flow direction, and quick-start recipes.
for the integration surface — OData base , auth (, scope , Bearer, 24h tokens), the entity sets (Insights/Topics/TopicModels/Conversations/Participants + CRM objects), (////, paging), the (, PAT bearer, CSV, async jobs), (, header, 3x retry), and the (, OAuth discovery).
