Skip to content
September only: install your Web Assistant in one click.See the campaign
Azamol AI — Intelligent Assistance Solutions

AZAMOL AI ASSISTANT

Add your assistant to your site

Five steps, ten to fifteen minutes on average. The same steps apply no matter what theme, plugins or hosting provider your site uses.

What you need before you start

  • Your public key — a short string starting with az_pk_. You’ll find it in the Embed Code tab of your Assistant Panel.
  • Your website’s domain — the address your assistant will run on (e.g. example.com).
  • Access to your site’s HTML — a theme editor, a custom code area, or a plugin.
Open your Assistant Panel

Your key isn’t secret

The public key is visible in your page’s source code, and that’s normal. On its own it does nothing: the assistant only opens on domains you’ve verified. If someone copies your key onto their own site, the assistant simply won’t render there.

Installation

  1. Verify your domain

    In your Assistant Panel, go to the "Domains" tab and add the domain your assistant will run on. You can choose either verification method: a DNS TXT record specific to your domain (the record name follows the pattern `_azamol.<your-domain>`), or a verification file you upload to your server (`https://<your-domain>/.well-known/azamol-dogrulama.txt`). Either way, the panel generates the value you need — just copy it with the copy button.

    The assistant won’t appear anywhere until your domain is verified — that’s exactly what protects your key from being used on other sites. If you use more than one address (e.g. example.com and www.example.com), add and verify each one separately.

  2. Publish a persona version

    Set how your assistant talks in the "Persona" tab and publish a version. The assistant can’t go live without a published persona version.

  3. Publish your assistant

    Once your domain is verified and a persona version is published, click the Publish button in the "Settings" tab. This step takes your assistant from draft to live — even if the embed code is already on your site, the assistant stays hidden until you publish.

  4. Paste the embed code into your site

    Add the line below right before your page’s closing </body> tag. You can copy your own key from the "Embed Code" tab in your Assistant Panel.

    <script src="https://azamol.ai/embed/v1.js" data-azamol-key="az_pk_XXXX" async></script>

    The code needs to be on every page, so the most practical place is your theme’s footer. You’ll find where to paste it for your specific platform below.

  5. Refresh the page and check

    Open your site. A round button should appear in the bottom-right corner. Clicking it opens the assistant window — the assistant only loads at that moment, so visitors who never open it aren’t loaded with anything extra. If something’s off, see the troubleshooting section below.

Your site must run on HTTPS

The assistant only works on sites served over https://. If your site is still on http://, enable your SSL certificate first — nearly every hosting provider offers this for free today.

If you use voice messages: microphone permission

For visitors to send voice messages, your site's Permissions-Policy header must not block microphone access. If your server already sends a restrictive header (some security plugins and CDNs add one by default), define the permission below:

Permissions-Policy: microphone=(self "https://azamol.ai")

Without this permission only the voice message feature stops working — text chat and image sending are unaffected, and the visitor sees a clear warning when they tap the microphone icon.

What can a visitor send the assistant?

Alongside text, the assistant accepts images and voice messages. Visitors don’t need to install anything — it all works inside the chat window.

  • Images: JPG, PNG, WebP or GIF, up to 5 MB each. A visitor can send a product photo, a screenshot or a picture of a document and ask about it.
  • Voice messages: recorded with the microphone button, up to 60 seconds. For visitors who’d rather not type, or who are moving fast on a phone.
  • One attachment per message — an image and audio can’t be sent together.

A message with an attachment still counts as a single message against your quota. There is no surcharge for sending a photo or a recording.

Where to paste it, by platform

WordPress

  1. In the admin panel, go to Appearance → Theme File Editor.
  2. Open the footer.php file.
  3. Paste the code right above the </body> line.
  4. Save.

To keep it from being lost on a theme update, it’s safer to use a code-insertion plugin like WPCode or a child theme.

Wix

  1. Go to Settings → Custom Code.
  2. Click Add Code and paste the code.
  3. Set the placement to Body — end.
  4. Save it so it applies to all pages.

