How We Build New Member Onboarding Workflows

Turn day one into a relationship

A new member onboarding workflow welcomes members the day after they join and guides them toward the products and services that make the credit union their primary financial home.

Why it matters: The first 90 days set the tone for the whole relationship. Members who add direct deposit, digital banking, or a debit card early are more likely to stay and grow. With the right datestamps, you can show which of those actions happened after onboarding began.

How the workflow is built

Enrollment trigger — The member's membership open date is yesterday. Most core integrations push data once a day with the previous day's activity, so "yesterday" catches every new member in each daily sync.

Suppression — We keep this light so every eligible new member gets the welcome. We exclude only the standard non-marketing groups:

• Hard bounces
• Unsubscribes
• Members flagged "do not market" (or equivalent) in your core

Re-enrollment — Off. Members are onboarded once.

Goal — Usually none. Onboarding is a welcome series, not a single conversion. If you want members to exit early once they've done everything (e.g., added direct deposit and enrolled in digital banking), we can set that as the goal.

Workflow steps:

1. Set enrollment datestamp — Set "Date Enrolled in New Member Onboarding" to the current date. (Needed only if you want reporting, but we recommend it every time.)
2. Email series — Typically 4–6 emails over the first 60–90 days, each focused on one action: welcome, digital banking, direct deposit, debit card, eStatements, and a relevant next product.
3. Optional branches — If/then branches skip emails for things the member already has (e.g., no direct deposit email if direct deposit is already set up).

Data requirements

Required:

• Membership open date — From your core, on the  member object), updated daily.
• Membership status — Open/active vs. closed, so we never welcome a closed account.
• Marketing eligibility flag — Your core's "do not market" or opt-out indicator.
• Valid email address from the core.

Required for reporting:

• Enrollment datestamp — "Date Enrolled in New Member Onboarding" (date picker, contact object).
• A datestamp for every product or feature you want to track — For example:
  • "Date Direct Deposit Added"
  • "Date Digital Banking Enrolled"
  • "Date eStatements Enrolled"
  • "Date Debit Card Activated"
  • Open dates on any product deals or objects (loans, credit cards, certificates)

These dates come from your core integration when available. If the core only sends a yes/no flag (e.g., "Has Direct Deposit = Yes"), we build a separate HubSpot workflow that sets the date the moment that flag changes.

Helpful:

• Product holdings at open — So branches can skip what the member already has.
• Branch or channel of origin — For segmenting reporting (branch, online, indirect).

Pre-launch checklist

• Membership open date confirmed in HubSpot and updating daily
• Trigger uses "open date is yesterday" (adjusted if your sync schedule is different)
• Membership status filter excludes closed members
• Suppression in place: bounces, unsubscribes, core "do not market"
• Re-enrollment off
• Enrollment datestamp action is the first step
• Every tracked product/feature has a datestamp (from the integration or a HubSpot workflow)
• Any HubSpot datestamp workflows built and turned on before onboarding goes live
• Emails reviewed, approved, and links tested
• Attribution window agreed (often the length of the series, e.g., 90 days)

How we report on it

What we compare: "Date Enrolled in New Member Onboarding" vs. each product/feature datestamp.

How it's built: A formula field for each tracked item checks whether the item's date falls after the enrollment date and within the attribution window. Members who meet that criteria count as having adopted that product or service during onboarding.

Typical dashboard tiles:

• New members enrolled (by month)
• Adoption rate during onboarding, by product/feature (e.g., % who added direct deposit)
• Products opened during onboarding, by product type
• Email engagement by step
• Optional: adoption among members who clicked a specific email vs. those who didn't

Important Notes & Limitations

• "Yesterday" depends on your sync — If your integration runs on a different schedule, or skips weekends, we adjust the trigger so no new member is missed.
• Flags aren't dates — A yes/no field tells us whether a member has something, not when they got it. Without a date, we can't attribute it to onboarding.
• No backfill — Datestamps only capture activity from the day they're set up. Members onboarded before then can't be reported on.
• Products held at open won't count — If a member opened checking and set up direct deposit on day one, that adoption happened before onboarding began.