# Crisp

The c15t crisp helper loads the Crisp chat widget only after visitors allow functionality in Inth. On withdrawal, c15t removes the loader and reloads the page.

## Key facts

- **Tool:** Crisp
- **Category:** Support and chat
- **Consent categories:** Functionality
- **Setup method:** c15t package
- **Package:** @c15t/integrations

## Links

- [Documentation](https://c15t.com/docs/integrations/crisp)
- [Crisp](https://crisp.chat/)

Offer live chat with Crisp to visitors who allow functionality. Until then, c15t sets no CRISP\_WEBSITE\_ID, so no chat widget shows.

Inth keeps the consent record of each choice, with the visitor’s country and the policy that applied.

[Start for free](/dashboard/sign-up)

## Before you start

You need an Inth project that connects to your app and c15t in that app. You also need the website ID from your Crisp installation snippet.

Link another support contact for visitors who deny functionality, since the widget does not load for them.

[Open the quickstart for your framework](https://c15t.com/docs/frameworks)

## How consent works with Crisp

When functionality becomes allowed, the c15t crisp helper writes your website ID and loads the Crisp loader.

Before it loads, the helper creates window.$crisp as an empty array, unless your page made one already.

Commands that your code pushed onto $crisp stay in the queue. They never reach Crisp while the visitor denies functionality.

On withdrawal, c15t removes the script element and calls no Crisp API. The widget stays until c15t reloads the page.

## Installation

Crisp has one load mode in c15t. The helper waits for functionality permission.

### Wait for permission

No request goes to Crisp until the visitor accepts functionality. On withdrawal, c15t reloads the page to end the widget.

```ts
crisp({ websiteId })
```

An opt-out policy or no policy gives optional categories permission before a choice. Then Crisp loads on the first page. This guide uses an opt-in policy.

## Setup steps

#### Install the integration package

Add the helpers next to c15t. An import alone does not start the Crisp widget.

```
pnpm add @c15t/integrations
```

#### Add your website ID

The helper trims the ID. An empty ID logs an error, and the widget does not load.

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

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

Options such as locale, tokenId, cookieDomain and safeMode pass through to the Crisp runtime config.

### Register it with your existing setup

#### Next.js

Add scripts to c15t.config.ts, next to next.config.ts. Keep the rest of your config, such as mode, in the same call. App Router, Pages Router and static export read the same file.

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

export default defineConsentConfig({ scripts });
```

#### TanStack Start

Pass scripts to the ConsentRoot in your root route. Import helpers in the route module, not in a server function: script configurations carry callbacks.

```
import { scripts } from '../consent-scripts';

<ConsentRoot state={consent} scripts={scripts}>
```

#### React

Add scripts to the options of your ConsentProvider, next to mode. Keep the banner, dialog and preferences link inside the provider.

```
import { scripts } from './consent-scripts';

<ConsentProvider options={{ mode, scripts }}>
```

#### Nuxt

Register scripts under the c15t key in app.config.ts. Keep them out of nuxt.config.ts, which reaches the browser as JSON and drops the helper callbacks.

```
import { scripts } from '../src/consent-scripts';

export default defineAppConfig({
  c15t: { scripts },
});
```

#### Vue

Pass scripts to the c15tVue plugin call you have now. The plugin starts one script loader when the app mounts.

```
import { c15tVue, manifest } from 'c15t/vue/vue-plugin';
import { scripts } from './consent-scripts';

app.use(c15tVue, {
  mode: manifest(),
  scripts,
});
```

#### Astro

Add scripts to the client entrypoint, which the integration finds on its own. Keep helpers out of astro.config.mjs: its options are serialized into the page.

```
import type { C15tClientOptionsExtension } from 'c15t/astro';
import { scripts } from './consent-scripts';

export default { scripts } satisfies C15tClientOptionsExtension;
```

#### Svelte

Pass scripts as a prop to the ConsentProvider you have now. The provider owns the loader and disposes it on unmount.

```
<script lang="ts">
  import { ConsentProvider, manifest } from 'c15t/svelte';
  import { scripts } from './consent-scripts';
</script>

<ConsentProvider mode={manifest()} {scripts}>
  <!-- Your app and consent UI -->
</ConsentProvider>
```

#### SvelteKit

Add scripts to the ConsentRoot in the root layout. Import helpers in the layout component, not in +layout.server.ts: a server load cannot send functions to the browser.

```
<script lang="ts">
  import { ConsentRoot } from 'c15t/svelte';
  import { scripts } from '../consent-scripts';

  let { children, data } = $props();
</script>

<ConsentRoot state={data.consent} {scripts}>
  {@render children()}
</ConsentRoot>
```

#### HTML: Paste the vendor’s snippet behind consent

The helpers need a bundler. On a page with the c15t script tag, paste the vendor’s own snippet instead and keep it inert until visitors allow its category. Helper options, such as loadMode, do not apply.

```
<script type="text/plain" data-c15t-category="functionality">
  // The vendor's snippet, unchanged
</script>
```

#### JavaScript

Pass scripts to init() from @c15t/browser, next to your mode. With createConsentRuntime, pass scripts to it instead.

```
import { init, manifest } from '@c15t/browser';
import { scripts } from './consent-scripts';

const consent = init({
  mode: manifest(),
  scripts,
});
```

Remove the original Crisp snippet, so it cannot load without consent.

## Verify your setup

Filter DevTools Network by crisp.chat. Then test the three states.

- **Before a choice**: No Crisp request appears, and c15t sets no window.CRISP\_WEBSITE\_ID.

- **After you allow functionality**: The request to client.crisp.chat/l.js appears, and the chat launcher shows.

- **After you withdraw functionality**: c15t reloads the page, and the new page loads no Crisp widget.

Commands that your code queues on $crisp run only after the visitor allows functionality.

[Open the full Crisp guide](https://c15t.com/docs/integrations/crisp)

## Related guides

- [Front Chat](/integrations/front-chat)

- [Google Maps](/integrations/google-maps)

- [Gorgias Chat](/integrations/gorgias)