HubSpot training session with BluePoint covering CRM property strategy, a new Contact Type field, CallRail integration planning to replace the POP answering service, and drip campaign architecture for traditional vs. reverse ATM sales. Attendees included Wade Zirkle and Mike Stebbins (BluePoint) and Avokerie Onorimuo, Mark Hope, and Melissa Cusumano (Asymmetric).
Meeting recording: Fathom
Lead Status in favor of Lifecycle Stage for all reporting and automation. Lead Status may remain visible temporarily but should not be populated going forward.Disqualified to Lifecycle Stage. A new Disqualified option was added to the Lifecycle Stage property to formally remove contacts from active campaigns without deleting them.Contact Type property. A new custom dropdown property was created to segment contacts by relationship type. Agreed options: Leads, Customers, GPO Partners, Vendors. Vendors were included to maintain a central communication record.Product property and excluding disqualified contacts.Problem: The CRM used both Lifecycle Stage and Lead Status in parallel, creating confusion and redundant data entry. Lifecycle Stage was not visible in the contact sidebar for most records.
Resolution:
- Lifecycle Stage added to the contact sidebar and moved to a prominent position.
- Lead Status left in place temporarily; Mike will stop populating it and evaluate removal after contacts are migrated.
- Disqualified stage added to Lifecycle Stage to handle contacts who should be excluded from all outreach.
Sidebar customization note: Changes made by Mark in his HubSpot session may only apply to his view. Mike needs to verify his own sidebar reflects the same layout and replicate the changes if not. Wade's view may also differ.
Bulk editing contacts:
1. Create a filtered list view (e.g., Active Leads — filter by Lead Status = active values).
2. Set page size to 100 to see all records.
3. Select all contacts.
4. Use Edit to update a property (e.g., set Contact Type = Lead) across the entire group at once.
A new custom property was created from scratch in HubSpot (Settings → Properties → Create Property):
| Option | Notes |
|---|---|
| Lead | Anyone not yet a customer being actively pursued |
| Customer | Existing paying customers |
| GPO Partners | Organizations like Integra that refer leads; partners, not vendors |
| Vendors | Companies BluePoint pays (e.g., service providers) |
Mike will begin bulk-updating existing contacts with this property. The Active Leads list view was configured to display Contact Type and Lead Status columns side by side to facilitate this work.
Problem: POP answering service costs $300/month and is not performing well. Calls from ATM sticker numbers are mostly support/complaint calls, not sales leads, making AI answering a viable replacement.
Planned use cases:
| Use Case | Approach |
|---|---|
| ATM support numbers | Port/forward existing sticker numbers through CallRail → forward to AI answering service. CallRail records calls for monitoring and AI optimization. |
| State page lead tracking | Assign unique local-area-code numbers to key state landing pages to attribute inbound leads and build local trust with prospects. |
| Outbound sales calls | Use CallRail numbers for outbound dialing to avoid spam flags and enable call recording. Numbers can be rotated if burned. |
HubSpot integration: CallRail is already connected to BluePoint's HubSpot account (installed by Mark). When a caller's number matches a HubSpot contact, the call is automatically logged to that record. Unmatched numbers require manual association.
Call recording: Included in the base CallRail plan at no extra charge. Transcription is available for an additional fee and is recommended for quality monitoring.
Next step: Wade will email Mark (cc Leslie) with a full requirements list. Mark will respond with a setup recommendation. Leslie handles the existing number routing and will need to be looped in for any forwarding changes.
Wade has a Fathom Premium subscription ($200/year) but cannot add Mike as a team member. The suspected cause is that the plan is a single-user "Premium" tier rather than a team plan. Wade and Mike will investigate offline and resolve outside this session.
The HubSpot ↔ LinkedIn Sales Navigator integration requires the Advanced Plus tier. LinkedIn requires a minimum of 10 seats for this plan, making it cost-prohibitive for BluePoint's current team size (~2 sales seats). Pricing is not published; a sales call is required.
Wade will contact LinkedIn again to negotiate a smaller minimum seat count or explore alternative pricing.
Contact Type = Lead for existing active contacts; add Lifecycle Stage column.Contact Type property.