To avoid sending multiple review requests to the same contact, SocialPilot Reviews provides Duplicate Request Prevention (DRP).
This feature lets you control how frequently a contact can receive review requests.
In This Article:
- How Does Duplicate Request Prevention (DRP) Work?
- Why Use Duplicate Request Prevention?
- Where Can Duplicate Request Prevention Be Applied?
- Understanding Warning Messages
- Managing Duplicate Request Prevention (DRP)
How Does Duplicate Request Prevention (DRP) Work?
When DRP is enabled for a brand, a contact is protected for a defined period after receiving a review request.
During this period:
- You cannot send another review request to the same contact.
- The contact cannot be enrolled in another campaign.
- Quick Review Requests to that contact are also restricted.
The duration of this protection is set at the brand level.
Why Use Duplicate Request Prevention?
Enabling DRP helps you:
- Avoid sending repeated requests to the same contact.
- Maintain a better customer experience.
- Prevent unnecessary follow-ups.
- Improve the quality of responses.
Where Can Duplicate Request Prevention Be Applied?
Duplicate Request Prevention (DRP) is enforced across:
- Quick Review Requests
- Campaign enrollment
- Contact selection
Depending on the action, you may see:
- An error message when sending a request.
- A lock icon next to a contact.
- A warning before launching a campaign.
Understanding Warning Messages
When a date is shown: The contact has already received a review request, and the protection period is active. The displayed date shows when the contact becomes eligible to receive a new request.
When no date is shown: The contact is enrolled in a campaign, but the first review request has not yet been sent. Since the protection period begins only after the first request is delivered, an end date cannot be calculated yet.
Managing Duplicate Request Prevention (DRP)
DRP is configured at the brand level, where you can define the time interval between review requests.