I just got charged Rs ***** for LinkedIn Sales Navigator after a free trial. I had no i...

GetHuman5610888's Refund a Charge issue with LinkedIn from January 2021

Help with my LinkedIn issue
First: share to improve GetHuman5610888's odds
Strength in numbers! Companies respond better when others are watching.
Before contacting them, items GetHuman5610888 may need:
Username, Email on Account, Phone Number, and Name of Account Holder
The issue in GetHuman5610888's own words
I just got charged Rs ***** for LinkedIn Sales Navigator after a free trial. I had no intention of subscribing, and didn't get an email notifying me when the charge was going to take place on an old card I no longer use. Just noticed it now (it was charged earlier today). How do I contact customer support * get a refund? I've tried going to this page *https:**www.linkedin.com*help*linkedin*answer*****?query*Refund&hcppcid*search* and hitting Request Account Review, but it says "We're unable to complete your request. You do not appear to have purchased a Premium subscription."**Please help!

GetHuman5610888 did not yet indicate what LinkedIn should do to make this right.

How GetHuman5610888 fixed the problem

We are waiting for GetHuman5610888 to fix the problem and share the solution with the rest of us customers.

Do you have a customer issue as well?
We can help you get LinkedIn's attention and get better help faster. Tap below to get started.
Help from Real People?
If our free tools aren't enough, we partner with a US-based company with live tech support experts available 24/7. Take advantage of a $1 one-week trial membership and chat with an expert now.
Chat with a Live Expert
Having LinkedIn issues too?
Get tips from pros & other customers, and get it handled faster:
For better results, write at least 100 characters
This email address isn't valid


Refund a Charge issue
Reported by GetHuman5610888
Jan 3rd, 2021 - 3 months ago
Not resolved
Seen by 2 customers so far
Similar issue to 11715 others
0 customers following this


GetHuman5610888 started working on this issue
Jan 3rd 7:38am