The primary source of processing delay is the qualification loop triggered when a dealer submits a request using a generic email domain (Gmail, Yahoo, Outlook.com, etc.). All other steps are low-friction and require minimal time. This SOP documents all paths including the inquiry loop so the process can be standardized, delegated, and eventually automated.
A dealer or installer completes the MSP contact form at digital-watchdog.com/msp-contact-form. This generates a case in the CRM. The case will contain the following data fields:
Check the domain of the submitting email address. This determines which qualification path applies.
This is the primary source of processing delay. Follow these steps in order before proceeding:
A domain validation check on form submission could flag generic emails in real time, prompting the submitter to provide a business domain before the case is created. This would eliminate the inquiry loop entirely for this scenario. Flagged for Ideas Platform Proposal.
Confirm that the dealer is an active member of the Digital Watchdog Channel Partner Program (CPP). MSP platform access is restricted to CPP members only.
CPP status could be a real-time lookup on form submission — if the email domain matches a non-CPP account, the form could surface a CPP enrollment prompt before the case is even created. Flagged for Ideas Platform Proposal: CPP + MSP Unified Intake.
Before provisioning, verify that no organization has already been created for this dealer on the requested platform(s). Duplicate organizations are not permitted.
Create the Channel Partner organization on each requested platform using the information from the verified CRM case. To create a new end-user organization in the myDW CP portal, navigate to: Login → Organization List → EU Org. Enter the required business information and save — the primary contact will receive an invitation email to set up their access.
Successful provisioning generates a CP (Channel Partner) Organization Number for each platform provisioned. Record this number immediately — it is required for the CRM update in Step 6.
Return to the dealer's CRM account record and log the CP Organization Number generated in Step 5.
If the provisioning platforms expose an API or webhook, the CP Org Number could be written back to the CRM automatically upon successful org creation — eliminating this manual step entirely. Flagged for Ideas Platform Proposal.
Send the welcome email to the primary contact immediately following successful provisioning and CRM update. This is Touch 1 of a 4-touch post-provisioning communication sequence.
The 4-touch sequence (Touches 2–4) is a strong candidate for CRM-triggered automation — once a case is marked "Provisioned," the sequence fires automatically on a schedule. Touch 1 may remain manual to allow for personalization. Flagged for Ideas Platform Proposal.
Escalate to distributor partner contact for verification. The distributor relationship is the source of truth for CPP eligibility when direct CRM verification is not possible.
Provision only the platform for which SLA acceptance is confirmed. Note on the case that the second platform is pending SLA acceptance and send the appropriate SLA link to the dealer.
Do not create a new org. Retrieve the existing CP Org Number from the CRM Subscriptions Object and connect the dealer with platform support to restore access to their existing organization.
Send the CPP enrollment page link (digital-watchdog.com/page/chptnr) and a brief overview of the program benefits. Flag the case as "Pending CPP Enrollment" and follow up after 5 business days.
Apply the following status labels to cases in the CRM to maintain visibility across the onboarding funnel and support leadership reporting.