|
FreeWheel's Support Portal is used to:
Requests for technical assistance are handled by Freewheel Support during your local business hours, Monday to Friday, or 24/7 for high or urgent priority inquiries for most products. Support requests are addressed by Support Engineers, who are product experts that can directly address or escalate issues to appropriate specialists within FreeWheel as necessary. |
Before submitting a request, check the Freewheel Hub or FreeWheel's API documentation for information that may help answer your question(s). For questions of a non-technical nature, please reach out to your FreeWheel account team.
Accessing the FreeWheel Support Portal requires a username/e-mail address and password.
Please note that the Support Portal login credentials are the same ones used to access the FreeWheel Hub, but are different from what is used to access your FreeWheel product. Access to these logins are typically initiated or provided by your account management team. |
For a forgotten FreeWheel Support Portal/Hub password, visit https://forgotpass.freewheel.tv/ |
FreeWheel Support Portal passwords expire every 180 days. All users will be emailed a reset password link after 165, 170, 175 days. To reactivate expired accounts, contact your FreeWheel account management team. |
To submit a support request, please complete the request form with as much detail as possible. Doing so provides FreeWheel's support engineers with the information they need to investigate the first time; with minimal delay for follow-up.
From the "Submit a Request" page, select the appropriate request type from the drop down to complete the request form below. Required fields are marked with a red asterisk (*).
Field | Description | |||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|
CC | The option to include additional email addresses, which are CC'ed when FreeWheel responds to the ticket | |||||||||||
Subject* |
| |||||||||||
Description* | A detailed description of the request or issue. If applicable, please include:
Information specific to the issue, such as:
Other useful information to include:
One of the best questions to ask when submitting ticket is what is the problem you are trying to solve? Answering this question at the very beginning of your support ticket will help contextualize the issue and ensure FreeWheel answers it as comprehensively as possible. Example: Rather than asking if a particular function is supported, or what the purpose of a function is, ask how you can accomplish a specific end goal. | |||||||||||
Priority* | Assign a priority level to your ticket from one of the options below.
Ticket Priority Levels
| |||||||||||
Other Data to Include | Different forms may include requests for other information. For instance, in mapping a buyer seat FreeWheel will want to know the seat, DSP, and buyer. For reporting requests FreeWheel will need to know what the business case and use is for the report, so the support engineer can tune it according to your business needs. | |||||||||||
Attachments | Screenshots, exported reports, traffic capture, and/or other files that may aid our team in their investigation. |
From the FreeWheel Support Portal, you can review submitted requests which you have been grated access to. See more about this below.
For concerns about a ticket and to request escalation, some tips include the following:
Leverage your account manager: Your account management team is also able to help with issues requiring escalation. Please use this sparingly.
Service notifications, through the Support Portal, are a way to stay informed about FreeWheel system updates, product release information, and office closures. You can opt-in to service notifications from the following sections topics:
FreeWheel recommends joining System Updates, which are used to announce any unplanned incidents. |
To subscribe to service notifications:
Once subscribed, section topics with new articles will be e-mailed from noreply@Freewheel.zendesk.com. Please check your spam folder to ensure messages are not lost. |
Alerts are automatically displayed in the UI when live as well |