Misleading anniversary promo, broken handling, and zero billing grace period

[Arthur_Soares]

Hi all,

I’m sharing this publicly because a renewal issue escalated into a blocked account due to misleading marketing, ad-hoc support handling, and a billing system with no grace period.

This is not about the price of the subscription. It’s about process and user experience.

⸻

Timeline
• 18.12.25
Roon sent a “10 Years of Roon” campaign framing a $99 yearly offer as a thank you to customers.
I contacted support asking how existing, paying users could benefit.
• 19.12.25
Support replied that the campaign was not aimed at existing subscribers, only inactive or trial accounts.
• 20.12.25
I replied pointing out the mismatch between the marketing language and actual eligibility.
• 30.12.25
Follow-up sent after no response.
• 09.01.25
Support replied and offered a one-time 30% discount on my upcoming renewal as an individual solution.
• 10.01.25
I accepted the offer and waited for confirmation.
• 17.01.25
The system attempted to charge the full renewal price, not the agreed amount.
The charge failed and my account was immediately blocked.

⸻

Issues exposed
1. Misleading marketing
The campaign was framed as customer-facing while explicitly excluding existing paying users.
2. One-off support workaround
The issue was handled manually, without confirmation or safeguards, creating more risk rather than resolving it.
3. Billing execution failure
The agreed renewal price was not applied before charging.
4. Zero grace period
A single failed charge resulted in immediate loss of access to my library and service. No warning, no retry window.

Being locked out of a music library instantly due to a billing mismatch is an unacceptable user experience.

⸻

Why this is public
• Private support did not resolve this cleanly.
• The “fix” introduced new failures.
• Other users should know what to expect if renewal billing goes wrong.

I’m not asking for a personal exception. I’m asking for clarity:
• Is excluding existing customers from such campaigns intentional?
• Is there truly no billing grace period?
• Is this the expected experience when a renewal charge fails?

I hope Roon staff or moderators can clarify the intended behavior.

— Arthur

[danny (Danny Dulai)]

The problem you experienced is rooted in the fact that you should have been charged the discounted rate immediately and have a year added to your subscription. There was no other way the e-commerce platform we use could have done it correctly. Because that didn’t happen, it triggered a snowball of troubles.

To answer your 3 “for clarity” questions:

• Many campaigns we run are directed towards new users only. Without going into the details of marketing campaign theory, this is pretty common practice amongst all SaaS product companies trying to acquire new users.

• The e-commerce and subscription management system we use has no grace period.

• This is the expected behavior when a renewal charge fails. It looks like the charge did go through 12hrs later and you have access again.

I’m sure you’ve contacted support already and when the holiday weekend has passed, they will refund your 30%.

[Arthur_Soares]

@danny

30%

Danny, thanks for the response and for explaining the mechanics.

I understand now that, given the constraints of the e-commerce platform, the discounted price should have been charged immediately and a year added. Since that didn’t happen, everything downstream behaved “as designed,” which explains the snowball effect.

That said, the core concern remains, and the marketing copy itself is central to it. The email I received stated, verbatim:

“In celebration of a decade of Roon and as a thank you to our customers, we’re offering a full year for just $99.”

That wording very clearly sets the expectation that this offer is customer-facing, not limited to inactive or trial accounts. If the intent was new-user acquisition only, the copy does not reflect that reality.

A second clarification that matters for the UX discussion: access was not restored in a neutral way. I ultimately paid the full amount manually to avoid continued loss of access to my media library. The refund is now a corrective step after the disruption, not something that prevented it. This effectively forces users into a “pay first, fix later” position just to regain access.

More broadly, Roon is not a transient, one-off transaction. It’s a product users invest in over years. People build libraries, curate metadata, write plugins, buy dedicated hardware, and shape entire home audio ecosystems around it. I’ve done so myself. That level of long-term investment changes the bar for acceptable failure modes.

A UX that is extremely taxative around conversion and billing, with zero grace period and immediate lockout, treats the relationship as transactional rather than long-term. Everyone understands that companies need to charge, collect, and operate profitably. But there is a balance between protecting revenue and punishing users for billing edge cases, and in this situation that balance clearly tipped the wrong way.

I appreciate you engaging publicly here. My hope is that this doesn’t stop at a refund, but leads to reflection on whether these defaults truly reflect the long-term relationship Roon has with its users.

[beka]

Hey @Arthur_Soares,

Thank you for this thoughtful, detailed, and fair post; it’s exactly the kind of constructive feedback that helps us see things from our users’ perspectives, and we appreciate you taking the time to share.

The anniversary email phrasing inadvertently caused confusion, despite being aimed at specific account types, primarily those that were inactive. It should have been much clearer from the start and we’ve already taken action to avoid this from happening in the future.

The disruption you’ve experienced (the lack of a grace period and immediate lockout after a failed renewal) must have been especially disappointing for someone who’s invested for years in building their setup and library around Roon. We’ve fallen short of the experience we aim for for our customers. In your case we’ve since adjusted the charge to match the discounted rate. More broadly, your feedback is part of our discussions around eligibility transparency and billing handling.

Thanks again for engaging like this: we are listening and we welcome any further thoughts from you or the community.