A new employee can need several technology services before their first working day, but an MSP should not build accounts from a vague message saying that somebody is starting. A structured starter request helps the provider confirm authority, required services and timing while keeping the client's own onboarding responsibilities distinct.
Use an agreed request route
Ask clients to submit starter information through the MSP's approved service channel rather than relying on messages to individual technicians. This creates a traceable request and reduces the chance that important onboarding work remains in somebody's personal inbox.
Confirm the requester is authorised
Follow the provider's established client-authorisation process before creating or changing access. A convincing email or urgent phone call should not replace whatever approval controls the MSP and client have agreed.
Collect only the information needed for the setup
Identify the user's relevant business details, start timing and required technology services without turning the IT ticket into a duplicate HR record. The client remains responsible for deciding the person's role and access requirements.
Separate standard access from exceptions
If the client has an agreed baseline for a type of user, apply it through the normal process. Requests for additional privileges or unusual systems should be made explicit and approved appropriately rather than copied from another employee without review.
Coordinate account and device readiness
A user may need both service accounts and physical equipment. Keep these workstreams linked to the same starter request so the MSP can see whether one part is ready while another remains outstanding. Do not mark the onboarding complete simply because an account exists.
Manage lead time realistically
Late starter requests can create pressure for immediate action, especially when equipment must be sourced or third-party services are involved. Give the client a factual status and prioritise within the agreed support process rather than bypassing security or quality checks to meet an unsupported deadline.
Record what was provisioned
Update the relevant service or asset records when work is completed. Clear documentation helps later support and gives the MSP a reliable basis when the client eventually requests role changes or offboarding.
Close with a defined handover
Confirm the technical setup through the agreed client route and handle any initial credentials or activation steps using the provider's approved security process. The client should know what is ready, what remains their responsibility and what outstanding item, if any, still needs action.