Point to the part that needs attention
A report that says a setting looks wrong can leave a lot to interpretation. Showing the exact area and explaining what you expected gives the person investigating a much better starting point, especially when several monitors or integrations look similar.
PageLantern’s in-app feedback flow lets you describe an issue and optionally attach a capture of a selected page area. The latest improvements make that capture more reliable and keep a screenshot problem from blocking the report itself.
Write the context, then choose a capture
Open Report an issue, select the topic that fits, and write what happened in Message. Include what you were trying to do, the result you saw, and the result you expected. A short sequence of actions helps us reproduce the problem and understand where the workflow broke down.
Move over the relevant page area to see the selection outline, then click to attach a capture. Review Attached UI capture before sending. If it shows the wrong area or adds no useful information, use Remove capture and keep the written explanation.
Keep sending possible when capture fails
Screenshots are optional. If the browser cannot create the image, the form explains that you can still send the report without one. Your description can carry the investigation forward while you include any relevant page or monitor context in the message.
The capture flow also protects a newer selection from being replaced by an older capture that finishes later. Attachments use a PNG image, and you can inspect the result before choosing Send report. These changes make the report you review a more dependable guide to what you intended to share.
Share the useful detail deliberately
Capture preparation clears input and text-area values in the copied page content used to make the image. Your working page stays unchanged. Other visible text can still appear, so review the preview and avoid including credentials, private customer information, or anything the investigation does not need.
Finish with a concrete example and enough context to reproduce the behavior. If you cannot use the in-app report, the contact page provides another way to reach us. A focused report helps us understand the customer impact and find the part of the workflow that needs attention.