Chat and support

Crisp

Configure Crisp

Copy the website ID from your Crisp installation snippet, where it is assigned to CRISP_WEBSITE_ID.

npm install @c15t/integrations@alpha

src/consent-scripts.ts

import { crisp } from '@c15t/integrations/crisp';

export const scripts = [crisp({ websiteId: 'YOUR_WEBSITE_ID' })];

Register the scripts

Complete your framework quickstart first. Keep its Inth endpoint, policy, styles and consent UI. Remove the vendor's original script, SDK initializer or tag-manager entry, so the vendor loads only through c15t.

The vendor pages put the helper in src/consent-scripts.ts. If your framework quickstart already has a scripts array, such as the one in c15t.config.ts in the Next.js guide, add the helper to that array instead of creating a second file. The scripts export is a configuration, not an initializer. Add it to the c15t provider you already have, at the registration point for your framework below. These are edits to that provider, not a second provider.

Add the configuration to scripts in c15t.config.ts, next to next.config.ts:

import { defineConsentConfig } from 'c15t/next';
import { scripts } from './src/consent-scripts';

export default defineConsentConfig({ scripts });

Keep the rest of your config, such as mode and routePrefix, in the same call. ConsentRoot reads the config in the browser, so the layout keeps passing only state. App Router, Pages Router and static export all read the same file. See Next.js scripts and embeds.

Options

Option	Default	Behavior
`websiteId`	Required	Written to `window.CRISP_WEBSITE_ID`. The helper trims it. Empty or whitespace-only values log an error and the script does not load.
`locale`	None	Widget locale, written to `window.CRISP_RUNTIME_CONFIG.locale`.
`sessionMerge`	None	Merges anonymous sessions into token-backed sessions. Written to `CRISP_RUNTIME_CONFIG.session_merge`.
`tokenId`	None	Session continuity token, written to `window.CRISP_TOKEN_ID`.
`cookieDomain`	None	Cookie domain, written to `window.CRISP_COOKIE_DOMAIN`.
`cookieExpiry`	None	Cookie lifetime in seconds, written to `window.CRISP_COOKIE_EXPIRE`.
`safeMode`	`false`	Pushes `['safe', true]` to `$crisp` before the loader.
`scriptSrc`	`https://client.crisp.chat/l.js`	Loader URL override. A blank value falls back to the default.

Loading and revocation

crisp uses the functionality category. The chat widget loads only while functionality is allowed, so link another support contact for visitors who deny it. On revocation the helper removes the script element and calls no Crisp API. The running widget stays until c15t reloads the page.

Before loading, the helper creates window.$crisp as an empty array unless your page already made one. Commands your code pushed onto $crisp earlier stay queued, and Crisp runs them when it loads. They never reach Crisp while functionality is denied.

Verify Crisp

After you allow functionality, the request to client.crisp.chat/l.js appears and the chat launcher shows. Before that, window.CRISP_WEBSITE_ID is undefined.

Test in a private window with an opt-in policy. Open DevTools Network, disable the cache and filter by the vendor's domain:

Load the page. No request goes to the vendor before you choose.
Click Reject, then reload. There is still no vendor request.
Open Privacy settings and allow the helper's category. The vendor script loads without a page reload.
Turn the category off again and save. c15t reloads the page, and the new page makes no vendor request.

c15t reloads on revocation because removing a script element does not stop code that already ran. The vendor's listeners, timers and queued events stay alive until the page unloads. If you set reloadOnConsentRevoked: false, stop the vendor yourself. Register a callback-only script whose onConsentChange calls the vendor's opt-out API, as shown in custom integrations, and check the permission before each of your own event calls. The reload does not delete cookies the vendor already set; see clear on revocation for your framework.

The helper sets vendor to its script ID, so once you declare that vendor a visitor can turn it off inside an allowed category. See vendor consent for your framework. The consent verification guide covers navigation, expiry and hosting checks.