A few months ago I ordered and received a new kind of pierced earring backs. However...

GetHuman2604889's Technical and Service Support issue with Amazon from March 2019

Help with my Amazon issue
Top Tip from another customer
If you are having technical issues with your Sprint device then I suggest bringing the device into a store near you. You can use this locator to find the store - http://storelocator.sprint.com/locator/
The issue in GetHuman2604889's own words
A few months ago I ordered and received a new kind of pierced earring backs. However there were no instructions. I cannot figure out how they work. Can you help me? They've just been sitting in my jewelry box and I'd really like to be using them. Judy Payne
GetHuman2604889 did not yet indicate what Amazon should do to make this right.
I have an issue with Amazon too
How GetHuman2604889 fixed the problem
I will not be using those backs again. Once on, I find it very difficult to remove them. Actually Amazon has a better product for pierced ears that have become enlarged. They are small adhesive pieces that you place behind your ear, covering the hole. Then you insert the earring through it and put the backing on. I have never had one droop or come off accidentally.
Please help with my Amazon issue
Do you have a customer issue as well?
We can help you get Amazon's attention and get better help faster. Tap below to get started.
Having Amazon 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

Amazon

Technical and Service Support issue
Reported by GetHuman2604889
Mar 27th, 2019 - a mon ago
I have an issue with Amazon too
Fixed
Seen by 4 customers so far
Similar issue to 143357 others
0 customers following this
Items needed
Email address on the account
Order number
Name on the account
Billing address
Timeline
GetHuman2604889 started working on this issue
Mar 27th 4:47pm
GetHuman2604889 indicated the issue is not fixed yet.
Apr 5th 7:25pm
GetHuman2604889 confirmed the issue is fixed. Hooray!
Apr 5th 7:26pm