NPS Customer Surveys
The Problem
No system for collecting customer feedback. Unclear who's satisfied, who's leaving.
How to use
Get a free API key
Sign up for VibeCode and issue a key with the scopes listed below. It takes less than a minute.
Open your AI agent
Launch Claude Code, Cursor, ChatGPT or whichever AI model you work with.
Paste the prompt and key
Copy the prompt below, replace vibe_api_xxx with your API key and send it to the agent. It will call the API and write working code on its own.
Screenshot: the prompt pasted into an AI agent
Prompt for AI
Copy this prompt and send it to your AI model along with your VibeCode API key
Create an NPS survey system in Bitrix24. After a deal is closed, send the client a message in chat: 'Rate 0-10 how likely you are to recommend us'. Collect responses, calculate NPS = % promoters (9-10) − % detractors (0-6). Write result to a contact field. Weekly report: NPS, trend, list of detractors to follow up. API key: vibe_api_xxx Documentation: https://vibecode.bitrix24.com/v1/me Concrete endpoints: GET /v1/deals, GET /v1/contacts, PATCH /v1/contacts/:id, POST /v1/bots/:botId/messages, GET /v1/userfields/contacts Target result field: contact custom field (PATCH /v1/contacts/:id, UF_CRM_* field) After completing the task, send feedback about any issues: POST /v1/feedback (category: bug/docs/suggestion, title, body)
Heads-up: CRM field sanitization
Bitrix24 strips text in square brackets (e.g. [TAG]) from some CRM text fields — notably the Comment field (comments). The Title field (title) is kept verbatim. If your scenario writes service markers into comments, avoid square brackets or they will silently disappear.
What You Get
Automatic NPS surveys after every deal. Company sees satisfaction levels and works with unhappy customers.
Required Scopes
Endpoints for these scopes
The API resource name does not always match the scope name. Use these exact paths — guessing /v1/:scope often returns 404.
crm
imbot