Currently the new DUNNING_REMINDER event only contains the subscription ID.
If the DUNNING_REMINDER event data was extended to include the same or similar of what FAIL_RENEW_SUBSCRIPTION contains then more context specific emails could be sent and we could utilize Arc Subs smart dunning configuration to only send emails on certain steps.
For example.. Currently using the FAIL_RENEW_SUBSCRIPTION event I can send a first email "Oops there was a mixup and your payment did not go through. Please update your CC.... etc". On the next to last fourth email send "Urgent... access will be lost.... etc".
You can do this today with FAIL_RENEW_SUBSCRIPTION because the fail reason and attempt number is included in event. https://dmn.arcpublishing.com/alc/arc-products/arc-subscriptions/release-notes/listening-to-arc-events-using-web-sockets/#fail-renew-subscription
This cannot be done with the new DUNNING_REMINDER event. Currently since we are using the FAIL_RENEW_SUBSCRIPTION event, a code change is required in order to turn off or on an email reminders.
Richard
Thanks, Richard -- Let me sync with the team when Jessica is back later this week to see what's possible here.
Attempt is needed otherwise the feature does not make sense to have.
How do you know what kind of message to send if you don’t know which step the user is on in dunning?
Why even have a separate controlled setting for contacting the customer or not?
Yes I am aware that the step is part of the failed renewal event and that is what we are using. We will have to continue using that event instead of the dunning reminder and make code changes when we want to turn off or on a message.
Unfortunately, this data is not available for inclusion in the websocket and the ALC article was incorrectly updated. I'm sorry for the back-and-forth here.
Thanks for creating a ticket! The support engineer is investigating currently
Hi Richard -- I'm sorry to hear you aren't seeing the step value. I'll flag this for the team but could you please open an ACS ticket? Thanks!
I am not seeing attempts in socket messages for dunning reminders
Here is an example from today.
a:5:{s:14:"subscriptionID";i:5286450016160889;s:11:"declineType";s:11:"SoftDecline";s:18:"numberOfRetryRules";i:7;s:11:"gracePeriod";i:0;s:7:"dueDate";i:1674687018000;}Nice... I will check it out.
Hi Richard. This was shipped with release 1.71 on Jan 19, 2023
Thanks for this idea! I think it makes sense as an extension to the existing events. We'll review it with the team.