Inquiry routing
Give the problem enough context to reach the right discipline.
The contact page is the intake point for several different DSDillon practices. A useful inquiry identifies the affected system or decision, the business impact, what changed and the outcome the business needs. Credentials, passwords, private keys and highly sensitive operational details should remain out of public forms.
SECTION 01Website, search and analytics inquiries
Include the website or domain, the service or market involved, the symptom you can observe and any recent change. For search questions, name the exact visibility problem rather than sending a broad request to “rank the site.” For measurement questions, identify the action the business needs to track and where the current reporting breaks.
SECTION 02Business email and infrastructure inquiries
Provide the domain, affected addresses or service, whether the issue concerns sending, receiving, authentication, access or migration, and when it began. Do not send mailbox passwords. Diagnostic work can begin from DNS, message headers, provider information and controlled tests without exposing credentials through the public intake.
SECTION 03Real estate and property-management inquiries
State whether the matter concerns ownership, leasing, tenant onboarding, rent administration, maintenance or another property decision. Include the general property location, property type, current occupancy and the task you want DSDillon to handle. Sensitive tenant documents should move through an appropriate private channel when required.
SECTION 04Executive-security advisory inquiries
Describe the role, activity or operating concern at a high level and the decision the organization needs to make. Avoid publishing routes, schedules, live vulnerabilities or protective procedures in an open form. Immediate emergencies belong with the appropriate emergency or public authority.
SECTION 05What happens after intake
The initial information is used to identify the appropriate discipline and whether more evidence is needed before a scope can be defined. Complex work may require a structured assessment, access review or consultation before implementation. The written scope should state responsibilities, deliverables and material limitations.