Skip to main content

AI Voice Agent → HubSpot Properties: Setup Guide

This article explains how to map answers collected by the AI Voice Agent to contact properties in HubSpot, so every response your agent gathers during a call is saved directly to the right field in your CRM.

Written by Adriana Świerczek

Note: This feature requires an active and correctly configured HubSpot integration. Without at least one active HubSpot integration, the HubSpot property (internal name) field won't appear next to your questions in AI Voice.

How It Works

For every question configured in AI Voice, you can choose which HubSpot contact property should store the caller's answer.

In AI Voice, you fill in the field:

HubSpot property (internal name)

Once this is set, each answer collected during a call is automatically synced to the corresponding property on the HubSpot contact.

Before You Start: The Property Must Already Exist in HubSpot

CallPage doesn't create HubSpot properties automatically. Before mapping a question, you (or your HubSpot admin) need to create the property manually in HubSpot as a contact property.

Tip: Set up all the properties you plan to use in HubSpot first, then come back to configure the mapping in AI Voice - it will save you a round trip if a property turns out to be missing.


Important Rules

  1. The property must already exist in HubSpot. CallPage doesn't create properties on the HubSpot side. Create it manually in your HubSpot contact property settings before mapping it in AI Voice.

  2. Use the internal name, not the display label. HubSpot shows users a friendly label, e.g., What doing, but the API expects the internal name, e.g. what_doing. Always use the internal name in AI Voice.

  3. The name must match exactly (1:1). The value entered in AI Voice must be identical to the internal name in HubSpot.

    ✅ Correct:

    • HubSpot internal name: what_doing

    • AI Voice field: what_doing

    ❌ Incorrect:

    • HubSpot internal name: what_doing

    • AI Voice field: What doing

  4. Recommended naming convention:

    • lowercase letters

    • no special characters

    • no spaces

    • no accented/national characters

    • ideally snake_case

    Examples: tool_interested, customer_need, what_doing

  5. An incorrect property name can stop the sync. If the name entered doesn't exist in HubSpot, or doesn't match the internal name exactly, the answer won't be saved. In some cases, HubSpot may reject the entire contact update, meaning other data from the same sync won't be sent either.

Example Configuration

Question in AI Voice:

  • Label: What u doing

  • HubSpot property (internal name): what_doing

Contact property in HubSpot:

  • Internal name: what_doing

Result: The caller's answer to "What u doing" is sent to HubSpot under the what_doing property.

Best Practices

  • Create properties in HubSpot first, then map them in AI Voice - never the other way around.

  • Copy the internal name directly from HubSpot rather than retyping it, to avoid typos.

  • Stick to snake_case for any new properties you create, to keep naming consistent and avoid mismatches.

  • Double-check mappings after editing questions - renaming a question's label doesn't change the property mapping, but it's a good moment to confirm everything still lines up.

Did this answer your question?