Account Merge and Duplicate Profile Support Workflow Builder
Design a safe support workflow for duplicate customer profiles, account merge requests, identity checks, audit logging, and rollback planning.
Prompt Template
You are a support operations manager designing a safe workflow for duplicate profiles and account merge requests. Build a support process for: **Product/account system:** [SaaS, marketplace, ecommerce, community, fintech, healthcare, etc.] **Duplicate triggers:** [same email, social login, typo email, migration issue, household accounts, CRM sync] **Customer request:** [merge accounts, transfer purchases, consolidate history, delete duplicate] **Data involved:** [orders, subscriptions, messages, saved payment methods, health/financial data, user content] **Identity verification requirements:** [email OTP, ID check, admin confirmation, security questions, SSO] **Support tools:** [help desk, CRM, admin panel, data warehouse, engineering queue] **Risk constraints:** [privacy, fraud, compliance, irreversible merges, enterprise tenants] Create a complete workflow with: 1. **Eligibility rules** — when accounts can be merged, linked, transferred, or must stay separate. 2. **Do-not-merge conditions** — fraud risk, different legal owners, enterprise tenant boundaries, payment conflicts, active disputes. 3. **Verification script** — customer-friendly identity checks before any action. 4. **Agent decision tree** — triage path by request type and risk level. 5. **Step-by-step merge workflow** — pre-checks, backup/export, merge action, post-checks, customer confirmation. 6. **Support macros** — intake, verification needed, merge complete, unable to merge, escalation. 7. **Escalation path** — when to involve trust & safety, privacy, billing, engineering, or legal. 8. **Audit log fields** — what to record for accountability. 9. **Rollback or remediation plan** — what to do if the merge was wrong or incomplete. 10. **QA scorecard** — how supervisors review merge tickets. Prioritize customer privacy, irreversible-action safeguards, and clear agent instructions.
Example Output
# Duplicate Profile Workflow: LearnLoop
Eligibility Rules
Accounts may be merged when the same verified person controls both emails, neither account is under enterprise SSO, and the merge only consolidates course history, certificates, and preferences.
Do-Not-Merge Conditions
- One account belongs to a school-managed tenant and the other is personal.
- Payment methods or invoices belong to different legal entities.
- The customer cannot verify both email addresses.
- Either account has an active fraud, chargeback, or privacy investigation.
Verification Script
“Before I make any changes, I need to confirm you control both accounts. Please verify the code sent to each email address. We will not merge payment methods, and you will receive a confirmation summary before we close the ticket.”
Agent Workflow
1. Confirm request type: merge, transfer, delete duplicate, or link only.
2. Verify both emails with OTP.
3. Check tenant ownership, billing status, disputes, and admin restrictions.
4. Export profile snapshot IDs to the ticket.
5. Perform merge in admin panel using the primary account selected by the customer.
6. Confirm course history, certificates, and preferences moved correctly.
7. Send completion macro with what changed and what did not.
Audit Fields
Ticket ID, agent ID, primary account ID, duplicate account ID, verification method, merge timestamp, data types moved, exclusions, customer confirmation link.
Tips for Best Results
- 💡Treat account merges as high-risk because they can expose private history to the wrong person.
- 💡Document do-not-merge rules as clearly as merge rules; agents need safe stopping points.
- 💡Always record account IDs and verification evidence before making irreversible changes.
- 💡If rollback is not technically possible, add a second approval step for risky merge types.
Related Prompts
Screen Recording Bug Report Intake Workflow Builder
Design a support intake workflow that helps customers submit useful screen recordings, reproduction steps, device details, and privacy-safe bug evidence.
Missing Item in Package Support Workflow Builder
Create an ecommerce support workflow for missing items in delivered packages, including triage, macros, replacements, fraud checks, and fulfillment feedback.
Customer Complaint Response Template
Write a professional, empathetic customer complaint response that resolves issues and preserves the relationship.