Add Crisp chat on checkout
Crisp adds a live chat widget to checkout so buyers can ask questions before they pay. In AtomicPay, Crisp is configured per product in the product checkout integrations area.
Use this guide when checkout hesitation is high, when support agents should help during payment, or when buyers need clarification about pricing, trials, or delivery before completing purchase.
What Crisp on checkout controls
| Area | Purpose |
|---|---|
| Chat widget visibility | Shows Crisp on the configured product checkout experience. |
| Website ID binding | Connects the product checkout to the correct Crisp workspace. |
| Buyer support entry point | Lets buyers ask questions before payment is completed. |
| Validation | Requires a valid UUID Website ID before save. |
| Support workflow | Connects live conversations to your Crisp inbox and team process. |
Before you enable Crisp
- Confirm the product and checkout page are ready.
- Make sure support agents know which products use checkout chat.
- Review team roles and product access for support coverage.
- Ensure checkout copy still explains payment and delivery without relying on chat alone.
- Decide how support will use short links versus chat during conversations.
Configure Crisp on checkout
- Confirm you are in the correct business workspace.
[Screenshot: App header — correct business workspace selected.]
- Open the product that should show Crisp on checkout.
[Screenshot: Product opened — checkout integrations area accessible.]
- Go to the product checkout integrations area.
[Screenshot: Checkout integrations tab — Crisp section visible.]
- Enable Crisp.
[Screenshot: Crisp toggle enabled on product checkout.]
- Enter the Crisp Website ID from your Crisp workspace.
[Screenshot: Website ID field — valid UUID pasted from Crisp.]
- Save the configuration.
[Screenshot: Crisp configuration saved successfully.]
- Open the live checkout link as a buyer.
[Screenshot: Live checkout opened — buyer view for chat test.]
- Confirm the widget appears on checkout.
[Screenshot: Crisp chat widget visible on checkout page.]
- Send a test message and confirm the support team receives it in Crisp.
[Screenshot: Crisp inbox — test message received from checkout.]
[Screenshot: Support playbook — payment, refund, and access escalation steps.]
Website ID format
The Website ID must be a valid UUID, for example:
12345678-1234-1234-1234-123456789abc
Copy the ID from Crisp workspace settings. Placeholder or partial values will block save.
What to verify before launch
| Check | Why it matters |
|---|---|
| Widget appears on the real checkout URL | Buyers must see chat where they actually pay. |
| Support staffing matches launch traffic | Chat without response hurts conversion. |
| Agents know approved support policies | Especially for refunds and upgrades. |
| Checkout copy is still clear | Chat should support conversion, not replace pricing clarity. |
| Payment method questions are documented | Reduces inconsistent buyer answers in chat. |
Best practices
- Enable Crisp only on products where support can respond reliably.
- Train agents to use Sales and customer history during conversations.
- Keep support links separate from campaign links.
- Review chat-related conversion issues alongside incomplete payments.
- Remove or adjust chat if response times are too slow during launches.
Common mistakes
- Enabling Crisp without support coverage.
- Using the wrong Crisp Website ID for the product.
- Letting support share campaign or affiliate links incorrectly.
- Promising delivery or refund outcomes that conflict with product policy.
- Testing chat on an unpublished checkout draft.
FAQ
Does Crisp appear after purchase too?
This integration is for checkout. Post-purchase support may use other channels depending on your delivery and support workflow.
Why is save blocked?
Crisp is enabled but the Website ID is missing or not in valid UUID format.
Can support agents use Crisp without broad admin access?
Yes, when roles and product access are configured correctly. See use sales access as a support agent.