diff --git a/TODO-cove-data-protection.md b/TODO-cove-data-protection.md
index 93f88dd..fd74295 100644
--- a/TODO-cove-data-protection.md
+++ b/TODO-cove-data-protection.md
@@ -342,7 +342,7 @@ Other backup systems that use APIs:
 **Effort:** Low (2-3 days)
 **Value:** Low (storage metrics only, no backup monitoring)
 
-### Option B: Request Expanded API Access from N-able
+### Option B: Request Expanded API Access from N-able ⭐ RECOMMENDED
 **Contact N-able support and request:**
 1. MSP-level API user capability (cross-customer access)
 2. Access to restricted column codes:
@@ -364,6 +364,96 @@ Other backup systems that use APIs:
 **Effort:** Unknown (depends on N-able response)
 **Value:** High (if successful)
 
+---
+
+### 📧 Support Ticket Template (Ready to Send)
+
+**To:** N-able Cove Data Protection Support
+**Subject:** API Access Request - Backup Monitoring Integration
+
+**Email Body:**
+
+```
+Hello N-able Support Team,
+
+We are developing a backup monitoring solution for MSPs and are integrating
+with Cove Data Protection via the JSON-RPC API for our customers.
+
+Current Situation:
+- We have successfully authenticated with the API
+- API endpoint: https://api.backup.management/jsonapi
+- API user management: https://backup.management/#/api-users
+- Method tested: EnumerateAccountStatistics
+- Role: SuperUser + SecurityOfficer
+
+Current Limitations (Blocking Integration):
+We are encountering "Operation failed because of security reasons (error 13501)"
+when attempting to access essential backup monitoring data:
+
+1. Backup Status Fields
+   - Cannot determine if backups succeeded, failed, or completed with warnings
+   - Need access to status/result columns
+
+2. Timestamp Information
+   - Cannot access last backup date/time
+   - Need reliable timestamp fields to track backup frequency
+
+3. Error Messages
+   - D02Fxx and D03Fxx column ranges are blocked
+   - Cannot retrieve error details to show users what went wrong
+
+4. API User Scope
+   - API users are customer-scoped only
+   - Need MSP-level API user capability for cross-customer monitoring
+
+Impact:
+Without access to these fields, we can only retrieve storage usage metrics,
+which is insufficient for backup status monitoring - the core requirement
+for our MSP customers.
+
+Request:
+Can you please:
+1. Enable MSP-level API user creation for cross-customer access
+2. Grant access to restricted column codes containing:
+   - Backup status (success/failed/warning)
+   - Last backup timestamps
+   - Error messages and details
+   - Session/run history
+3. Provide documentation on the semantic meaning of column codes (especially
+   D01F00-D01F07 and D09F00 which currently work)
+4. OR suggest an alternative integration method if expanded API access is
+   not available (webhooks, reporting API, email notifications, etc.)
+
+Technical Details:
+- Our test results are documented at:
+  docs/cove_data_protection_api_calls_known_info.md (can provide upon request)
+- Safe columns identified: I1, I14, I18, D01F00-D01F07, D09F00
+- Restricted columns: Entire D02Fxx and D03Fxx ranges
+
+Use Case:
+We need this integration to provide our MSP customers with centralized backup
+monitoring across multiple backup vendors (Veeam, Synology, NAKIVO, and Cove).
+Without proper API access, Cove customers cannot benefit from our monitoring
+solution.
+
+Please advise on the best path forward for enabling comprehensive backup
+monitoring via the Cove API.
+
+Thank you for your assistance.
+
+Best regards,
+[Your Name]
+[Company Name]
+[Contact Information]
+```
+
+**Alternative Contact Methods:**
+- N-able Partner Portal support ticket
+- Cove support email (if available)
+- N-able account manager (if assigned)
+
+---
+
 ### Option C: Alternative Integration Methods
 Explore if Cove has:
 1. **Reporting API** (separate from JSON-RPC)