@Marco Thanks for the feedback. We explained the keyword situation in the first thread which was left open should anyone want to comment (and once you replied there, the thread automatically was taken out of solved status).
We are sorry if our explanation was not clear — it is still perfectly possible to fix any keyword issues by adding/correcting/deleting any individual cases in the meantime. We have a ticket open to create a more scalable long-term solution to accept keyword corrections en mass vs. an inefficient process which had become almost a full-time job to apply these corrections on our side in the absence of such a scalable process.
Correcting these keywords at that volume contributed to us being unable to stay on top of much more visible / impactful problems on Sprinklr, ones which often needed staff work and did not have a contributor workaround. The team has been putting in additional effort to catch-up on this backlog over recent weeks, hence the updates to those threads. We only have finite resources and we often to have to make difficult choices on priorities, such as this one, sorry. The threads are marked closed and solved to stop them reappearing in the Sprinklr admin tools and costing more time for us plus increasing the chances that the team will miss actually open threads. We are not being disrespectful, we are trying to be as efficient as possible in solving other open problems which are not pending a better solution.
@Col_Needham Thanks for your swift reply. I see that the thread I replied to now no longer has the Solved tag attached to it.
If I interpret you correctly, a thread that has the Closed tag (but not the Solved tag) still shows up in the admin tools. I'm not sure if that's the most desirable situation, but it does help understand why the Solved tag is sometimes used for threads that are not solved.
I know it's still possible to fix individual keywords, but the issues raised in the above-mentioned threads also require staff intervention because, AFAIK, contributors can't do auto-conversions for keywords. So even if a contributor would be able to delete all wrong entries for a certain keyword, these entries could still reappear in the future.
That being said, thanks again for your reply and it's always nice to see a lot of threads that actually have been solved by staffers in the past week(s) or so, so it's not all bad. :)
Col_Needham
Employee
•
8.2K Messages
•
190.5K Points
2 years ago
@Marco Thanks for the feedback. We explained the keyword situation in the first thread which was left open should anyone want to comment (and once you replied there, the thread automatically was taken out of solved status).
We are sorry if our explanation was not clear — it is still perfectly possible to fix any keyword issues by adding/correcting/deleting any individual cases in the meantime. We have a ticket open to create a more scalable long-term solution to accept keyword corrections en mass vs. an inefficient process which had become almost a full-time job to apply these corrections on our side in the absence of such a scalable process.
Correcting these keywords at that volume contributed to us being unable to stay on top of much more visible / impactful problems on Sprinklr, ones which often needed staff work and did not have a contributor workaround. The team has been putting in additional effort to catch-up on this backlog over recent weeks, hence the updates to those threads. We only have finite resources and we often to have to make difficult choices on priorities, such as this one, sorry. The threads are marked closed and solved to stop them reappearing in the Sprinklr admin tools and costing more time for us plus increasing the chances that the team will miss actually open threads. We are not being disrespectful, we are trying to be as efficient as possible in solving other open problems which are not pending a better solution.
Thank you for your understanding.
1