Velaro Deployments Guide

What is a deployment?

A deployment is the configuration package that connects Velaro to your website or app. It contains your embed script, team assignment, chat window design, and availability settings. Most businesses use a single deployment — one embed code on every page — and handle all routing logic through Rules.

Getting your embed code

1. Go to Deployments in the left sidebar.

2. Select your deployment (or the default one).

3. Click the Deployment Code tab.

4. Copy the embed script.

5. Paste it just before the </body> tag on every page where you want chat available.

Once the script is on your site, all routing, chat window appearance, surveys, and team assignment are controlled from the Velaro admin — you do not need to touch the website code again.

Installing the embed code

WordPress: Use a plugin like "Insert Headers and Footers" or paste directly in your theme's footer.php file before </body>.

Shopify: Go to Online Store > Themes > Edit Code > theme.liquid, paste before </body>.

Wix: Go to Settings > Custom Code > Add Code > Body - end.

Squarespace: Settings > Advanced > Code Injection > Footer.

React / Next.js / Vue: Add the script via useEffect on mount, or use next/script with strategy="afterInteractive".

Google Tag Manager: Add a Custom HTML tag, paste the embed code, trigger on All Pages.

Deployment settings

Team — which team receives conversations from this deployment by default. Rules can override this.

Chat Window — which chat window design (colors, greeting, avatar) visitors see.

Chat Availability — toggle off if you want to control availability entirely via Rules and schedules.

Passing visitor data to Velaro

Add this block BEFORE the embed script to pre-fill contact information automatically:

<script>
  window.VelaroSettings = {
    contact: {
      name: "Jane Smith",        // visitor's display name
      email: "jane@company.com", // used to match/create contact record
      phone: "+15551234567",     // optional
      customFields: {
        accountId: "ACC-9821",   // any custom field you created in Contact Fields
        plan: "Enterprise"
      }
    }
  };
</script>
<!-- paste embed script here -->

Values passed here appear instantly in the agent's contact panel and are available as variables (<<email>>, <<plan>>) in workflows and AI bots.

When do you need more than one deployment?

One deployment handles almost everything. Rules route conversations to different teams, surveys, workflows, and chat windows based on conditions — without changing the embed code.

You only need a second deployment when you are running completely separate brands or sites that should never share routing, contact data, or configuration — for example:

• A parent company and a subsidiary with different support teams and branding
• A white-label product sold under a different name
• A web chat deployment and a kiosk or in-store tablet with different UI requirements

If you are just routing different pages to different teams, use Rules instead.

Deployment limits

Your plan includes a set number of deployments. The usage banner on the Deployments page shows how many you have used. If you need more, contact your account manager or go to Billing to upgrade.

Removing the chat widget from specific pages

You do not need a separate deployment to hide chat on some pages. Add this before the embed script on pages where chat should not appear:

<script>window.VelaroSettings = { disabled: true };</script>

Testing your deployment

After pasting the embed code:

1. Open the page in a browser (not logged into Velaro).

2. The chat widget should appear in the corner.

3. Click it and send a test message.

4. Confirm it arrives in the Velaro messaging workspace under the correct team.

If the widget does not appear, check your browser console (F12) for JavaScript errors.