Why connect Crisp?
Your support team talks to customers every day through Crisp. They hear about bugs, feature requests, workarounds, and frustrations, but this intelligence is usually locked inside conversation threads.
When you connect Crisp, ProductBet captures the intention behind your customer conversations, reading the full thread for context, not just the first message.
What gets captured
ProductBet processes Crisp conversations and extracts:
- Feature requests and missing capabilities
- Bug reports and broken workflows
- UX friction and confusion points
- Integration requests
Each conversation becomes a signal with structured metadata from the original Crisp thread.
How to connect
Go to Settings > Integrations > Crisp and click Install Crisp app. You'll be redirected to Crisp to install the marketplace plugin and select which workspace to connect. After installation, you're redirected back and the integration is active.
How it works
Once connected, ProductBet automatically processes new Crisp conversations as they come in. When a customer sends a message or your team replies, ProductBet re-reads the full thread to capture the latest context.
If a conversation introduces a new issue that wasn't covered by earlier messages, ProductBet creates an additional signal. If the new messages only add detail to an already-captured issue, no duplicate signal is created.
Troubleshooting
- Not seeing signals? Make sure the integration shows as "Connected" on the integrations page. If it shows an error, try disconnecting and reconnecting.
- Missing conversations? ProductBet processes conversations in real-time via webhooks. Historical conversations from before the connection are not imported automatically — use the import button to pull them in.