SkyGrid DevelopmentWebsites, systems, and workflowsSupport is separate from project discovery so active customers can report an issue or request a change without entering a sales conversation.
Include the affected page or workflow, what you expected, what happened, when it happened, and any screenshot that helps explain the issue. Do not email passwords or full payment details.
For a SkyGrid-installed intake, booking, order, auction, payment, notification, or reporting workflow.
For content corrections, broken pages, display problems, accessibility concerns, analytics questions, or planned site updates.
For a SkyGrid-built portal, internal tool, dashboard, integration, or other custom application.
For invoices, project documents, ownership, access coordination, or a question that does not match the technical categories.
Use this form for an existing SkyGrid website, workflow, custom system, account note, requested change, content update, or file handoff.
Complete the WebFormafy support form below so SkyGrid receives the context needed to route and review the request.
Support starts with the active agreement and the information available. New scope, external vendors, and missing access can change the path to resolution.
Tell us: whether customer activity, payment, staff work, or a scheduled launch is blocked.
What it means: availability and response expectations follow the active support agreement and known business impact.
Tell us: whether an approved feature stopped working or you want different behavior, content, pages, or integrations.
What it means: new requirements may need clarification and a separate estimate before they can be scheduled.
Tell us: which platforms, accounts, or outside services are involved and whether anything recently changed.
What it means: vendor availability, permissions, limits, and account ownership can affect diagnosis and timing.
Tell us: the affected link, account role, record reference when safe, expected result, and actual result.
What it means: credentials, full payment details, and sensitive customer information should not be sent by ordinary email.
Support stays focused on active and completed projects. A new workflow, page, feature, integration, portal, or system begins through the project path that can evaluate scope and responsibility.
Use one email thread per issue when possible, and keep credentials or sensitive customer information out of the message.