So I have just signed up with crisp. My business email address is firstname.lastname@example.org. Crisp asks for an email address when signing up and sends you the chat transcripts after the conversation is complete.
The problem is that Crisp sends these transcripts from email@example.com
Now I have piping enabled for firstname.lastname@example.org for my General Queries Department so I keep getting the transcript opening tickets on the support system.
NOW I have to go and delete every support ticket that gets opened because blacklisting each email address is pointless because the sequence will always change and never be the same so its useles to blacklist it.
I want to add a wildcard in the Spam Control System *@bluesteam.on.crisp.email so that NO transcripts can open a ticket but lo and behold, there is no such thing as a wildcard on the Spam Control.
How can this be? It's such a simple feature that should be enabled with every spam control system.
Has anyone got a solution to this?
Hello, in WHMCS 6.3 in last days i started receiving significantly higher amount of SPAM support tickets than before. (bot spam not real people)
So i tried to switch "Captcha Type" from "Default (5 Character Verification Code)" to "reCAPTCHA (Google's reCAPTCHA system)"
I seen i already had prefilled public and private key there and i verified it is correct/same with keys in my google account where i added my site already.
But when i open contact form as a non logged in user in Firefox and Tor browser, it does not show up the recaptcha, it shows only:
When submitting, it says "The characters you entered didn't match the image shown. Please try again."
Is there any work around/hack (by editting some files) so i can prevent support ticket SPAM?
The default WHMCS 5 chars. captcha show up, but SPAM bots started going over it.
In recaptcha account, server side integration URL is: https://www.google.com/recaptcha/api/siteverify
<div class="g-recaptcha" data-sitekey="PubKeyHere"></div>
I see my recaptcha is "v2" type\
Update: The cause of this issue was Content-Security-Policy in .htaccess file that denied google domain.
Recently Browsing 0 members
No registered users viewing this page.