Laifaxin Sync Sequence Settings

Laifaxin Campaign and Sequence Setup

Apply the reusable email-campaign workflow to Laifaxin while preserving the low-level sequence safety checks learned from real plan configuration.

Read the required references

1. Read references/laifaxin-campaign-workflow.md completely for every task.
2. Also read references/sequence-sync-sop.md completely when configuring, cloning, auditing, or repairing intelligent follow-up sequence steps.
3. Also read references/audience-pool-enrollment-sop.md completely when searching the AI database, creating or reusing customer groups, applying market exclusions, adding contacts to plans, checking counts or overlap, or removing plan members.
4. Use the signed-in Laifaxin browser session and follow the available browser-control skill for UI work.

Start every task

1. Read all conversations, instructions, websites, research, customer files, and other materials explicitly in scope. Do not ask the user to convert them into a form.
2. Extract project facts and campaign choices automatically. Separate user decisions, source-backed facts, recommendations, and inferences.
3. Mark an uncertain conclusion as an inference. Never present it as confirmed.
4. Ask once only for material blockers that affect scope, external identity, truthfulness, safety, or sending results.
5. Treat a user-designated final instruction or verified Laifaxin plan as the current source of truth.

Choose the operating mode

• Prepare: Produce the brief, list requirements, copy, sequence, settings, test plan, and launch checklist. Do not change Laifaxin or send.
• Configure: Configure only the authorized Laifaxin lists, plans, sender, timing, and rules. Stop before any send or activation unless separately authorized.
• Inspect: Read state and report ready, warning, and blocking items. Do not modify unless the user asks for fixes.
• Test send: Send only to approved internal test addresses after confirming sender, subject, body, and recipients.
• Formal send: Require immediate final approval of sender, audience and count, copy, schedule, and batch limits before launch.

Default to Prepare when the requested mode is ambiguous.

Execute the campaign workflow

1. Build the project brief from current materials.
2. Normalize and validate recipient data when lists or sending are in scope.
3. Define each campaign's audience predicate, exclusions, email-status rule, target count, per-company cap, and non-activation state before searching or enrolling contacts.
4. Apply the audience SOP step by step for AI-database search, saved groups, asynchronous jobs, deduplication, bounded enrollment, or cleanup.
5. Segment only when the distinction changes the message, rules, or follow-up.
6. Prepare or verify copy without unsupported claims or deceptive personalization.
7. Configure Laifaxin sender identity, reply routing, sequence, timing, limits, and advanced rules as authorized.
8. Apply the sequence SOP step by step when copying or repairing sender and timing settings.
9. Run the pre-launch gate before any test or formal send.
10. Test, launch, and monitor only within the approved mode and scope.

Audience and enrollment invariants

• Treat a search result, saved view, contact tag, plan customer list, and active sending audience as different objects; verify each one independently.
• A success message proves only that Laifaxin accepted the request. Wait for background processing, then verify the saved-group count and the plan customer count.
• Never assume cross-plan deduplication or country accuracy. Test the current account behavior and disclose unresolved uncertainty.
• Use campaign-specific saved groups. Do not add one broad group to several plans without explicit approval and an overlap check.
• When the target is a minimum count, add bounded batches toward the remaining gap plus an agreed buffer; do not enroll an unlimited result set.
• Keep every newly populated plan inactive. Adding contacts never authorizes activation or sending.

Sequence synchronization invariants

• Learn the sender and timing from a user-verified source plan or explicit settings.
• Never hardcode or persist a sender label or internal account ID.
• Never copy a sender unavailable in the target account.
• Never fill the hidden sender input. Use the visible sender dropdown.
• Require exactly one sender before saving.
• Require source and target step counts to match unless the user supplies an explicit mapping.
• Do not save while sender options are open, templates are loading, or the selection is ambiguous.
• During sender/timing-only work, leave templates, subjects, bodies, contacts, customer counts, advanced rules, reply-stop rules, plan names, and activation state unchanged.
• Treat example schedules as named examples, not universal defaults.

Authorization and safety boundaries

• Do not send, activate, pause, add contacts, expand an audience, remove plan members, repurpose a saved group, or change content unless the request authorizes that action.
• Before any destructive removal, capture an export or a demonstrably reconstructable source, state the exact plan and visible count, explain rollback limits, and obtain explicit confirmation at the action point.
• Never delete an existing plan merely to create capacity without explicit authorization and a verified backup or export.
• Never store passwords, app passwords, tokens, customer secrets, or complete recipient lists in the skill.
• Preserve original customer data and create a separate cleaned version when file processing is requested.
• Never fabricate or falsely claim email verification, domain authentication, legal compliance, or manufacturing evidence.
• Follow applicable consent, sender-identification, opt-out, privacy, and anti-spam requirements; flag uncertainty rather than guessing.
• In configuration or inspection mode, report abnormal bounce, complaint, or authentication signals without changing plan state.
• In an explicitly authorized active monitoring workflow, pause affected sending and report abnormal signals.

Completion report

Return five compact sections:

1. Project requirements identified
2. Standard Laifaxin logic applied
3. Work completed
4. Warnings and blockers
5. Next step and external actions requiring approval

Include the source plan, target plans, steps checked or changed, sender used in the current session, schedule, exact recipient counts and evidence source, applied exclusions, account quota observations, pending background jobs, overlap warnings, unchanged fields, plan state, validation results, and unresolved exceptions.