LoyaltyLoop sends survey invites to your customers on your behalf. This gives your LoyaltyLoop invites a personal touch, looking just like any other email you might send to your customers.
This is a common mass email technique referred to as "spoofing". LoyaltyLoop employs this technique properly using industry best practices. Other nefarious companies may use this technique maliciously. When used maliciously, it is often used to trick email recipients into clicking on links that result in viruses or malware. When your spam protection alerts you to potential spoofing, it is justifiably warning you to take extra precaution when opening the email in question.
There are authorization technologies used for legitimately sending emails on behalf of some else. Sender Policy Framework (SPF) and DomainKeys Identified Mail (DKIM) are two such technologies. Basically, they verify that the email sender, in this case, LoyaltyLoop, is authorized to send emails on your behalf. The SPF record is configured on your specific domain record, usually managed through your hosting company (i.e. GoDaddy.com). When we set up your LoyaltyLoop service, our team works with yours to ensure your SPF (and/or DKIM) is set correctly.
When we launch a round of survey invites on your behalf, if you included your email address in your launch file too, this can trigger a fraud detection alert. This is something only you would see, not your customers, and is nothing to worry about. Because the survey invitation is sent FROM you and TO you, if you included your same email address in your launch file, this can sometimes trigger span software or trigger fraud detection. This is normal behavior of many email servers and email clients, and nothing to be alarmed by. It is important to note your customers would not see the spoofing warning when the SPF record is set correctly. They see a normal email coming from you to them (i.e. from and to different email addresses) asking for feedback.
Here's an example of a QC Email and what the "fraud detection" message may look like: