Getting off the plane in Finland came with a slew of interesting conversations in the metropolitan area back in October 2022 regarding digital infrastructure and continued strides for SaaS representation. During a practical customer case, a specific trigger for account closures at local co-operatives was highlighted as remaining undone. Here we highlight a pre-production macro written in the scripting language jinja using dbt. Think of a jinja macro as the type you may be used to in Microsoft Excel / using VBA.

Value creation & payback of these implementations is made tangible in the Customer Service and Corporate Relations practices through an upwards double-digit percent gain in retention and potential recovery of lost customer files. Understanding the specific date or source of a closure has an upstream effect on whether a team can assess the (a) seasonality or reason for the closures and (b) pave downstream use cases in the reasons for it (e.g. death of a relative, new institution, etc.). CRR can be calculated using tools from ZenDesk and others.

Perhaps we can have a strong sit-down about whether this labour is on equal footing in the Northern European landscape with respect to critical infrastructure contributions, as I am giving this away “free-of-charge”. Thoughts welcome, and I hope it will help you on your dbt journey. Save time on clogged Outlook instances yesterday and see whether you can drive higher customer retention on Monday.

{% if account_status == 'closed' %}
{% set closure_reason = 'Customer request' %}
-- Encapsulate the next line as a separate jinja macro
{% set closure_date = '2024-03-31' %}
{% set closure_message = 'Your account has been closed as per your request. If you have any questions, please contact customer support.' %}
{% set closure_notification = {
'subject': 'Account Closure Notification',
'recipient': '{{ customer_email }}',
'body': closure_message
} %}
{% endif % }