Skip to main content

Quick Call Introduction

📌 Overview: What is the QuickCall JavaScript Tag?​

QuickCall is a lightweight JavaScript tag that seamlessly integrates with your website’s contact or inquiry page, enabling rapid follow-up via MicoVoice’s AI calling system.

Designed to capture and convert inbound leads in real time, it empowers businesses to respond to inquiries even after business hours, including nights and weekends. By embedding the tag, any visitor who submits a form can automatically trigger an AI-initiated call, dramatically improving response speed and ensuring no lead is left unattended.

For Sales and Support teams, QuickCall means fewer missed opportunities and more efficient workflows. It allows Sales reps to focus on high-priority conversations while AI handles routine qualification, appointment scheduling, and follow-ups.

QuickCall is fully integrated with MicoVoice campaigns, so leads generated through the JavaScript tag flow directly into your call workflows. This makes it easy to track performance, automate actions based on lead behavior, and scale your outreach without expanding headcount or sacrificing customer experience.

Quick Call Setup

🛠️ Step 1: Setting Up a Call Flow Campaign in MicoVoice​

  1. Create and configure a callflow.
  2. Configure the necessary custom parameters that you would like to use in your callflow and are able to pass to the Quick Call javascript tag.

🌐 Step 2: Embedding the Tag on Your Website​

  1. Go to the Quick Call page.
  2. Provide at least one trusted site URL (example: https://mytrustedsite.com) and your quick call tag will be generated. Setting up allowed trusted sites allows us to make sure that calls can originate only from the places you want them to.
  3. The Quick Call tag consists of two parts:

    1. the tag body that looks like this:

      <script>!function(){const e=document.createElement("script");e.src="https://api.micovoice.com/api/v1/quick_calls/tag",e.async=!0,e.type="text/javascript",document.head.appendChild(e),window.__MV_DATALAYER__=window.__MV_DATALAYER__||[],window.mvtag=(e,t)=>{__MV_DATALAYER__.push({eventType:e,eventData:t,token:"[token]..."})}}();</script>
      <script

    2. the call to mvtag function that fires off the actual phone call:

      <script>
      mvtag("quick_call", {
      "full_name": "[[氏名]]",
      "last_name": "[[姓]]",
      "first_name": "[[名]]",
      "phone_number": "[[電話番号]]",
      "event_date_time": "[[イベント日時]]",
      "phonetic_full_name:": "[[よみがな（氏名）]]",
      "phonetic_last_name": "[[よみがな（姓）]]",
      "phonetic_first_name": "[[よみがな（名）]]",
      "custom_parameters": { "my_custom_field": "[[my_custom_field]]" }
        });
      </script>
  • If you place the both tags as provided in the UI, the call will go off as soon as the second JS tag executes. If you want to execute your call at a different timing, just delete the second tag and call the mvtag function with the necessary parameters when you’d like it to happen.
  • Fields in the JS tag like "lastName": "[[姓]]", correlate to the custom callfow parameters you configured during Step 1, and making sure all the required parameters are provided is crucial for the tag to work correctly. The parts that look like "[[姓]]" are dynamic and are meant to be replaced by you with the actual values that could come from the form inputs themselves, your data layer or any other similar source.

🧪 Step 3: Testing the Integration​

  • To make the calls be made in the sandbox mode do the following:

    • Enable the Sandbox mode in the API Settings page.

    • Enable the QuickCall tag and the callflow.

    • Supply a corresponding parameter to the mvtag function:

      <script>
      mvtag("quick_call", {
      "last_name": "[[姓]]",
      "is_sandbox": true,
      ...

    • A simulated sandbox call should fire off without making the actual phone call. The data from this call will appear in your call list table in the UI.

    • If you want to make the regular calls again remove the isSandbox parameter from the mvtag function and disable the Sandbox mode in the API settings.

    • Note: if you do not make sure to disable the sandbox mode in the API settings your production calls will not appear in the call list table.

Step 4: Controlling the Quick Call tag from the UI​

  • You are able to disable the Quick Call tag from the UI without removing the JS tag if you need to urgently make sure that the calls are not happening.
  • Additionally, if you believe that the JS tag has been leaked or compromised you can regenerate the tag and the old one will stop working from that point onwards.