Bug 21162

Summary:	Support Email Navigation Opens Blank Untitled Page and New Visitor Form Headers Have Low Visibility
Product:	CheckMark Chatbot	Reporter:	Nandhini <bnandhini>
Component:	Chat Widget	Assignee:	Abuzar Mohammed <mabuzar>
Status:	CLOSED ---	QA Contact:
Severity:	Minor
Priority:	Medium	CC:	mabuzar
Version:	Build-04
Target Milestone:	---
Hardware:	Cloud
OS:	Browser - Chrome

Description Nandhini 2026-08-27 11:50:30 IST

Issue 1: Support Email Link Navigation
Open the CheckMark AI Assistant.
Enter the prompt: “I need to reach the support team for my queries.”
The chatbot displays a list of responses containing support-related links.
Click the support@checkmark.com link.

Actual Result
The link navigates to a blank page with an “Untitled” page title by default. The email link works only after clicking the URL again.

Expected Result
The support@checkmark.com link should navigate/work correctly on the first click without displaying a blank or untitled page.

Issue 2: New Visitor Support Ticket Field Headers Have Low Visibility
Open the CheckMark AI Assistant.
Click Need Help → Create a Support Ticket → I’m a New Visitor.
Observe the field headers displayed in the support ticket form.

Actual Result
The field headers are displayed in a very light font color, making them difficult to read and reducing visibility.

Expected Result
All field headers should be displayed in a bold, darker font for better readability and a clearer visual appearance.
screenshot:
https://drive.google.com/file/d/10hD3s9X-PaZ6mNAM57moOo47yImCz3WY/view?usp=sharing
Screen rec:
https://drive.google.com/file/d/1EuNf1mSaM1_YJ-h1LZZrARp-D9NpFk5d/view?usp=sharing

Comment 1 Abuzar Mohammed 2026-09-02 12:10:35 IST

Issue 1:
This is not an actual navigational link. The support@checkmark.com text is intended to represent an email address, so it does not need to open a separate page when clicked.

Issue 2: solved

Comment 2 Abuzar Mohammed 2026-09-02 12:15:24 IST

resolved issue 2

Comment 3 Nandhini 2026-09-04 16:35:53 IST

Issue#1: As per the comments, closing this bug

Issue#2: working as expected
https://prnt.sc/6FSKDo6gAjcf