Troubleshooting guide
CRM Automation: Diagnostic Guide
CRM Automation: Diagnostic Guide organizes the decisions that matter for companies with poorly configured CRMs, inconsistent follow-up, or disconnected sales workflows: the current workflow, ownership, implementation choices, rollout risk, and acceptance evidence.
Working artifact
CRM Automation implementation-path comparison
Compare the smallest responsible paths before treating replacement as the default.
| Path | Best fit | Watch closely |
|---|---|---|
| Repair | The core of lead capture and form integration remains sound | Leads sit unassigned in a shared inbox |
| Extend | CRM data and workflow design has a stable, understood boundary | Follow-up depends on memory |
| Replace | Ownership or architecture prevents a responsible repair | Pipeline stages mean different things to each person |
Record the symptom before changing it
Leads sit unassigned in a shared inbox. Confirm who encounters it, where it occurs, and what changed before it appeared. Then distinguish the visible symptom from dependencies such as CRM data and workflow design.
- Save exact error text
- Record the last known working date
- List recent code, content, vendor, DNS, or account changes
Separate reachability, data, and behavior
For CRM Customization & Lead Automation, confirm account ownership, current exports or backups, recovery options, and recent changes before touching production. Preserve exact errors and timestamps that may disappear after a restart or update.
- Reachability check for rules, jobs, and notification automation
- Data or content check related to lead capture and form integration
- Behavior check for assignment and routing rules
Use stop conditions
Frame the first scope around lead capture and form integration and one observable acceptance journey. Treat assignment and routing rules as a later phase unless the evidence shows it is a true dependency.
- No confirmed backup
- Unknown production ownership
- Security or payment data may be involved
Verify the repair in the real journey
Repair fits when the core remains sound. Extension fits when the boundary around CRM data and workflow design is understood. Replacement fits when ownership, architecture, or operating risk prevents a responsible change.
- Lead capture and form integration
- Pipeline and lifecycle configuration
- Deduplication and data cleanup