Based on a trigger event you choose, this integration automatically flows the customer contacts for recent InfoFlo Print transactions into your LoyaltyLoop, allowing you to automate your feedback and review process.
In your InfoFlo Print, you have the option set the trigger event to send contacts to your LoyaltyLoop when either (1) the customer order has a ship date, or (2) the customer invoice is paid.
The process is easy and takes seconds to complete.
That’s it! The survey from LoyaltyLoop will be triggered every time an invoice gets fully paid on Infoflo.
On a daily basis, and based on the trigger event you choose, the following order details will automatically to
LoyaltyLoop:
|
|
|
|
Based on your selected trigger event, the integration will send the contacts to LoyaltyLoop on a daily basis. Allowing you to instruct LoyaltyLoop to send your feedback and review requests as soon as the next day.
Yes. To ensure your customer has had the appropriate amount of time to experience your product or service, you can impose a delay on sending your survey. As stated below, we will set a 3-day delay on the default launch configuration. If you prefer something else, please contact our support team at support@loyaltyloop.com, or 888-552-5667 option 3. Here's a blog post explaining imposed launch delays.
With the integration enabled, your data flows to LoyaltyLoop as you close transactions. You are now in position to have your surveys sent soon after the customer experiences your business.
By default, and unless you specify otherwise, upon activation of the integration LoyaltyLoop will reconfigure your survey launch configuration as follows:
If you'd like a different launch configuration, please contact our support team at support@loyaltyloop.com or 888-552-5667 option 3.
Your existing Touch Frequency Filter (TFF) will be maintained. For example, our default TFF is 90-days, meaning customers (based on email address)
who have been asked to give you feedback within the prior 90-days (or as per your specific setting), will be removed from your launch. This
prevents "over-touching" the same person too often.