Loop Voice
    CRM

    Loop Voice for HubSpot: CRM events start AI calls

    Connect HubSpot and its contact, company, deal and ticket events can start Loop Voice flows: an AI agent calls a new lead who asked to hear from you, or calls back a shopper whose ticket needs a conversation. Authorization happens on HubSpot, with no API key, and synced HubSpot contacts show in Loop Voice.

    What it does

    Starts
    Flows from HubSpot contact, company, deal and ticket events.
    Lists
    Lead triggers in the same event picker, next to the CRM events.
    Syncs
    HubSpot contacts, which show up in Loop Voice.
    Tracks
    Events skipped because the contact can't be contacted, in a banner.
    Applies
    Your do-not-contact list, your calling hours and the limit of 3 outbound calls per customer in 24 hours to every call a HubSpot event starts.

    How to connect

    1. 1

      In Loop Voice, open Settings, Integrations, HubSpot and connect. HubSpot shows a screen where you pick the account and grant access (HubSpot on OAuth installs); there is no API key to create.

    2. 2

      Connect as a HubSpot Super Admin or a user with App Marketplace access, which HubSpot requires for installing apps (HubSpot on installing apps).

    3. 3

      Create a flow and choose its trigger in the event picker: a contact, company, deal or ticket event, or a lead trigger.

    4. 4

      Add the steps that follow: a wait if you want one, the call, and a text with the link the lead needs.

    5. 5

      Keep the call step in Draft or Manual while the first events arrive, check who entered the flow and what the skipped-events banner shows, then switch the step to Live.

    Lives in Settings, Integrations, HubSpot. To disconnect from HubSpot's side, uninstall Loop Voice under Settings, Integrations, Connected Apps in HubSpot (<a href="https://knowledge.hubspot.com/marketplace/install-apps-in-the-hubspot-marketplace" target="_blank" rel="noopener">HubSpot on installing and uninstalling apps</a>).

    What you can do with it

    Match the HubSpot event to the call

    EventUse it whenWatch for
    Contact eventA form that asks for a call adds people as contactsImported contacts and newsletter sign-ups never asked for a call
    Lead triggerYou track people who asked for a call as leadsFire the trigger once with a test lead and your own number before you rely on it
    Deal eventYou track quotes or sales-assisted orders as dealsThe deal's contact needs a phone number
    Ticket eventA shopper's question would go faster by phoneComplaints and refund disputes are better left to your support team
    Company eventWholesale or business accountsA company isn't a person, so test one before you rely on it

    Start with one event and one flow, read the first calls, then add the next.

    Only people who agreed to calls

    Loop Voice doesn't cold-call. A lead in a Loop Voice flow is someone who filled in a form and agreed to be called, and an AI-voiced sales call needs prior express written consent. Collect it with a clear, unchecked box on the form that names your store, covers calls made with an AI or prerecorded voice and says agreeing isn't a condition of buying. Our guide to calling rules shows an example; confirm the wording with counsel.

    Collecting and proving that consent stays with you. If the event you picked could also fire for an imported contact or a newsletter sign-up, choose a narrower one before you switch the call step to Live.

    Read the skipped-events banner in week one

    When a HubSpot event arrives for a contact Loop Voice can't contact, the flow skips it and a banner keeps track. Read that banner during the first week: if skipped events keep piling up, check whether the form or import behind those contacts collects a phone number at all.

    A lead flow from form to call

    Example: an e-bike store's "Talk to a rider" form in HubSpot asks for a phone number and has an unchecked box agreeing to calls from the store, including AI calls. The flow starts on the contact event that form produces and runs three steps: wait 5 minutes, call, then text.

    On the call, the agent answers range, frame size and delivery questions from the store's pages. The text carries the model's page and the store's test-ride booking link. If nobody picks up, the flow still sends the text, and if the rider says stop, the number lands on the do-not-contact list before the text step runs. The lead follow-up use case covers the rest of the play.

    FAQ

    Common questions

    Do I need a HubSpot API key?

    No. You approve Loop Voice on HubSpot's own screen when you connect, and there's no key to copy. If HubSpot won't let you install apps, ask a Super Admin to connect.

    Why didn't a HubSpot event start a call?

    Look at the skipped-events banner first: events for contacts Loop Voice can't contact are skipped and tracked there. If the event wasn't skipped, the call may be waiting for your calling hours in the customer's time zone, the number may be on your do-not-contact list, or the customer may already have had 3 outbound calls in the last 24 hours.

    Should every HubSpot ticket get a callback?

    No. Call when a conversation settles it faster than email: a pre-purchase fit, sizing or compatibility question from someone who agreed to calls. Leave complaints, refunds and threads your team is already answering in writing to your support team. More in the ticket callback use case.

    Can I call a HubSpot list as a campaign?

    Not directly. Campaign audiences come from Shopify, Klaviyo or Omnisend segments; HubSpot's job is to start flows from events. To call a HubSpot list once, export the people who gave call consent and start a flow from a CSV upload, which maps your columns and controls who is enrolled.

    Related integrations

    Connect HubSpot to Loop Voice

    Setup takes under 10 minutes. No code, no headcount.