Troubleshooting

Product not loading, or visitors see "not found"

• Check Publish Product is on in Product Settings → Deployment → Publishing & Visibility. The switch stays greyed out until the product's workflow is complete.
• An unpublished product only opens for the person who created it, while logged in. Teammates and visitors see "not found" — unless they use the product's demo link (ending in ?demo=true).

Product won't show when embedded on my website

• Add your site's domain (for example example.com) to Allowed Domains for Embedding in Product Settings → Deployment. Subdomains are included automatically.
• If the field is empty, the product can't be embedded on other websites.

"You've reached your live products limit" when publishing

• Your plan allows a set number of live products. Switch off Publish Product on one you no longer need, or upgrade your plan.

A lead is missing from my results

• A lead is only recorded once the visitor sends their first message. Opening the page or reading the welcome screen doesn't create one.
• Check the workspace's Data retention setting in Settings → Client settings — leads older than the period you set are removed in a daily clean-up.
• Make sure you're in the right workspace. Each workspace has its own products and leads.

Test runs are showing up as leads

• Runs from the demo link (?demo=true) are test runs. They're marked Test in Analytics → All Results, and they show in your analytics by default, so a new product looks populated when you demo it.
• To leave them out, switch on Hide test runs at the top of the product's Analytics. It applies to the whole workspace: every product's analytics, the dashboard, the Brain map and exports.
• Test runs never use up a submission cap. You can also delete them one by one from All Results.

My webhook, Zapier or lead email didn't fire during a test

• That's expected: test runs from the demo link (?demo=true) never send lead emails, notifications, webhooks or Zapier data, so a demo can't push fake leads into your inbox or CRM. The page shows a small Test mode label while you're on a demo link.
• To check an integration, use Send Test in Product Settings → Webhook, or complete the product from its live link (without ?demo=true).

AI conversation feels off or generic

• Review your instructions on the AI Product node, under Conversation → Collection Instructions. The more specific you are about the AI's role, your audience and the tone, the better the conversation.
• Check each question under Conversation → Questions is clear — vague questions get vague answers.

Product replies in the wrong language

• Open the AI Product node and set Conversation → Collection Instructions → Language. On Auto, the product follows the language your instructions are written in, so English instructions give an English product.
• The setting covers the questions, the AI Agents' analysis and the result page, so you don't need to repeat "reply in German" in every prompt.
• Building with Claude? Just say "Set the language of [product name] to German."

Result page doesn't appear at the end of a test run

• Publish the product and run through it again from the live link.
• To test before publishing, use the product's demo link (ending in ?demo=true). A run started from that link goes all the way through to a Standard or Page result. Document results from a demo run only open for the product's creator.

Outcome not generating after the conversation ends

• Open the AI Product node's Outcome tab. Check Continue to outcome is selected, and under Output format pick the output you've connected — Standard, Page, Advisor Chat or Document. A format with nothing connected shows (Add node).
• Confirm the output node (Standard, Page, Advisor or Document) is connected to the AI Product node on the canvas — a line should run between them.
• Check your credit balance under Settings → Account & billing → Subscription → Usage, or that your own key is working in Settings → AI & connections → Claude API Key.

Visitors see "This assistant isn't available right now" or "we couldn't reply just now"

• The AI couldn't respond. The most common causes are your account running out of Productised credits ("isn't available right now"), or a rejected Claude key or an Anthropic account out of credit ("couldn't reply just now"). Visitors' answers are still saved, and Owners and Admins get a notification saying which.
• Check your notifications, then Settings → AI & connections → Claude API Key and your balance under Subscription → Usage. A replaced key or new credits work straight away — there's no need to republish.

Custom domain isn't working

• Check the DNS record at your registrar matches the one shown in Settings → Client settings → Custom Domain exactly: a CNAME to productisedai.fly.dev for a subdomain, or an A record to 66.241.125.89 and an AAAA record to 2a09:8280:1::6b:61da:0 for a root domain.
• DNS usually updates within 5–30 minutes, but can take up to 24 hours. Then click Check status — it issues the HTTPS certificate and activates the domain. This applies to domains set up through Claude too.
• A product without a web address opens at yourdomain.com/c/<product-id> instead of yourdomain.com/product-name. New products get one automatically; set or change one next to the product on the Custom Domain page, or ask Claude.

Productised branding still shows on my pages

• The "made by" badge shows Productised until you add your own logo and link in Product Settings → Branding (paid plans), or ask Claude to set custom branding.
• Set a favicon in Product Settings → Page SEO, or a default favicon for the whole domain in Custom Domain settings.
• Set your own share image in Page SEO so link previews show your brand.

The AI disclosure isn't showing on a product

• Check Show AI disclosure is on in Settings → AI & connections → AI Disclosure.
• Check the product is ticked under Products on the same page. Products created before the disclosure launched start unticked.
• No "Privacy Policy" link? Add a link or write your policy on the same page — without one, the line links only the AI Notice.

Claude changed the wrong workspace

• The connector works in the workspace you last had open in the app. Switch workspace in the app, then ask Claude again.
• If Claude can't find a product, its reply names the workspace it's working in — check that's the one you meant.

I can't see a setting

• Some settings are for Admins only: Subscription, Usage & cost, the Team, Claude and API keys, Data retention, AI Disclosure and Logs.
• Ask the account owner or an Admin to change your role in Settings → Account & billing → Team.

Lead emails aren't arriving

• Check Lead Notifications is on in the product's Settings → Deployment. It's off by default and set per product.
• Emails are sent when someone completes the product, not when they start. Check your spam folder.

Webhook not receiving data

• Check Enable outgoing webhook is ticked in Product Settings → Webhook, then use Send Test to confirm your endpoint is reachable.
• Webhooks fire when a lead completes the product. Use an https:// address.
• A webhook switches itself off after 5 failed deliveries in a row. Fix the endpoint, then switch it back on.
• If you're using Zapier, make sure the Zap is on and the trigger URL is the latest one from your Zap.

MCP node not working

• The server must be reachable on the public internet over https://. Addresses on private or internal networks are blocked for security.
• Check the access token you entered is current, then use Test Connection in the node's settings.