Skip to content
English
  • There are no suggestions because the search field is empty.

Momentum (NowCerts) Integration for GloveBoxCRM

Overview

This integration connects your Momentum (NowCerts) AMS to GloveBoxCRM so that contact, policy, and opportunity data syncs between the two systems. By keeping data consistent across these platforms, the integration increases overall agency efficiency while reducing duplicate work for your staff.

The integration supports both one-way or two-way data flows, meaning agencies can control how they want these systems and their information to work together.

How It Works (High-Level)

When configuring the integration, agencies choose whether to:

  • Pull Momentum data into GloveBoxCRM - one-way
  • Push GloveBoxCRM data into Momentum - one-way
  • Or both (two-way) - Momentum ⇔ GloveBoxCRM

Admins can adjust these integration settings at any time.

Once enabled, the synchronization process for each method is ongoing, meaning new or updated data from one system passes into the other either instantaneously or on a cadence of approximately 15 to 30 minutes.

    What Gets Synced

    The integration supports syncing three main types of records between Momentum and GloveBoxCRM: contacts, policies, and prospects (opportunities):

    • Both personal and commercial contacts can sync between systems.

    • Policies are automatically associated with the appropriate contact or business.
    • Prospects in Momentum sync into GloveBoxCRM pipelines as opportunities.

    Because records do not correspond 1:1 across each platform, not all data will sync directly even under a two-way configuration 

    Momentum ⇔ GloveBoxCRM: Synchronization Map

    The below table explains how records from each platform correspond and what data is passed in the integration for each sync method. 

    Momentum Sync GloveBoxCRM Info Synced
    Insured (Personal) Pull + Push Contact 
    (Personal)    		 Name
    Email
    Phone
    Address
    DOB
    Policy Associations
    Insured (Commercial) Pull + Push Contact (Commercial) AMS ⇒ CRM (Pull)
    Business Name
    DBA
    Address
    Email
    Phone
    Policy Associations

    CRM ⇒ AMS (Push)
    Business Name
    DBA
    Address
    Policy Associations
    Policy Pull + Push Policy (or Quote)

    AMS ⇒ CRM (Pull)
    Policy No.
    Line of Business
    Parent Carrier
    Dates - Effective - Expiration
    Premium ($)
    Policy Status → Pipeline Stage
    Contact Associations
    User Associations

    CRM ⇒ AMS (Push)
    Policies & Quotes
    Policy No.
    Line of Business
    Parent Carrier
    Dates - Effective - Expiration
    Premium ($)
    Policy Status
    Contact Associations
    Prospect Pull + Push Opportunity AMS ⇒ CRM (Pull)
    Contact & Policy Association
    Status → Pipeline Stage

    CRM ⇒ AMS (Push)
    Opportunity & Quote Assoc.
    Contact → Prospect
    User Pull Contact & Opportunity Detail AMS ⇒ CRM
    Record:
    -Ownership & Assignment
    -Tasks
    -Notes

    Key Integration Behaviors

    1. Contacts are matched between platforms using email and/or phone data to prevent duplicate record creation.
    2. Policies are matched between platforms by policy number.
    3. Fields without any equivalent structure in the opposite platform are neither pushed nor pulled.
    4. Momentum-side Tasks, Notes, Opportunities & User attribution are strictly one-way (pull), meaning changes to those elmenents in GloveBoxCRM will not reflect in the AMS for any sync method.
      1. For example, changing a contact owner in the CRM will not update the assigned agent on the insured record in Momentum.

    Common Questions

    Do I need to enable both sync methods?
    No. Agencies can choose Pull or Push only if desired.

    When would an agency only want to use one method?
    Typically this is done to accommodate a strategic business or IT decision.
    For example, an agency might want their producers focused strictly on new business vs. service, and would set up the integration as push only so that agents only utilize the CRM while CSRs monopolize the AMS.

    Why are certain updates fast and others delayed?
    The speed of the integration's sync behavior depends on multiple factors such as the direction, number of records affected, and the nature of the update itself.
    For example, updating an existing record is usually instantaneous in either direction, whereas creating new records may take several minutes to reflect in the other platform.

    Related Resources