Crmble Surveys Integration

Responsly writes customer feedback directly onto the Trello cards that Crmble turns into a CRM pipeline. Post-demo ratings appear as numbers on the card face. Win/loss reasons become color-coded labels. Account health scores sit next to deal values. The board becomes a visual feedback map of your entire pipeline.

For sales teams running their CRM on Trello through Crmble, the deal card is the single source of truth. Adding survey data to that card means reps never need to check a separate dashboard to understand how a prospect feels about the product, the demo, or the buying process.

Why deal cards need the customer’s voice

Crmble gives Trello boards pipeline structure — stages, deal values, probability scores, and reporting. But pipeline data describes the seller’s view of the deal. The buyer’s perspective is usually trapped in email threads, call notes, or not captured at all.

A deal card showing “45K, 60% probability, Demo Completed” tells you where the deal is. A card that also shows “Post-demo rating: 2/5, Comment: ‘The pricing model confused our CFO’” tells you whether the deal is actually alive.

Survey data on cards creates three advantages:

• reps prepare for follow-ups by reading the prospect’s exact words instead of relying on memory,
• managers spot deals at risk during pipeline reviews without drilling into individual notes,
• and Butler automations react to feedback signals faster than any human could review each card.

For more on structuring feedback that surfaces specific deal insights, see our guide on matrix questions.

How the integration connects

The Responsly–Crmble integration uses Trello’s API to write survey data onto cards. Setup is handled in the Responsly dashboard.

1. Generate a Trello API key and token — in Trello, navigate to the Power-Ups admin and generate credentials with board read/write permissions.
2. Map survey questions to card custom fields — assign each question to a Trello custom field. Ratings become number fields, categorical answers become label assignments, and comments become text fields.
3. Card matching — include the Trello card ID in the survey URL. Responsly uses this to update the exact card the survey relates to.
4. Butler rule setup — in Trello, create Butler automations that trigger on custom field changes written by the integration.

Post-demo ratings that move cards through the pipeline

A B2B software company sends a three-question survey immediately after every product demo: overall impression (1–5), feature relevance (1–5), and “What would prevent you from moving forward?” (open text).

Survey responses update the deal card instantly:

• Demo score 4–5 — a Butler rule moves the card to “Proposal Sent” and tags it with a green strong-interest label. The rep receives a Slack notification to send a proposal within 24 hours.
• Demo score 3 — the card stays in “Demo Completed” but receives a yellow needs-nurture label. The rep sees the open-ended feedback and tailors the follow-up.
• Demo score 1–2 — a Butler rule moves the card to “At Risk” and assigns the sales manager. The open comment on the card explains exactly what went wrong.

Before this system, the team relied on reps to self-report demo quality. Deals with low demo scores sat unattended in the pipeline for an average of 11 days. After automation, at-risk deals received manager attention within 4 hours. The team’s demo-to-proposal conversion rate improved from 38% to 52% over two quarters.

Win/loss labels from buyer surveys on closed deals

When a deal is marked won or lost, Crmble triggers an email with a Responsly survey to the primary buyer contact. The survey asks: deal outcome satisfaction, primary reason for decision (multi-select), and likelihood to expand or refer.

Closed cards receive:

• Win reasons as labels — “product-fit,” “pricing,” “support-quality,” or “competitive-advantage” labels appear on won cards,
• Loss reasons as labels — “price-too-high,” “chose-competitor,” “timing-wrong,” or “missing-feature” labels appear on lost cards,
• Satisfaction score — the buyer’s process satisfaction rating displays as a number field.

After six months the sales director filtered the board by loss labels: 41% of losses carried the “missing-feature” label, with the open comments consistently mentioning the same three capabilities. This data justified a product roadmap change that the sales team had been requesting without quantitative backing. Read about directional and non-directional hypotheses for structuring this kind of analysis.

Account health NPS visible on active deal cards

A SaaS company with annual contracts sends quarterly NPS surveys to existing customers. The NPS score and comment sync to the customer’s Crmble card on the “Active Accounts” board.

Pipeline review meetings now include account health:

• cards showing NPS 9–10 are flagged for upsell conversations,
• cards showing NPS 0–6 are moved to a “Retention Risk” list automatically by Butler,
• the sales manager reviews retention risk cards weekly, reading the verbatim comments directly on each card.

Accounts with NPS below 6 that received proactive outreach within 7 days renewed at 74%, compared to 49% for those that were contacted after 30+ days. The card-level visibility made it impossible to overlook a deteriorating account.

Setting up the integration

1. Get Trello API credentials — generate your API key and token from Trello’s developer portal with board read/write access.

2. Connect Trello in Responsly — open your survey’s Integrations tab, select Crmble/Trello, and paste the credentials.

3. Create custom fields on your Crmble board — add fields like demo_score (number), satisfaction (number), feedback_comment (text), and labels for win/loss categories.

4. Map survey questions — in Responsly, assign each question to the corresponding Trello custom field or label.

5. Configure Butler automations — build rules that trigger on custom field value changes: move cards, assign members, send notifications, or apply labels based on survey scores.

6. Embed survey links in pipeline workflows — include the survey URL with the card ID parameter in email templates sent at demo completion and deal close. Use skip logic to keep surveys under four questions for higher response rates from busy buyers.

Best practices

Send surveys at deal stage transitions. Post-demo, post-proposal, and post-close are the three moments where buyer feedback is most actionable. Each survey should be short and specific to that stage.

Use labels for categorical analysis, custom fields for scoring. Labels are visually scannable on the board — you can see loss reason patterns at a glance. Custom fields hold the numerical data for Crmble’s reports and Butler conditions.

Review loss reasons monthly, not quarterly. Patterns in loss data shift fast. A monthly review of loss labels catches emerging competitive threats or product gaps before they compound.

Close the loop on demo feedback within 48 hours. A prospect who rated a demo 2/5 and explained why deserves a follow-up that directly addresses their concern. The feedback is sitting right on the card — use it.

Start putting customer feedback on every deal card

Connect Crmble to Responsly and send your first post-demo survey. Let every rating, reason, and comment live where your sales team already works — on the Trello cards that run your pipeline.