Naked Wines runs a monthly wine subscription that funds independent winemakers directly, matching members to wines based on their taste profiles and delivering bottles on a recurring basis. The model depends heavily on ongoing member relationships — both to keep subscribers engaged and to sustain the winemakers financially. From the site, the customer support surface is notably broad: a contact form, phone line, email, and a dedicated accessibility request channel all sit alongside an active member chat, suggesting support volume is a meaningful operational layer.
If we're already off — say so in 20 minutes: book a call.
The thing we're curious about: with a subscription model, member queries tend to cluster around the same recurring moments — delivery windows, rating and recommendation updates, pausing or changing plans. Your site surfaces several distinct inbound channels (the contact form, phone, email, and an accessibility-specific route), which raises a question about whether those threads land in one place or fragment across separate queues. When support channels aren't unified, the team often ends up re-handling the same request more than once, and members experience slower resolutions at the moments that most affect renewal sentiment. One angle worth exploring is whether the recommendation and account-change journeys in particular create a disproportionate share of inbound contact — and if so, where in that flow the friction actually lives. What we genuinely can't tell from outside is how those channels are currently connected, what the ticket shape looks like, or whether this is already well-solved internally.