Outcome. Every contact that becomes a customer lands on one static list, giving marketing and CS ops a single, stable count and roster to build reports and dashboards from.
flowchart TD
A[Lifecycle stage becomes Customer] --> B[Add to New Customers - Onboarding Reporting list]

When to use it, when not to
- UseUse it as the simplest possible reporting building block, when no dedicated onboarding tracking exists yet on the contact object.
- UseUse it alongside the deal-based fiches in this category, a static list at the contact level often makes marketing reporting easier than pulling from deal records directly.
- SkipDo not use it if the team already reports off
Lifecycle stage = Customerdirectly in a saved report or list, a static list adds a second source of truth that has to be kept in sync with no extra benefit in that case. - SkipDo not use it if one contact can represent multiple deals or accounts over time, the list will count the person once, not once per deal, decide up front whether that matches what the report needs to answer.
or the customer onboarding pack, 39 EUR
One-time, excl. VAT. 30-day refund, no questions asked. Founding prices until 31 October, then 199 and 59 EUR. Includes every spec added later, up to the full 500, and the one-click installer on the full library. Building on client portals? The agency licence at 449 EUR covers unlimited client portals.





