Please help us help you and fill where relevant:
LimeSurvey version: LimeSurvey Community Edition Version 6.0.7+230515 
Own server or LimeSurvey Cloud: Own Server
Survey theme/template: Sea Green (Default admin theme)
==================

Dear Experts,We have an active LimeSurvey-based survey that generally meets our needs, but there are a few pain points I’d like to raise for your advice and possible improvements:

1. When a user first clicks the survey link but closes it without submitting any response, the system still marks the survey as completed and shows "this ticket has been rated" upon reopening, which prevents actual feedback from being submitted later.
2. In the results page, many incomplete survey entries appear, and the batch delete function does not seem to work—we selected multiple entries and clicked delete, but no action was taken, so we had to manually delete them one by one.
3. We currently pass ticket ID, subject, and customer email in the URL parameters when triggering the survey link through our ticketing system, but this makes it easy for others to manipulate the link and submit fake results, which affects the accuracy of the feedback.

We would appreciate any guidance or suggestions on whether these issues can be resolved or improved. I'm attaching my active .lss file so you have an idea:)
Thank you very much for your support.

Hi,
1.

the system still marks the survey as completed

No, it does not. But you also count "not submitted" responses.{statCountIf(TicketID.sgqa, TicketID.NAOK, 0 , 0)}
Refer to the manual
count number of responses (submitted or not) : {statCount("id", 0)}
count number of submitted response : {statCount("id")}

I suppose you only want to count submitted responses.

This means it is obvious that you see your end message (even in not submitted surveys the count is >0)
In my opinion you'd should use a quota to screen out respondents who try to enter an already submitted survey again

2. I can't reproduce.
But before you complain about an issue you should update to the actual version.
Your version 6.0.7. is nearly 2 years old and as you see, it's one of the first releases of the 6.x. branch.

3. Here you have to think about other ways how to link LimeSurvey with your ticket system.
You could use the API to create a new record of the respondent with ticket ID, subject, and customer email as additional attributes.
Run it as closed survey with e.g. ticketID as token.
But this is only a rough idea.

Joffm