Skip to content

Domain deep dive — CRM & sales support

Purpose

Single D1 narrative for engineers changing customer support, lead/client records, incidents, or promotions. It ties together:

Generated CRM & sales DocType reference
API inventory — e.g. api/issue.py, bulk upload, FAQs where relevant
Feature catalog — support tickets, company search

Domain boundary

In scope	Out of scope (link instead)
Support Ticket, Incident, Client Info, Clients List	Application incorporation pipeline — Incorporation & application
Promotion Code, Promo Code packages/services	Stripe payment products — Finance & AR
Candidate / client records	Full HR recruitment — ERPNext HRMS unless customized

DocType cluster (generated)

Sub-theme	Examples
Support	`support_ticket`, `incident`
Clients	`client_info`, `clients_list`, `candidate`
Promotions	`promotion_code`, `promo_code_package`, `promo_code_services`

Index: crm-sales.

Code map

Layer	Primary locations
APIs	`api/issue.py`, `api/bulk_upload.py`, `api/website_faqs.py` — cross-check API inventory
Desk	Standard DocType forms under Lee Kim Alliance ERP (confirm workspace on site)

Overlay priority (for `overlays.json`)

Priority	DocType keys	Rationale
P1 — Overlays present	`support_ticket`, `client_info`, `promotion_code` (see `overlays.json`)	Ticket SLA, client master, promos
P2	`incident`, `clients_list`, `promo_code_package`, `promo_code_services`	Escalations and bundle pricing
P3	`candidate`	Recruitment-specific; overlay if used in production

Failure modes (where to look)

Symptom	First checks
Ticket API errors	`api/issue.py`, auth, Security checklist
Promo not applying	Promotion Code validity, package links, Stripe alignment
Duplicate clients	Client Info uniqueness rules, import scripts

Logs: Error Log, API access logs for guest endpoints.

Engineering deliverables — governance policies (orthogonal to this domain narrative)
Feature catalog
Security checklist
Domain documentation strategy
Documentation upgrade roadmap