> ## Documentation Index > Fetch the complete documentation index at: https://docs.propilotapp.com/llms.txt > Use this file to discover all available pages before exploring further. # Rules & Limits > The full reference for sequence build rules, reply behavior, the one-active-sequence limit, editing restrictions, and auto-enroll priority. Sequences have guardrails so a cadence can't accidentally spam a contact, double-book them, or break mid-flight. This page is the full reference; the builder's floating **Validation** widget enforces the build rules live and blocks saving while errors remain. ## Build rules | Rule | Limit | Why it exists | | ---------------------- | ------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------- | | Steps per sequence | Up to **10** | Keeps cadences workable; longer journeys are better split into a second sequence. | | SMS steps | At most **2** | Texting is the most intrusive channel; extra touches should be email or calls. | | Spacing between steps | At least **10 minutes** | Prevents accidental back-to-back sends. | | Same-channel spacing | **24 hours** | No two SMS, and no two emails, may be scheduled within 24 hours of each other - measured across the whole cadence, even with other steps in between. | | New Conversation steps | **One per channel** | The first SMS (or email) opens the thread; a second touch on the same channel must be **Existing Conversation**. | | Sequence name | **Unique** in your organization | Capitalization doesn't matter - "Cold Intro" and "cold intro" collide. | | Step content | Required | SMS and email steps need a template; Existing Conversation steps must choose **Follow-up** or **New Property**. Call scripts are optional. | ## Reply behavior **Pause-on-reply is always on and not configurable.** The moment a contact replies, their enrollment stops and all pending steps are cancelled. They move to **Moved out** with a **Replied** badge. Manual contact has the same effect: if you send an SMS or email or place a call to a contact about the same property they're enrolled for, the enrollment stops - your personal touch replaces the cadence. Contacting them about a different property does not stop the enrollment. ## Off-market deals stop the cadence If a deal goes off-market, the daily listings refresh marks it inactive and stops any active enrollment tied to that property - there's no point messaging the listing agent about a listing that's no longer for sale. The contact moves to **Moved out** with a **Property inactive** badge. Because this happens on the daily refresh, the cadence stops on the next refresh after the listing leaves the market, not the instant it changes. If the deal comes back on the market, re-enroll the contact manually. ## One active sequence per contact A contact can be in only **one active sequence** at a time, even across different listings. If an agent is enrolled through one property, their cards on other properties show **In sequence ยท other listing** and new enrollments are skipped. Use **Stop & re-enroll** in the enroll window to switch a contact to a different sequence. ## Editing sequences Sequences with active enrollments can't be edited in place, so contacts mid-cadence are never affected by changes. Use **Duplicate & Edit** to create an editable copy with the changes you need, then enroll new contacts into the copy. The conversation type is locked at save time on every sequence, with or without enrollments. Turning a sequence **Off** stops future enrollments (manual and auto-enroll) without touching contacts already in flight - the confirmation reads **Turn off for future enrollments**. ## Auto-enroll priority If two Deal Hub auto-enroll rules match the same contact, the higher-priority sequence wins and the other rule records the contact as skipped (already enrolled). Drag sequences up or down on the Sequences page to change priority. ## Common questions No. Stopping on reply is the core of the feature - once a real conversation starts, the automated cadence should never message over it. Yes. The rule measures total elapsed wait time between two touches on the same channel. SMS, then a call task 12 hours later, then another SMS 6 hours after that, still violates the rule - the two SMS are only 18 hours apart. Any change to a sequence with active enrollments is blocked, not just additions. Duplicate the sequence and make the change on the copy. Nothing - they continue through their remaining steps. Only future enrollments are blocked. To stop in-flight contacts, remove them from their step lists individually.