cloudek.HOSTING PVT LTD Discuss a requirement
CLOUDEK · ENQUIRY GUIDE

Support or a project?
Start with the right boundary.

Cloudek describes infrastructure support and project work as service areas, not fixed packages. This guide helps distinguish the two kinds of conversation. No service commitment is implied. Availability, exact scope, access, capacity, fees, timing and deliverables must be confirmed in a customer-specific written agreement before work begins.

Enquiry only. A draft email does not book work, establish an SLA, approve system access or authorize changes. Keep the first enquiry high level; do not send credentials, customer exports or diagnostic evidence.

✓ Exact scope before work✓ Service and project terms kept separate✓ Changes need their own approval
Prepare an enquiry Review the service conversation
01ONGOING SUPPORT · IF AGREED

Define what is covered

A support discussion can identify included systems and request categories, permitted requesters, service hours and communication channels, customer dependencies, and any escalation process. Coverage, reporting cadence and response targets exist only when specifically reviewed, capacity-checked and accepted in writing; none is implied here.

Explore the support enquiry guide
02PROJECT WORK · IF AGREED

Plan a bounded change

A project discussion can identify its objective, named systems, milestones, dependencies, deliverables and objective acceptance evidence. Any implementation requires a separate approved change record with an authorized owner, window, prerequisites, rollback or stop conditions, and post-change verification. A recommendation or report is not change authorization.

Explore the project enquiry guide

What must be agreed before work

  1. Choose the work type. Separate recurring operations from a time-bounded project; do not use one scope to imply the other.
  2. Name boundaries and owners. Confirm authorized contacts, included systems, exclusions, dependencies, access, data handling and delivery capacity.
  3. Review commercial terms. The customer-specific agreement must state fees, tax/payment/cancellation terms, dates, deliverables and any service or response targets—or explicitly state that none apply.
  4. Accept the same written scope. Both parties must accept the controlling version before access or work. Changes, deployment and out-of-scope tasks require separate written approval.
Prepare a high-level enquiry
Limits and data handling

This guide is not a service offer, quote, contract, booking, SLA, security promise or evidence of available capacity. It does not authorize tenant access, remote connectivity, monitoring, incident response, system changes, deployment or use of customer information. Do not email secrets or raw exports; agree on an approved evidence channel and retention terms before sharing any customer material.

Questions before an enquiry

Is there a standard fee or response time?

No. Fees, coverage, capacity, service hours and any response targets must be reviewed and stated in an accepted customer-specific agreement. This page makes no commitment.

Can a support agreement include a project or migration?

Not by implication. A migration, deployment, modernization or other defined change needs its own scope, dependencies, commercial terms, change approval and acceptance criteria.

What should I include in an enquiry?

Share the broad outcome, general environment and whether you are considering ongoing support or a project. Leave out passwords, tokens, personal data, customer exports and sensitive diagnostics.