|
|
| | Author: | macebobo | Posted: | May 12, 2023 20:24 | Subject: | I see why the help desk is so quick now. | Viewed: | 341 times | Topic: | Off Topic | |
|
| I took my time to report an error through the Report a bug or technical issue
link
https://www.bricklink.com/helpDesk.asp?helpDeskID=114
and only after one day I got this back.
| Thank you for contacting us.
|
| For all API-related questions and suggestions, please contact our API Department at apisupport@bricklink.com.
|
They could not even forward it themselves and then let me know that I needed
to report issues there!
Ugh! I guess I am going to start calling them the less than helpful desk again.
|
|
| | | | | | | | | | |
| | | | | | Author: | macebobo | Posted: | May 12, 2023 22:07 | Subject: | Re: I see why the help desk is so quick now. | Viewed: | 74 times | Topic: | Off Topic | |
|
| In Off Topic, Admin_Russell writes:
| In Off Topic, macebobo writes:
| I took my time to report an error through the Report a bug or technical issue
link
https://www.bricklink.com/helpDesk.asp?helpDeskID=114
and only after one day I got this back.
| Thank you for contacting us.
|
| For all API-related questions and suggestions, please contact our API Department at apisupport@bricklink.com.
|
They could not even forward it themselves and then let me know that I needed
to report issues there!
Ugh! I guess I am going to start calling them the less than helpful desk again.
|
API was never handled by Help Desk. It's handled directly by our Sys-Ops
team and there is a separate Terms of Service agreement which they enforce. They
are very responsive and helpful too.
|
Thank you Russell. I did forward it to them, however why could the help desk
agent not forward it and let me know in the future I need to send corrections
to the API documentation there? Also, maybe the bug reporting page should note
what it is for if it is not for all bugs related to Bricklink.
There are so many errors in the API documentation that it makes developing against
it painful. I would even volunteer to keep it up to date if manpower is an issue.
|
|
|
| | | | | | | | | | | | | |
| | | | | | | | Author: | Admin_Russell | Posted: | May 13, 2023 01:23 | Subject: | Re: I see why the help desk is so quick now. | Viewed: | 114 times | Topic: | Off Topic | |
|
|
BrickLink ID CardAdmin_Russell
|
Location: USA, California |
Member Since |
Contact |
Type |
Status |
May 9, 2017 |
|
Admin |
|
|
BrickLink Administrator |
|
| In Off Topic, macebobo writes:
| | | Ugh! I guess I am going to start calling them the less than helpful desk again.
|
API was never handled by Help Desk. It's handled directly by our Sys-Ops
team and there is a separate Terms of Service agreement which they enforce. They
are very responsive and helpful too.
|
Thank you Russell. I did forward it to them, however why could the help desk
agent not forward it and let me know in the future I need to send corrections
to the API documentation there?
|
Because the API channel is completely separate from the Help Desk. In order to
properly get into the API channel, the user must report directly to that email
address. Otherwise, the request can get lost or it's difficult to respond
back to the original user. We've had such problems in the past of messages
being misdirected or falling through the cracks that we are trying to be pretty
strict about this. This is what our Help Desk agents are instructed to do - it's
not about whether they feel like forwarding a message or not.
| Also, maybe the bug reporting page should note
what it is for if it is not for all bugs related to Bricklink.
|
The API is a specialized service that we tend to keep hidden from the general
public. For better or for worse, this the way it has always been. If it helps,
think of the API service as a different company, like XE.com which currently
provides exchange rate services. You wouldn't go to BrickLink customer service
to report a problem with XE.com
In the same way, our customer service agents are instructed not to answer questions
related to the catalog and catalog contributions. Instead, they ask the user
to direct their question toward our catalog admins. They do not forward messages
to them as if we were all in one big office.
| There are so many errors in the API documentation that it makes developing against
it painful. I would even volunteer to keep it up to date if manpower is an issue.
|
For every correction to the API Help Pages, someone needs to test and verify
how the API is currently working. As with many Help Pages on BrickLink, they
have fallen behind and need upgrading. But it's not something that is likely
to be done overnight. It takes work from the community who is using the API and
it takes work on the other side to confirm, test, and deploy changes.
If you keep at it, I am confident you'll be able to get every error corrected.
It just may take a while.
|
|
|
| | | | | | | | | | | | | | | | | |
| | | | | | | | | | Author: | macebobo | Posted: | May 13, 2023 04:21 | Subject: | Re: I see why the help desk is so quick now. | Viewed: | 63 times | Topic: | Off Topic | |
|
| In Off Topic, Admin_Russell writes:
| The API is a specialized service that we tend to keep hidden from the general
public. For better or for worse, this the way it has always been.
|
Maybe time to ask why it has always been that way.
The new bride is making her first big dinner for her husband and tries her hand
at her mother's brisket recipe, cutting off the ends of the roast the way
her mother always did. Hubby thinks the meat is delicious, but says, "Why
do you cut off the ends — that's the best part!" She answers, "That's
the way my mother always made it."
The next week, they go to her grandmother's house, and she prepares the famous
brisket recipe, again cutting off the ends. The young bride is sure she must
be missing some vital information, so she askes her grandma why she cut off the
ends. Grandma says, "Sweetheart, that's the only way it will fit in the
pan!"
|
|
|
| | | | | | | | | | | | | | | | | |
| | | | | | | | | | Author: | WoutR | Posted: | May 13, 2023 05:51 | Subject: | Re: I see why the help desk is so quick now. | Viewed: | 57 times | Topic: | Off Topic | |
|
| In Off Topic, Admin_Russell writes:
Think of this from the user perspective...
When I have or see a problem, I report it to the help desk. I think that is all
we can expect from the average user.
That user does not need to know that there is not one helpdesk, but three. The
landing page should simply direct the user so the information automatically gets
where it needs to be.
When the user comes to https://www.bricklink.com/helpDesk.asp, there is op option
for "API problem" or "Catalog problem". The user will simply
choose which option seems to fit best.
If there was an option here to choose, the user could be directed to a page with
the proper instructions for these specific issues. That would improve the user
experience and reduce the workload for the help center. Looks like an easy to
implement WIN-WIN solution...
|
|
|
| | | | | | | | | | | | | | | | | | | | | |
| | | | | | | | | | | | Author: | jennnifer | Posted: | May 13, 2023 09:53 | Subject: | Re: I see why the help desk is so quick now. | Viewed: | 55 times | Topic: | Off Topic | |
|
| In Off Topic, WoutR writes:
I would hazard a guess that many of the members reporting 'Catalog problems'
either wouldn't know to direct their issue there or would direct non-Catalog
issues there. It's not entirely clear to most new members what that distinction
is. We get messages on the Forum all the time asking our Inventory admin to help
with someone's store inventory.
When I was admin, I got tons of messages asking for help with buying or for an
interaction with a seller. I believe it is best of all messages to go through
the main Help desk and then they can redirect the small subset of people who
are actually inquiring about a Catalog issue and not a site issue. Also, experienced
catalog contributors already know how to contact an admin directly and wouldn't
need a separate portal for that.
My two cents...
~Jen
|
|
|
| | | | | | | | | | | | | | | | | | | | | | | | | |
| | | | | | | | | | | | | | Author: | randyf | Posted: | May 13, 2023 14:00 | Subject: | Re: I see why the help desk is so quick now. | Viewed: | 54 times | Topic: | Off Topic | |
|
| In Off Topic, jennnifer writes:
| When I was admin, I got tons of messages asking for help with buying or for an
interaction with a seller.
|
We still do. Multiple times per week. It is kind of annoying.
|
|
| | | | | | | | | | | | | | | | | |
| | | | | | | | | | Author: | ErwinNL | Posted: | May 13, 2023 09:20 | Subject: | Re: I see why the help desk is so quick now. | Viewed: | 58 times | Topic: | Off Topic | |
|
| In Off Topic, Admin_Russell writes:
| In Off Topic, macebobo writes:
| | | Ugh! I guess I am going to start calling them the less than helpful desk again.
|
API was never handled by Help Desk. It's handled directly by our Sys-Ops
team and there is a separate Terms of Service agreement which they enforce. They
are very responsive and helpful too.
|
Thank you Russell. I did forward it to them, however why could the help desk
agent not forward it and let me know in the future I need to send corrections
to the API documentation there?
|
Because the API channel is completely separate from the Help Desk. In order to
properly get into the API channel, the user must report directly to that email
address. Otherwise, the request can get lost or it's difficult to respond
back to the original user. We've had such problems in the past of messages
being misdirected or falling through the cracks that we are trying to be pretty
strict about this. This is what our Help Desk agents are instructed to do - it's
not about whether they feel like forwarding a message or not.
| Also, maybe the bug reporting page should note
what it is for if it is not for all bugs related to Bricklink.
|
The API is a specialized service that we tend to keep hidden from the general
public. For better or for worse, this the way it has always been. If it helps,
think of the API service as a different company, like XE.com which currently
provides exchange rate services. You wouldn't go to BrickLink customer service
to report a problem with XE.com
In the same way, our customer service agents are instructed not to answer questions
related to the catalog and catalog contributions. Instead, they ask the user
to direct their question toward our catalog admins. They do not forward messages
to them as if we were all in one big office.
| There are so many errors in the API documentation that it makes developing against
it painful. I would even volunteer to keep it up to date if manpower is an issue.
|
For every correction to the API Help Pages, someone needs to test and verify
how the API is currently working. As with many Help Pages on BrickLink, they
have fallen behind and need upgrading. But it's not something that is likely
to be done overnight. It takes work from the community who is using the API and
it takes work on the other side to confirm, test, and deploy changes.
If you keep at it, I am confident you'll be able to get every error corrected.
It just may take a while.
|
I have a small list on my Discord with issues I've reported multiple times,
but not recently, I will mail them to the API mail address again. I'd be
happy to help test and update the WIKI.
I work with the API daily (for BLS Manager), and am in contact with multiple
sellers that develop software using the API. I think that I know a lot of the
quirks that it has .
|
|
|
| | | | | | | | | | | | | | | | | |
| | | | | | | | | | Author: | 1001bricks | Posted: | May 14, 2023 23:55 | Subject: | Re: I see why the help desk is so quick now. | Viewed: | 43 times | Topic: | Off Topic | |
|
| | | Thank you Russell. I did forward it to them, however why could the help desk
agent not forward it and let me know in the future I need to send corrections
to the API documentation there?
|
Because the API channel is completely separate from the Help Desk.
|
Sorry Russell, but this time I strongly disagree with you
From a member POV, BrickLink's API are used on the BrickLink website provided
by BrickLink.
Nobody as a member should have to care about who's doing the Taxes questions,
the Development, the Resource Management and cleaning the BrickLink office floors
(thank you!).
But if there's a question regarding whatever subject, then BrickLink should
gracefully transfer the question, and/or make the proper people to be in contact,
and/or (better!) provide a ticket system with a specific topic for Taxes, Developement,
API, etc.
|
|
|
| | | | | | | | | | | | | | | | | |
| | | | | | | | | | Author: | Stellar | Posted: | May 15, 2023 10:29 | Subject: | Re: I see why the help desk is so quick now. | Viewed: | 41 times | Topic: | Off Topic | |
|
| In Off Topic, Admin_Russell writes:
|
The API is a specialized service that we tend to keep hidden from the general
public. For better or for worse, this the way it has always been. If it helps,
think of the API service as a different company, like XE.com which currently
provides exchange rate services. You wouldn't go to BrickLink customer service
to report a problem with XE.com
|
It would be great if it was the other way around, there is awesome people in
this community that could build better tools and innovate in the LEGO world.
|
|
| | | | | | | | | | | | | | | | | | | | | |
| | | | | | | | | | | | Author: | 1001bricks | Posted: | May 15, 2023 10:43 | Subject: | Re: I see why the help desk is so quick now. | Viewed: | 51 times | Topic: | Off Topic | |
|
| | | The API is a specialized service that we tend to keep hidden from the general
public. For better or for worse, this the way it has always been.
|
It would be great if it was the other way around, there is awesome people in
this community that could build better tools and innovate in the LEGO world.
|
The problem is, Sergio, the servers load/bandwidth: it's not infinite.
If some 'sharp' users (5%) take down BrickLink then 'regular'
users (95%) will suffer of this, and it's not acceptable.
|
|
| | | | | | | | | | | | | | | | | | | | | | | | | |
| | | | | | | | | | | | | | Author: | macebobo | Posted: | May 15, 2023 12:28 | Subject: | Re: I see why the help desk is so quick now. | Viewed: | 32 times | Topic: | Off Topic | |
|
| In Off Topic, 1001bricks writes:
| | | The API is a specialized service that we tend to keep hidden from the general
public. For better or for worse, this the way it has always been.
|
It would be great if it was the other way around, there is awesome people in
this community that could build better tools and innovate in the LEGO world.
|
The problem is, Sergio, the servers load/bandwidth: it's not infinite.
If some 'sharp' users (5%) take down BrickLink then 'regular'
users (95%) will suffer of this, and it's not acceptable.
|
This should not be an issue for the largest toy company in the world, companies
load balance all the time. But heck, TLG can't even figure out how to handle
the May the 4th traffic with cloud based load balancers/servers.
So, sigh, I have to agree with you. Buy I also agree with Sergio, it would be
nice if we got a more comprehensive API which, if implemented properly, could
alleviate the load on the servers.
But, I am not impressed with Lego's information technology prowess.
|
|
|
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
| | | | | | | | | | | | | | | | Author: | SylvainLS | Posted: | May 15, 2023 12:39 | Subject: | Re: I see why the help desk is so quick now. | Viewed: | 42 times | Topic: | Off Topic | |
|
| In Off Topic, macebobo writes:
| […]
But, I am not impressed with Lego's information technology prowess.
|
To update an old adage: Nobody ever got fired for buying Microsoft and SAP.
|
|
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
| | | | | | | | | | | | | | | | | | | | Author: | SylvainLS | Posted: | May 15, 2023 15:33 | Subject: | Re: I see why the help desk is so quick now. | Viewed: | 31 times | Topic: | Off Topic | |
|
| In Off Topic, macebobo writes:
Hmm, it’s strange: for the 25-30 years I have heard and used this phrase, it
was always understood that it meant “they took the biggest player, the CYBottom
solution, without evaluation.” IOW, that “but they should” was implied. The
time the slogan was to be taken at face value ended up in the 1980s. So, it’s
strange to me that there’s still people using it as the slogan.
It may be cultural. Maybe we are all cynics in my circles
|
|
|
| | | | | | | | | | | | | | | | | |
| | | | | | | | | | Author: | 1001bricks | Posted: | May 19, 2023 17:40 | Subject: | Re: I see why the help desk is so quick now. | Viewed: | 47 times | Topic: | Off Topic | |
|
| | | Thank you Russell. I did forward it to them, however why could the help desk
agent not forward it and let me know in the future I need to send corrections
to the API documentation there?
|
Because the API channel is completely separate from the Help Desk. In order to
properly get into the API channel, the user must report directly to that email
address. Otherwise, the request can get lost or it's difficult to respond
back to the original user. We've had such problems in the past of messages
being misdirected or falling through the cracks that we are trying to be pretty
strict about this. This is what our Help Desk agents are instructed to do - it's
not about whether they feel like forwarding a message or not.
|
While this...
http://v4ei.com/comics/index.php?id=helpful&check=s2300
|
|
|
| | | | | | | | | |
| | | | | | Author: | ghyde | Posted: | May 13, 2023 15:36 | Subject: | Re: I see why the help desk is so quick now. | Viewed: | 55 times | Topic: | Off Topic | |
|
| In Off Topic, Admin_Russell writes:
| In Off Topic, macebobo writes:
| I took my time to report an error through the Report a bug or technical issue
link
https://www.bricklink.com/helpDesk.asp?helpDeskID=114
and only after one day I got this back.
| Thank you for contacting us.
|
| For all API-related questions and suggestions, please contact our API Department at apisupport@bricklink.com.
|
They could not even forward it themselves and then let me know that I needed
to report issues there!
Ugh! I guess I am going to start calling them the less than helpful desk again.
|
API was never handled by Help Desk. It's handled directly by our Sys-Ops
team and there is a separate Terms of Service agreement which they enforce. They
are very responsive and helpful too.
|
Why can't there be an automated process that analyzes the form submission
and simply tells the user that they've entered the wrong destination for
the query they've submitted?
A lot of form related issues boil down to whether the form submission is properly
screened so that the queries get directed to where they should go, and make a
lot less work for admins to do.
If it returns an error or can't find a department that the form submission
should go to, then it gets manually forwarded to an administrative address that
analyzes why the submission fails and adjusts the analyzing process accordingly.
People, by their very nature, do not want to have to comprehend which department
they're trying to contact. However, since they have to, the form submission
analysis software needs to tell them that the message would be better suited
for another department. If they insist on proceeding anyway, the form success
page should point out that they might not get the response they were expecting,
because the department they want is not correctly specified.
This would help reduce the incorrect submissions, by how much is anyone's
guess.
My point is that there is computer software and resources that can deal with
this, instead of having a person deal with it. This should make the Help Desk
administrative tasks a lot easier to manage.
Just my 2c worth. Make of it what you will.
Cheers ...
ghyde
|
|
|
| | | | | | | | | | | | | |
| | | | | | | | Author: | SylvainLS | Posted: | May 13, 2023 17:32 | Subject: | Re: I see why the help desk is so quick now. | Viewed: | 39 times | Topic: | Off Topic | |
|
| In Off Topic, ghyde writes:
| […]
Why can't there be an automated process that analyzes the form submission
and simply tells the user that they've entered the wrong destination for
the query they've submitted?
|
Could be worse:
in French: https://www.dailymotion.com/video/x7d36o
in German: https://www.youtube.com/watch?v=_CXAOiaX9CA
I haven’t found an English version of that part of the animation The Twelve
Tasks of Asterix, but you may find the whole movie more easily.
|
|
| | | | | |
| | | | Author: | UTLF | Posted: | May 12, 2023 20:46 | Subject: | (Cancelled) | Viewed: | 56 times | Topic: | Off Topic | |
|
| (Cancelled) |
|
| | | | | | | | | |
| | | | | | Author: | macebobo | Posted: | May 12, 2023 22:10 | Subject: | Re: I see why the help desk is so quick now. | Viewed: | 42 times | Topic: | Off Topic | |
|
| In Off Topic, UTLF writes:
| send your resume to Bricklink if you think you can improve things
|
I do not want to ever live in southern California again. Born and raised there,
left as soon as I turned 17, via entering the Air Force.
I know they are doing what they can to improve, but it sure didn't feel like
an exceptional experience to me.
|
|
| | | | | | | | | | | | | |
| | | | | | | | Author: | wildchicken13 | Posted: | May 12, 2023 23:33 | Subject: | Re: I see why the help desk is so quick now. | Viewed: | 46 times | Topic: | Off Topic | |
|
| In Off Topic, macebobo writes:
| I know they are doing what they can to improve, but it sure didn't feel like
an exceptional experience to me.
|
BrickLink or Southern California?
|
|
| | | | | | | | | | | | | | | | | |
| | | | | | | | | | Author: | Nubs_Select | Posted: | May 12, 2023 23:48 | Subject: | Re: I see why the help desk is so quick now. | Viewed: | 42 times | Topic: | Off Topic | |
|
| In Off Topic, wildchicken13 writes:
| In Off Topic, macebobo writes:
| I know they are doing what they can to improve, but it sure didn't feel like
an exceptional experience to me.
|
BrickLink or Southern California?
|
|
|
| | | | | | | | | | | | | | | | | |
| | | | | | | | | | Author: | macebobo | Posted: | May 13, 2023 03:46 | Subject: | Re: I see why the help desk is so quick now. | Viewed: | 41 times | Topic: | Off Topic | |
|
| In Off Topic, wildchicken13 writes:
| In Off Topic, macebobo writes:
| I know they are doing what they can to improve, but it sure didn't feel like
an exceptional experience to me.
|
BrickLink or Southern California?
|
Yes and no, respectively.
|
|
| | | | | |
| | | | Author: | popsicle | Posted: | May 12, 2023 21:56 | Subject: | (Cancelled) | Viewed: | 107 times | Topic: | Off Topic | |
|
| (Cancelled) |
|
| | | | | | | | | |
| | | | | | Author: | macebobo | Posted: | May 12, 2023 22:15 | Subject: | Re: I see why the help desk is so quick now. | Viewed: | 50 times | Topic: | Off Topic | |
|
| In Off Topic, popsicle writes:
|
It's good to see positive posts such as this, John. Thanks. Post your disgruntlement,
sure, but be willing to balance it with posting the good or positive experience
too. It's how developing occurs.
|
Cory,
I will report the exceptional here too, when I experience it. But I'm not
going to hold my breath.
John
|
|
| | | | | | | | | | | | | |
| | | | | | | | Author: | popsicle | Posted: | May 12, 2023 22:52 | Subject: | (Cancelled) | Viewed: | 108 times | Topic: | Off Topic | |
|
| (Cancelled) |
|
| | | | | | | | | | | | | | | | | |
| | | | | | | | | | Author: | Nubs_Select | Posted: | May 12, 2023 23:18 | Subject: | (Cancelled) | Viewed: | 39 times | Topic: | Off Topic | |
|
| (Cancelled) |
|
| | | | | |
| | | | Author: | legoman77 | Posted: | May 13, 2023 10:37 | Subject: | Re: I see why the help desk is so quick now. | Viewed: | 63 times | Topic: | Off Topic | |
|
| In Off Topic, macebobo writes:
| I took my time to report an error through the Report a bug or technical issue
link
https://www.bricklink.com/helpDesk.asp?helpDeskID=114
and only after one day I got this back.
| Thank you for contacting us.
|
| For all API-related questions and suggestions, please contact our API Department at apisupport@bricklink.com.
|
They could not even forward it themselves and then let me know that I needed
to report issues there!
Ugh! I guess I am going to start calling them the less than helpful desk again.
|
The help desk is a different matter. The cat admins do such a super job. The
hardest job at Bricklink, in my opinion is the taking care of the catalog. A
hundred years from now this will be the legacy of Bricklink. The catalog here
is the best possible, much better than the Lego group's knowledge of what
they sell. With my OCD I loved to catalog my sets and making sure they were
complete even before I decided to sell the collection.
These admins deserve all our praise for sorting through all the requests and
the changes Lego made to the sets including different inventories for the same
sets sold in the US and Europe.
Again, this will be Bricklink's legacy.
John P
|
|
|
| | | | | | | | | |
| | | | | | Author: | misheezy | Posted: | May 13, 2023 10:59 | Subject: | Re: I see why the help desk is so quick now. | Viewed: | 46 times | Topic: | Off Topic | |
|
| I'm a cataloger by profession, in a library. The quality of the catalog is
the legacy of every institution! And, sadly, the least appreciated effort. Thank
you for recognizing the work that goes into maintaining that legacy!
| The hardest job at Bricklink, in my opinion is the taking care of the catalog. A
hundred years from now this will be the legacy of Bricklink. The catalog here
is the best possible, much better than the Lego group's knowledge of what
they sell. With my OCD I loved to catalog my sets and making sure they were
complete even before I decided to sell the collection.
These admins deserve all our praise for sorting through all the requests and
the changes Lego made to the sets including different inventories for the same
sets sold in the US and Europe.
Again, this will be Bricklink's legacy.
John P
|
|
|
|
| | | | | |
| | | | Author: | Stellar | Posted: | May 17, 2023 15:32 | Subject: | Re: I see why the help desk is so quick now. | Viewed: | 44 times | Topic: | Off Topic | |
|
| In Off Topic, macebobo writes:
| I took my time to report an error through the Report a bug or technical issue
link
https://www.bricklink.com/helpDesk.asp?helpDeskID=114
and only after one day I got this back.
| Thank you for contacting us.
|
| For all API-related questions and suggestions, please contact our API Department at apisupport@bricklink.com.
|
They could not even forward it themselves and then let me know that I needed
to report issues there!
Ugh! I guess I am going to start calling them the less than helpful desk again.
|
Hello Sergio,
Thanks for reaching out to us.
We had a few users make us aware of this mistake and appreciate you letting us
know as well. We have passed the information on to our API team, and they are
currently working on getting this fixed.
Thank you again for making us aware of this, have a wonderful day.
Just got this reply to the same issue that I too opened a ticked, seems our concerns
got in.
|
|
|
|
|
|