Set up customer support on your website.

This walkthrough takes an HTML or React / Vite website from no chat to a tested conversation in your Macaron inbox. You need permission to edit and publish the site. A model key, repository connection and payment account are not needed for chat.

Add your website free

By Macaron · Updated

1. Add your website and enable chat

Sign in to Macaron, open Apps and choose Add app. Select Website, enter its name and HTTPS address, then review and create it. You can leave the code repository empty until you need a coding run.

Open the saved website and choose Set up chat. Enable customer chat, then choose HTML / website or React / Vite under Your framework. Setup fills in your public app ID and Macaron server address. Use the snippet from your own workspace; YOUR_APP_ID below is a placeholder.

Adding a website address lets Macaron inspect public HTML. It does not install chat, import existing visitors or give Macaron access to private analytics or payments.

2. Paste one script and publish

For a plain HTML site, paste the script once before the closing body tag in your shared page template. For React / Vite, put it in index.html before </body>, outside your React component tree. No React package or extra backend endpoint is needed for basic chat.

For a site builder that permits custom scripts, use its site-wide footer-code setting and publish the change. A field that renders scripts as text will not install the widget. If your builder cannot execute custom scripts, this installation path will not work there.

Keep one copy per page. Publish to a staging site you control first, then test the deployed page. A local edit or a pasted snippet in Macaron does not change your live website.

<script src="https://macaron.sh/macaron-support.js?v=notice-1" data-app="YOUR_APP_ID" defer></script>

3. Verify a message and a reply

Use a separate customer browser window so you can test both sides. Keep this a clearly labeled test, without real customer or payment data. The launcher appearing is only the start of this check.

  1. Open the published website, open chat and send: ‘Setup test — can the team reply on this website?’
  2. In Macaron, open that website’s inbox. Confirm the test arrived under the correct product, then send a short test reply.
  3. Return to the customer chat and keep it open until the reply appears. In Set up chat, use Check delivery: customer message received, team reply sent and reply loaded should all be confirmed for the conversation.
  4. Navigate to another page and refresh. Confirm that the conversation remains accessible and that only one launcher is present.
  5. Repeat on a phone-sized viewport. Check that you can open, type, send and close chat with the keyboard and that chat does not cover a required site action.

If the launcher or messages do not appear

If there is no launcher, check the published page, not just your editor. Confirm that the script uses your app ID, chat is enabled for that product and macaron-support.js loads successfully in browser developer tools. Remove a duplicate script before testing again.

If the script loads but chat cannot connect, inspect the request to /api/support/apps/YOUR_APP_ID/config on your Macaron server. A wrong ID, disabled chat, network failure and an empty inbox need different fixes. Read the returned error before changing the code.

If your Content Security Policy blocks the widget, use the reported violation to configure the script, API connections, widget styles and configured logo within your existing policy. Keep HTTPS and your site’s security policy. A consent manager or browser extension can also prevent loading; test with your intended consent settings and a clean browser profile.

If the customer message arrives but the reply is missing, return to the same conversation in the customer browser. Clearing browser storage or starting a new conversation changes which conversation is open. A hosted test chat can help isolate delivery from installation, but it does not verify the script on your site.

4. Turn a real problem into a useful report

Once installation works, respond to a customer question in the inbox. For a bug, ask for the affected page, browser, the steps before the failure and the expected result. Create a fix report from the conversation so the evidence remains attached to the website.

Saving a report does not start an agent. When you need code work, use Connect code and model, verify repository and provider access, choose a compatible machine and enter your actual project checks. Review the change and repeat the customer’s steps against the release before marking the report resolved.

After a verified fix is released, publish a customer-facing fix update. Optional email and push updates require configured delivery providers and separate customer opt-in. Installing chat alone does not enable them or prove that a customer’s problem was solved.

What you need for the first conversation

Free includes customer chat and reports for one app or website. You can complete the message-and-reply check before connecting a model, code repository, revenue provider or cloud machine. See current pricing for Pro limits and separate provider costs.

The app ID in the script is public routing information. Keep owner sessions, model keys and billing credentials on the server. Site analytics and payment imports are separate owner-controlled connections; a successful chat installation does not establish visits, revenue or churn reduction.