Crisp

Crisp adds the Crisp live chat widget and exposes the $crisp queue for chatbox actions such as opening the chat, setting user details, and resetting sessions.

Official Crisp documentation

• Web Chat SDK
• $crisp methods
• Identity verification
• Cookie policies
• Session continuity
• Language customization

Integrate with c15t

import { type ReactNode } from 'react';
import { ConsentManagerProvider } from '@c15t/react';
import { crisp } from '@c15t/scripts/crisp';

const scripts = [crisp({ websiteId: 'crisp-123' })];

export function ConsentProvider({ children }: { children: ReactNode }) {
  return (
    <ConsentManagerProvider
      options={{
        mode: 'hosted',
        backendURL: 'https://your-instance.c15t.dev',
        scripts,
      }}
    >
      {children}
    </ConsentManagerProvider>
  );
}

How c15t loads it

• Category: functionality (Functional)
• Loads when: functionality consent is granted
• Before load: c15t seeds window.$crisp, CRISP_WEBSITE_ID, and any optional Crisp runtime globals
• On revocation: c15t follows the default script loader behavior for non-persistent scripts

Configure the integration

The helper seeds Crisp's documented globals before loading https://client.crisp.chat/l.js.

crisp({
  websiteId: 'crisp-123',
  locale: 'fr',
  cookieDomain: 'app.example.com',
  cookieExpiry: 3600,
  tokenId: 'secure-user-token',
  sessionMerge: true,
  safeMode: true,
});

locale and sessionMerge are written to CRISP_RUNTIME_CONFIG. cookieDomain maps to CRISP_COOKIE_DOMAIN, cookieExpiry maps to CRISP_COOKIE_EXPIRE, and tokenId maps to CRISP_TOKEN_ID. safeMode queues ['safe', true] on window.$crisp before the loader runs so Crisp starts in safe mode.

For session continuity, generate tokenId on your backend with a secure random value. Do not use emails, hashes of emails, timestamps, or incrementing IDs as Crisp session tokens. If you verify user emails, generate the HMAC signature on your backend and set it with Crisp's $crisp API after the helper loads.

Types

CrispOptions

Script