Server colocation, rack space and cloud hosting for business workloads

Hands-on coordination

What Smart Hands can help coordinate

Smart Hands requests work best when the task is specific and authorised. Share the device, location name and expected outcome so Colo ICC can review the right next step.

Equipment checks

Ask for visual checks around a named server, appliance or rack item when your team cannot inspect it in person.

Cabling context

Provide port labels, device names and the intended connection path before requesting a cable or port-related check.

Power actions

Describe the device and approval contact before asking about reboot or power-cycle coordination.

Task follow-up

Include names, timing, references and any change notes so the request can be routed and confirmed clearly.

Before you request Smart Hands

Send enough detail for the task to be understood

A Smart Hands request should explain the equipment, location context and exact outcome your team wants. That detail helps Colo ICC review whether the request can be routed and coordinated clearly.

Do not send passwords, private keys or sensitive credentials in a first email. Colo ICC can advise the appropriate next step for sharing access details if needed.

Device and location context

Share the service or location name, device label, rack or unit reference if known, and the person authorised to discuss the task.

Task objective

Describe what needs to be checked, connected, identified or power-cycled, including the expected result after the task.

Timing and contact path

Include preferred timing, change reference if your team uses one, and the phone or email contact who can confirm the next step.

Need hands-on task support?

Contact Colo ICC before requesting Smart Hands work

Share the device, location context, task objective and authorised contact. Colo ICC can then review the request and route the next conversation clearly.

Useful details to send
  • Device name, label or rack reference if known
  • Requested task and expected result
  • Preferred timing and approval contact
  • Any change reference your team already uses