> ## Knowledge Base Index > Fetch the complete knowledge base index at: https://help.novalya.com/sitemap.xml > Use this file to discover available pages before exploring further. > Pure-Markdown content can be obtained by appending a '.md' suffix to the content URLs listed in the sitemap (without the trailing slash). # How does the "Avoid duplicate birthday messages" option work? # How does the "Avoid duplicate birthday messages" option work? **Reading time:** 3 min ## Quick summary The "Avoid duplicate birthday messages" option prevents sending multiple messages to same contact for **same birthday**. If enabled, only one message is allowed per birthday per year. --- ## Where this option is located ### In campaign configuration **Location:** 1. Create or edit Birthday campaign 2. **Step 4: Advanced options** 3. Checkbox "Avoid duplicate birthday messages" **Recommended status:** **Enabled** --- ## How it works ### Basic principle Operation is based **per birthday and per year**: **If option is enabled:** - Novalya records that message was sent for this contact's birthday - All other sending attempts for same birthday will be blocked - Automatic reset on January 1st of following year **If option is disabled:** - You can send multiple messages (before, day D, after) to same contact - No restriction --- ## Case 1: Sending before birthday ### Period D-1 to D-6 **Example:** You send message at D-2 (2 days before) **Result if option enabled:** - ✅ Message sent at D-2 - ❌ Other BEFORE days are blocked: - D-6, D-5, D-4, D-3, D-1 → Blocked - ✅ Day D remains available - ✅ D+1 and D+2 remain available **Interface display:** - Status: "Already sent" only for "before birthday" period - Other periods (day D, after) remain usable | If you send before birthday, you can still send on day D or after. --- ## Case 2: Sending on day D ### Birthday day **Example:** You send message on day D **Result if option enabled:** - ✅ Message sent on day D - ❌ AFTER days are blocked: - D+1, D+2 → Blocked **Impact:** - If you planned to also send at D+1 → Won't work - Contact already received their birthday message on the day itself --- ## Case 3: Sending after birthday ### Period D+1 or D+2 **Example:** You send message at D+1 (next day) **Result if option enabled:** - ✅ Message sent at D+1 - ❌ Other AFTER day is blocked: - D+2 → Blocked **Advantage:** - You can send **after** birthday if you didn't send before or on day D - Useful if you missed previous periods --- ## Annual reset ### January 1st of each year **How it works:** System automatically resets on **January 1st**: **Example:** - Marc's birthday: March 15 - You send message on March 13, 2026 (D-2) - Marc is blocked for rest of his 2026 birthday - **January 1, 2027**: Reset - You can send message again for his 2027 birthday | Each contact can receive ONE birthday message per year, regardless of chosen period. --- ## Difference with other filters ### Specific to Birthday module This option is **different** from: **"Already targeted by Novalya" (prospecting):** - Used in prospecting campaigns - Avoids targeting multiple times in prospecting - Doesn't impact birthdays **"Existing conversation":** - Filters if conversation is open - Can be combined with birthdays - Different logic **CRM filters / Pipelines:** - Organize your contacts - Don't block sending - Complementary to duplicates option | Birthday duplicates option is independent and specific to birthday campaigns only. --- ## Why enable this option ### Protection and professionalism **Reasons to enable (recommended):** 1. **Prevents multiple sends** - Contact receives only one birthday message - Avoids redundancy 2. **Protects your image** - Avoids appearing "automated" or "spam" - Maintains natural behavior 3. **Avoids artificial behavior** - Sending 3 messages (D-1, D, D+1) to same contact = suspicious - Single message = natural 4. **Guarantees single contact point** - You choose your best timing (D-1 or D+1) - Maximize impact with one well-placed message --- ## If period is blocked ### "Already sent" status In contact list for campaign, you'll see: **Status:** "Already sent" **Meaning:** - Message already sent for this birthday this year - Contact is excluded from current campaign - You cannot force sending **Possible action:** - Wait until next year (January 1st reset) - Or disable option for future campaigns (not recommended) --- ## FAQ ### Is this related to Facebook or is it a Novalya rule? It's an internal Novalya rule to protect you and maintain natural behavior. Facebook doesn't impose this limit. ### Is it per campaign or per account? It's **global to Novalya account** for Facebook. If you send via one campaign, another campaign cannot send for same period of same birthday. ### Can I see who already received message this year? Yes, in contact list, "Already sent" status indicates message was sent for this birthday. ### What happens if I disable option mid-year? Past sends remain recorded until January 1st. Disabling option allows sending new messages, but this is not recommended. --- ## Related articles | [How to send birthday messages?](/en/article/how-to-send-facebook-birthday-messages-with-novalya-giq5df) | [How to use CRM pipelines?](/en/article/how-does-novalya-crm-work-facebook-and-instagram-1g4uqg1) | [What are Facebook sending limits?](/en/article/what-are-message-sending-limits-on-facebook-and-instagram-1yoq3ed) --- || **Need help?** || Our support team is available by email at **support@novalya.com** or via the **[Ticket Center](https://app.novalya.com) (open the ticket center from the help menu)** in your Novalya space. || Our team aims to reply within 24 hours on business days.