How to submit a tick to Botkin? - briefly
Log in to Botkin, open the “Submit Tick” page, complete the required fields (title, description, severity), attach supporting files, and press “Send”. A confirmation email containing the ticket number will be sent immediately.
How to submit a tick to Botkin? - in detail
Submitting a tick to Botkin requires precise preparation, correct channel selection, and verification of the received acknowledgment.
First, gather all relevant information about the issue. Include a succinct title that captures the core problem, a detailed description outlining the circumstances under which the tick occurs, and any error messages displayed. Attach supporting artifacts such as log files, screenshots, or reproducible steps. Ensure that timestamps are in UTC and that sensitive data is redacted.
Second, format the submission according to Botkin’s specifications. Use plain‑text or markdown files, avoid proprietary formats. Structure the content with clear sections: Title, Description, Steps to Reproduce, Expected Result, Actual Result, Attachments. Maintain a maximum file size of 5 MB per attachment.
Third, choose the proper submission channel. Botkin accepts tickets through its web portal and via a dedicated email address. For the web portal, log in with your registered credentials, navigate to the “Create Ticket” page, fill in the fields, upload the files, and press Submit. For email, address the message to [email protected], place the formatted text in the body, and include attachments using standard MIME encoding.
Fourth, confirm receipt. After submission, Botkin generates a unique ticket identifier. Record this identifier for future reference. The system typically sends an automatic acknowledgment within five minutes. If no acknowledgment arrives, resend the ticket using the same channel and verify that the identifier was not omitted.
Finally, monitor the ticket’s status. Botkin updates the ticket with progress notes, assigned priority, and resolution details. Use the web portal’s dashboard or the email notifications to track changes. When the issue is resolved, close the ticket only after confirming that the fix addresses all described symptoms.
Adhering to these steps ensures that the tick is processed efficiently and that the response from Botkin aligns with the organization’s support standards.