Shopify

  1. Go to Online Store → Themes → Edit code.
  2. Open the theme.liquid file.
  3. Paste the code right above the </body> line.
  4. Save.

Webflow

  1. In your project settings, go to Project Settings → Custom Code.
  2. Paste the code into the "Footer Code" field (Before </body> tag).
  3. Click Save Changes and republish your site (Publish) — the code only goes live after you publish.

This field is only available on paid publishing plans; it may not work in the Designer preview.

Squarespace

  1. Go to Settings → Advanced → Code Injection.
  2. Paste the code into the "Footer" field — this runs on every page of your site.
  3. Save.

Code Injection may be disabled on some entry-level Squarespace plans; check your plan if you don’t see it.

Your own HTML site

  1. Open each page’s HTML file.
  2. Add the code right above the closing </body> tag.
  3. Upload the files to your server.

If you have a shared footer template, adding it there is enough.

If the assistant doesn’t appear

Work through these in order. Most cases come down to one of the first two rows.

SymptomLikely causeFix
No button shows up at allThe code isn’t on the page, or the key attribute is missingSearch your page’s source code for the embed/v1.js line. If it’s missing, the code hasn’t been added; if it’s there, check the data-azamol-key spelling.
I click the button but the window doesn’t openThe domain isn’t verified yet, or the assistant hasn’t been publishedCheck verification in the "Domains" tab and publish status in the "Settings" tab of your Assistant Panel. www and non-www versions count as separate addresses.
The window opens but stays emptyThe address isn’t on the allow-listOpen your browser console (F12) — if framing was blocked, it will be logged there.
It only shows up on some pagesThe code wasn’t added to every pageMove the code into your shared footer template.
It works locally but not in productionThe live address hasn’t been verified separatelyAdd and verify both your test and live addresses in the "Domains" tab.
You’re using a non-standard portAddresses like example.com:8443 count as a separate originAdd the address with its port as its own domain and verify it.
Your site has a Content Security Policy (CSP)The browser is blocking the frameAdd frame-src https://azamol.ai, script-src https://azamol.ai and connect-src https://azamol.ai to your policy.
You’re using an ad blockerThe script may be blockedTry it in a private window with the blocker turned off.

If none of this helps, open your browser console (F12) and send us a screenshot of any lines starting with [azamol-embed].

Which links does the assistant share?

Because we crawl your site during setup, the assistant can include a link to the page its answer is based on — so visitors don’t have to ask where it says that.

  • Only pages on your own domain that were actually seen during the crawl can be shared.
  • If the assistant invents or guesses an address, that link is stripped on the server before it reaches the visitor. This is an enforced rule, not a polite request to the model.
  • At most 2 distinct pages are linked per reply, so answers don’t turn into a list of URLs.

Links open in a new tab — the visitor doesn’t lose the conversation.

What to add to your privacy policy

The assistant processes the messages your visitors write in order to generate replies. Under GDPR/KVKK, you are the data controller and Azamol acts as the data processor on your behalf. That means the consent language and disclosure obligations belong in your own privacy policy.

  • State that your site has an AI assistant and that messages are processed.
  • Remind visitors not to enter sensitive data — ID numbers, health information and the like — into the assistant.
  • State that conversation content is not stored — messages are processed only to generate the reply and are then discarded; Azamol does not keep conversation text and its staff cannot read it.
  • Disclose that messages are processed on cloud infrastructure located outside your country, and cover that transfer in your notice.

Frequently asked questions

Will it slow down my site?▼

No. The file that loads is roughly 7 KB compressed and runs async — it doesn’t wait for or delay your page load. The assistant window itself only loads when a visitor clicks the button.

Will it break my design?▼

No. The assistant runs inside an isolated frame separate from your page; your CSS doesn’t affect it, and it doesn’t affect your page.

Can I use the same key on more than one site?▼

You can add more than one domain; you’ll see your limit in the Assistant Panel. Each address needs to be verified separately.

What if I want to remove it?▼

Just delete the single line you added. It leaves nothing else behind.

Stuck somewhere? Get in touch — we’re happy to help. Contact us