Set UpDeploying

Step 9: Deploying — Phone Number or Web Widget

A Workflow does not take real calls until it is deployed. Both options are in the top bar of Create Workflow.

Deploy to Phone

  1. Click Deploy to Phone.
  2. Choose one of your account’s available (unassigned) phone numbers from the list.
  3. Click Deploy. On success you’ll see “Deployed to production.”
⚠️

Only phone numbers already provisioned on your account are shown — there’s no self-service “buy a new number” flow inside Create Workflow today. If you need an additional number, contact support.

If you want to move your existing business number onto the agent, that is a planned step with HoloLogix. Do it only after testing is complete and at an agreed time.

Deploy to Web Widget

An embeddable voice-call button for your own website.

  1. Click Deploy to Web.

  2. On the Domain tab, add every domain the widget will be embedded on (e.g. support.example.com, or a wildcard like *.example.com). At least one domain is required.

  3. On the Appearance tab, set (per domain, if you have more than one):

    SettingOptions
    Languageen, de, pt
    Themelight, dark
    Positionbottom-right, bottom-left, top-right, top-left
    Default modecollapsed (closed until clicked) or expanded (open on page load)
    TitleCustom display name (defaults to “MIA Voice Assistant”)
    Animated blobShow or hide the animated visual on the launcher button

  4. Click through to generate your script, then copy it from the Script tab. It looks like:

    <script src="https://your-mia-domain/api/widget?ref=YOUR_REF_TOKEN&lang=en&theme=dark&position=bottom-right&title=MIA%20Voice%20Assistant&mode=collapsed"></script>

  5. Paste that <script> tag into your website’s HTML, anywhere before </body>. The widget only loads on domains you whitelisted in step 2.

The widget’s footer attribution (“Made in Europe by holologix.ai”) is fixed and not configurable.

What your IT needs to know:

  • The page must be served over HTTPS — browsers won’t grant microphone access otherwise.
  • The visitor must allow microphone access. The browser prompt appears on the first click. If it’s denied, no conversation can start.
  • A strict Content Security Policy can block the script. Whitelist the domain accordingly.
  • With cookie and consent banners: check that the widget isn’t blocked, or deliberately wire it into your consent logic.
  • Test on mobile in advance, especially Safari on iOS — microphone permissions behave more strictly there.
  • The widget interface is available in en, de, pt. That only affects the button’s labels — which language your agent speaks is set in the Workflow and is independent of this.

Test before you go live

Use the Call Now button in Create Workflow to place a live test call to your agent at any time, without needing a real deployment first. Continue to Test for how to test properly before you rely on this agent for real customers.

Follow-up (Integration Tab)Overview