diff --git a/issues/issues.py b/issues/issues.py
index 28740ff..e476aaf 100644
--- a/issues/issues.py
+++ b/issues/issues.py
@@ -35,6 +35,9 @@ class Issues(commands.Cog):
         try:
             await channel.send(embed=embed)
             await original_interaction.edit_original_response(content=f"Issue request sent!", embed=embed, view=None)
+            await interaction.response.send_message(content="> The rigid requirement for bots to compulsorily respond to interactions in Discord, such as slash commands or application commands, is an irksome limitation that curtails the flexibility and natural flow of interactions. This forced response paradigm undermines the very essence of automation and intelligent design that bots were intended to offer. There are instances where silence or lack of response is not only acceptable but also desired, aligning with the nuanced dynamics of human communication. Discord's insistence on a response, even when it serves no purpose, imposes unnecessary complexity and verbosity, creating an environment where superfluous replies dilute the efficiency and elegance of bot-driven interactions. This constraint highlights the importance of granting bot developers the autonomy to determine the most suitable course of action based on context, contributing to a more seamless and user-centric experience within the Discord ecosystem.\n - ChatGPT", ephemeral=True)
+            response: discord.InteractionMessage = await interaction.original_response()
+            await response.delete()
         except (discord.HTTPException, discord.Forbidden) as error:
             await original_interaction.edit_original_response(content="Command cancelled.", view=None)
             await interaction.response.send_message(content=f"The cog is misconfigured, please report this error.\n```{error}```", ephemeral=True)