Detect out-of-office / auto-replies separately from genuine replies

Today, Sendr's reply-detection treats any inbound message on a thread as a genuine reply, which stops the sequence/workflow for that contact. Automated out-of-office (OOO) responders trigger the exact same behavior, so contacts who are simply away get permanently unenrolled from follow-ups as if they'd actually replied. Requested by Floris Jansen (Vectify), who asked whether an OOO reply stops the workflow and confirmed this is affecting his live campaign (US - Ecom - Floris). Suggested behavior, similar to how other sequencing tools (HubSpot Sequences, Hunter Campaigns) handle this: detect common OOO/auto-reply patterns (subject lines like 'automatic reply', 'out of office', header markers like Auto-Submitted: auto-replied, or body phrases like 'currently unavailable', 'on vacation', 'will respond upon my return'), tag these separately from genuine replies, and do NOT stop the sequence for these contacts. Ideally also surface an 'Auto-reply detected' tag in the inbox/activity view so users can see it happened, and let the sequence resume automatically once the OOO window likely ends (or at minimum, allow easy bulk re-enrollment of contacts whose only 'reply' was an OOO message). Current workaround suggested to the customer: insert a SendrAI classification step after reply-detection to distinguish OOO/auto-reply text from genuine replies and branch accordingly, but this isn't reliable or native.