How to work with Labelbox support to report issues and feedback.
The Machine Learning Support Engineers (MLSEs) at Labelbox will troubleshoot issues and provide timely resolutions upon communication from users.Our mission is to respond to and resolve your issue as quickly as possible while maintaining the highest quality of technical support. We understand and appreciate your eagerness to maximize productivity on the Labelbox platform, and we are here to unlock these opportunities for you.
Support is available during our normal business hours, which span from 9:00 AM to 8:00 PM Eastern Time on Monday through Friday, with the exclusion of major U.S. holidays.
Meet our Labelbox Chat Bot, a cutting-edge solution designed to cater to your queries regarding scripting, understanding app functionality, and more. Powered by the advanced ChatGPT 3.5 turbo, this bot relies on prompts provided by users to deliver insightful and accurate responses.Now, the key to extracting the best output lies in crafting good prompts. A good prompt is precise and clearly articulates the user’s question or request. By providing specific and well-formulated prompts, users can unlock the full potential of the Labelbox Chat Bot, receiving tailored and relevant information that enhances their experience.Think of good prompts as the key to unlocking a seamless and efficient interaction with our AI-powered assistant, ensuring that you get the most out of each engagement.
Our Community is dedicated to addressing common issues. Feel free to browse through the available resources, or register and contribute your own insights to help others.
Access to our ticket portal is by invitation only. If you do not have an account, please reach out to your sales representative for assistance. Alternatively, you can visit our Community section, where we’ll be happy to provide support.
Upon choosing the type of ticket you wish to open, you will be prompted with a submission form. While each ticket type is unique, the foundational elements are similar. Understanding where to find and how to select the correct information is immensely helpful to our Support team and will contribute to faster resolution times overall.Below is a synopsis of the most important fields, how to fill them out, and what they represent:
The email address entered in this field should belong to the primary stakeholder of the concern being reported. The ticket will be associated with the Jira portal identity for this user and the email address should be associated with a Labelbox account.Other users can be added as Request participants after the creation of the ticket in order to view and participate in the thread.
The email address(es) entered in this field should represent the Labelbox account(s) in which the relevant issue is occurring. Typically, the entry here will be the same as the above field, but this is not always the case when reporting a team-related concern.
To find a workspace ID, click on your initials in the left panel and select Workspace settings. The workspace ID will be displayed alongside a button for quick copying.
To find a project ID, select a project and copy the ID from the URL. The project ID will be located immediately after projects/ and span until the next / in the URL.
To find a dataset ID, navigate to the Catalog, select the dataset from the menu, and copy the ID from the URL. The dataset ID will be located immediately after catalog/ and span to the end of the URL.
From Catalog, you can click on any data row to open a detailed view of that data row. On the right of the detail view panel, you can find and copy the data row ID.
You can also find the data row ID and label ID by selecting a project and navigating the Data Rows tab. Click on any data row to open the Data browser.
In the URL, the data row ID will be located immediately after data-rows/ and span until the next / in the URL ( in red), followed by the label ID (in green).
The label ID will appear in the left panel (in green). Data rows that have not been labeled will not have a label ID.
Asset ID and Data row ID are used synonymously and refer to the Labelbox-generated IDs assigned to each data row in an organization.A Label ID is only generated once annotations have been submitted on a data row. Keep in mind, when utilizing Benchmarks or Consensus, there may be more than one Label ID associated with a single data row.
After you create a ticket, the email address entered in the on behalf of field will receive an email from [email protected]. The subject of the email will follow the format of LS-#### <Summary>, where Summary is the summary you entered when filing the ticket.When you receive the email, click on View request to open the ticket in the Customer Help Portal. If someone else raised the ticket on your behalf and you have never used the portal, you may need to complete a brief sign-up procedure.
Alternatively, you can view all tickets you or your teammates have created by navigating to Requests in the top right corner of the customer help portal. Once here, you can filter your tickets, monitor their status, and select a ticket directly from the portal.
Here are some best practices for getting quick resolutions on your tickets:
Include attachments on your tickets. Screenshots, screen recordings, JSON files, Python snippets, and any other resources that can provide additional context for the ticket are welcomed and encouraged.
Create separate tickets for separate issues. If you have multiple, unrelated questions and concerns, please open separate tickets. When possible, please refrain from raising a new issue on an existing ticket. Keeping issues separate helps us reach resolutions faster as a team and allows us to better monitor trends so that we can continue to improve our Support overall.
Comment to re-open a ticket. If a ticket has been closed by the Support team and the same issue emerges — or perhaps you have more feedback to add — you can always comment on the ticket and it will automatically re-open.
Use the Customer Support Portal. Communication on tickets will be clearer, more efficient, and easier to digest on the Jira portal compared to over email. In addition, you can use the portal to view all tickets raised by your team, which can illuminate trends and enable the consolidation of your efforts.
