Production Checklist

1.Use a production environment

Make sure you're working in your production environment, not sandbox, before copying keys.

2.Add your allowed domain

Add your site's exact domain (e.g. https://example.com) to the allowed domains list in your environment settings.

3.Publish the bot

Bots must be explicitly published before the widget or API will serve responses. Check the bot's status in the dashboard.

4.Use the correct public key

Copy the public widget key (pk_live_…) from the production environment — not the sandbox key.

5.Set the right usage mode

Decide whether to use hard stop (block at limit) or pay-as-you-go (continue and pay overage) in your billing settings.

6.Check your quota

Review your plan's included usage and confirm it's sufficient for expected launch traffic.

7.Test the fallback response

Send a message your bot doesn't know the answer to and confirm the fallback response is acceptable.

8.Test the mobile widget

Open your site on a mobile device and verify the chat bubble renders and functions correctly.

9.Review your billing plan

Confirm your plan covers expected usage. Upgrade before launch if needed.

10.Monitor usage after launch

Check the usage dashboard after going live. Set up alerts if your plan approaches its limit.

Using sandbox keys in production

Sandbox keys will not serve responses on your live site. Always switch to pk_live_ keys before launch.

Forgetting to publish the bot

Even if your bot has Q&A, it won't respond until it's published. Check the bot status before embedding.

Missing allowed domain

The widget will silently fail if your domain isn't in the allowed list. Add it before testing.

No usage plan set

If you don't set a limit mode, the default behavior may surprise you. Choose hard stop or PAYG explicitly.