Customer Support & Ticketing Policy
Details how customers submit service requests, expected response times, and escalation paths.
Purpose and Objectives
The Customer Support & Ticketing Policy establishes the framework through which customers request assistance, report incidents, and track service issues within GridColo facilities. Data center operations depend not only on robust infrastructure, but also on clear, reliable communication channels between customers and GridColo's Network Operations Center (NOC). The objective of this policy is to provide customers with transparent processes for submitting requests, receiving timely responses, and escalating concerns, while ensuring GridColo maintains accountability and consistency in its support services.
Applicability
This policy applies to all GridColo customers, their authorized personnel, and designated vendors when submitting support requests related to colocation services. It covers requests for operational assistance, incident reporting, account or access issues, and facility-related concerns. It applies across all Security Levels (1–4) and for all categories of colocation service.
Policy Statement
GridColo is committed to providing responsive, professional, and transparent customer support. Support requests must be logged through official ticketing channels to ensure proper tracking and accountability. The NOC operates 24x7x365 and is empowered to respond directly to incidents, dispatch field staff, escalate to management, and coordinate communication with customers.
Support Channels
Customers may contact the GridColo NOC using the following channels:
Phone (24x7)
+1 (469) 273-1337. This line connects directly to the NOC for urgent issues or time-sensitive escalations.
Email (ticket creation)
noc@gridcolo.com. Messages sent to this address automatically generate a ticket in the support system.
Web Helpdesk
helpdesk.gridcolo.com. Customers may log in to create and track tickets, update requests, and review status.
All requests should be logged via ticket for accountability, even if first reported by phone.
Ticket Categories
When submitting a request, customers should categorize tickets as one of the following:
Incident
Unexpected outage, fault, or disruption requiring urgent response.
Request
Routine operational support such as remote hands, access updates, or information requests.
Change
Authorized maintenance or configuration activity initiated by the customer, subject to the Change Management & Work Authorization Policy.
Inquiry
General questions not tied to immediate operational needs.
The NOC will reclassify tickets if necessary to ensure accurate handling.
Response Targets
GridColo endeavors to respond to support requests within the following timeframes:
Critical Incidents (P1)
Acknowledgment within 15 minutes; action initiated immediately.
High Priority (P2)
Acknowledgment within 1 hour; action initiated within 2 hours.
Standard Requests (P3)
Acknowledgment within 4 business hours; resolution targeted within 1 business day.
Low Priority / Inquiries (P4)
Acknowledgment within 1 business day; resolution on best-effort basis.
Response times are targets, not guarantees, but GridColo will strive to meet or exceed them consistently.
Escalation Paths
If a customer believes a request is not being handled with appropriate urgency, they may escalate as follows:
First level
Call the NOC directly at +1 (469) 273-1337 and reference the ticket number.
Second level
Request escalation to the NOC shift supervisor, who will review ticket priority and dispatch resources.
Third level
Request escalation to the GridColo Operations Manager, who will assume ownership of the issue.
Final level
Escalate to executive management via the NOC, which will coordinate direct communication with a senior GridColo executive.
Escalation paths are available 24x7 for incidents and during business hours for standard requests.
Customer Responsibilities
Customers are responsible for:
- Submitting requests through official channels (phone, email, or web helpdesk).
- Providing accurate, detailed descriptions of the issue or request, including affected equipment, time of occurrence, and any troubleshooting already attempted.
- Updating tickets with relevant progress or closure information if the issue resolves independently.
- Ensuring only authorized personnel submit tickets on behalf of the customer organization.
NOC Responsibilities
The GridColo NOC is responsible for:
- Logging, tracking, and managing all tickets through to closure.
- Categorizing and prioritizing tickets appropriately.
- Providing updates at regular intervals until resolution.
- Coordinating dispatch of on-site staff or vendor support as required.
- Documenting root cause analysis (RCA) for significant incidents.
Communication Standards
All tickets will receive a unique tracking number. Customers may track status via email updates or the web helpdesk portal. Updates will be provided at intervals appropriate to ticket severity: hourly for critical incidents, daily for high-priority requests, and upon material changes for standard or low-priority tickets. All communications are logged for accountability and audit purposes.
Closure and Feedback
Tickets will be closed once the NOC and customer agree that the issue has been resolved or the request fulfilled. Customers may be asked to confirm closure. Closed tickets remain available for historical review. Customers are encouraged to provide feedback on support quality to help GridColo improve service.
Responsibilities and Enforcement
Customers must comply with this policy when requesting support. Repeated failure to follow process (e.g., bypassing ticketing for routine requests) may result in delays or limited service.
GridColo is responsible for maintaining responsive, accountable, and transparent support operations, and for updating this policy as practices evolve.
Effective Date and Amendments
This policy is effective upon publication and remains in force until replaced. GridColo may amend this policy to reflect evolving customer needs, technology improvements, or service model adjustments. Customers will be notified of substantive changes through the helpdesk portal and official communications.