1What FoxPlug reads from Crisp
These are the exact things it reads, and nothing else.
| What | The details it takes |
|---|---|
| Your Website ID | typed by you in the box under the token: the long id of your Crisp website. A pasted Crisp address is trimmed down to that id. Without a valid one the read stops with an error |
| Your plugin token | the two values of a Crisp Marketplace plugin token, identifier and key, pasted as identifier:key. They are sent to Crisp as basic sign-in together with a header saying it is a plugin token. A token missing either part stops the read with an error |
| Your newest conversations (segments and creation time only) | for each conversation: the segments on it and the time it was created, 50 per page, up to 3 pages, so at most 150 conversations. The conversation list Crisp sends back carries other fields too, among them message previews and visitor details; the code takes only the segments and the creation time and drops the rest |
| Counts per segment | over the last 30 days; a segment must be at least 3 characters and be on at least 2 conversations; the top 20 are kept, each as a 'request' with as many votes as conversations |
2Moments it finds, and what each becomes
A moment is one thing that happened in Crisp worth a second look. Each one is scored, then it becomes a post, a changelog entry, a thing to fix or an idea to email, or it is skipped.
A segment used on at least 3 conversations in the last 30 days matches the words of something you shipped in the last 30 days
The moment is titled like this: Looks like you shipped what 6 people asked for: csv export
Six conversations from the last 30 days carry the segment 'csv export', and one of your updates this month is 'Added CSV export to reports'. FoxPlug writes 'Looks like you shipped what 6 people asked for: csv export' and says the segment is on 6 conversations in 30 days. At most 3 such moments come out of one read.
3How the brain uses it
The rules below are the ones that apply to Crisp. The same rules, with worked examples, are on the brain page.
- Crisp is read for conversation segments only, counted over 30 days. A segment on at least 2 conversations becomes a request with that many votes, handled like Intercom and Help Scout tags. Message text, visitor names and emails are never read. How the brain decides
- A segment with at least 3 conversations whose words match something you shipped in the last 30 days becomes a 'looks like you shipped it' say line. Matching is by words; check it before you post. How the brain decides
- FoxPlug keeps segment names and counts, not who asked, so it cannot write to the people who asked; telling them is yours to do. How the brain decides
4Set up Crisp in a few steps
Access: a Crisp Marketplace plugin token (identifier and key) plus your Website ID, pasted by you. What to give it: plugin token with the conversation sessions read scope (FoxPlug only reads); Website ID goes in the box under it.
- Sign in to the Crisp Marketplace (it is a separate sign-in from your Crisp inbox), open Plugins and click New Plugin.
- Choose the Private type and name it FoxPlug.
- On the plugin page, open Tokens, go to Production and ask for a production token. Choose the read scope for conversation sessions.
- Install the plugin on your website using the private install link in the plugin's settings.
- Paste the token into FoxPlug as identifier:key, and type your Website ID in the box under it.
- Press Check for what's new.
5Limits worth knowing
Where it stops, so nothing surprises you.
- Reads at most 3 pages of 50 conversations, and stops earlier when a page has under 50.
- Only conversations created in the last 30 days are counted.
- A segment needs at least 2 conversations to appear and at least 3 to produce a 'Looks like you shipped it' moment; at most the top 20 names are kept.
- Segments have no completed state, so there is never a 'Shipped what N people asked for' moment from Crisp, only the matched kind.
- Crisp's reference lists the conversation list route, its page size of 20 to 50 (the reader asks for 50), the conversation sessions scope, and a segments field on each conversation. A plugin token has a daily request quota set by Crisp (5000 a day by default, Crisp says it can be configured).
- NOT confirmed: the order the conversation list comes back in (the reader does not rely on it but only sees the first 150 conversations Crisp sends), and whether the creation time is in seconds or milliseconds (the reader accepts both). The conversation list response has no example in Crisp's reference.
- NOT confirmed: whether a private plugin token for your own website needs Crisp to approve its scopes, and how long that takes. Crisp's page says some scopes need approval, which can take a few minutes.
- The token is a two-part secret and the sheet cannot show that it is limited to reading, so read only is false; FoxPlug only makes GET requests either way.
6What it never reads
Read only means read only, and the list below is what the code leaves alone.
- Message text, previews and conversation notes
- Visitor names, email addresses, phone numbers and locations
- Anything that writes to Crisp: it sends no message, changes no conversation and adds no segment
7How Crisp differs from the tools next to it
Near-identical to Help Scout, Intercom, Zendesk and Freshdesk in what FoxPlug does with the result: labels on conversations are counted over 30 days and matched to what you shipped. Crisp: a Marketplace plugin token (identifier and key) plus your Website ID, then the conversation list (50 per page, up to 3 pages); segment names only. None of these has a completed state, so all can only give 'Looks like you shipped it' moments.
8Questions
Why does FoxPlug ask for a Website ID as well as the token?
A Crisp plugin token can be installed on several websites, and every conversation list is read per website. The Website ID, the long id of the site in your Crisp settings, tells FoxPlug which one to count.
Does FoxPlug read my chats or my visitors' details?
No. It counts the segments you put on your newest conversations. Message text, visitor names, emails and phone numbers are not read or kept.
Do I need to label my conversations?
Yes. FoxPlug counts segments, so a conversation without any segment adds nothing. The more consistently you label what people ask for, the more useful the counts are.
Has the Crisp connection been tested against a real account?
No. It is marked code-path-only: the code path exists and its offline checks pass, but no real Crisp account of ours has exercised it. Treat the first read as the test.
FoxPlug reads this tool only when you press Check for what's new, and only to read. Plans and limits are on the pricing page. Questions: support.