5 solution docs
Crisp solution docs
Live chat and a shared inbox from one script tag, kept off your critical path.
Pick Crisp and all 5 land in docs/solutions/crisp/, next to the rules and skills that reference them.
Every Crisp doc in the registry
Tags: app-router · consent · conversion · cookies · crisp · gdpr · hmac · impersonation · inp · lcp · next-script · nextjs · operations · performance · privacy · routing · security · segments · support · third-party
Consent gating a chat widget without breaking it
Chat sets cookies before anyone types a word, so hiding the launcher is not compliance. Gate the script tag itself, make withdrawal real, and know why a reload is the only honest teardown.
crisp · gdpr · consent · cookies
Keeping the chat bubble off the pages that need a clean hero
hide and show are visibility commands, not load control. Gate the script by route, hide on navigation, and give marketing pages a trigger you designed instead.
crisp · support · routing · conversion
Identifying signed-in users in chat without letting anyone impersonate them
An email set from the browser is a claim anyone can make. Sign it server-side with HMAC, pass the signature through, and give your support team a label they can act on.
crisp · support · security · hmac
Loading a chat widget without wrecking your Core Web Vitals
The vendor snippet is a synchronous script in the head. Move it to next/script with lazyOnload, measure the difference, and keep the click working while it downloads.
crisp · performance · lcp · inp
Routing support conversations with segments and session data
A shared inbox where everything looks the same is a queue, not a support system. Segments route, session data answers the first three questions, and both belong in code.
crisp · support · segments · routing