IT Service Management: A Practical Support Brief for Melbourne Businesses

When an IT issue arrives through email, a phone call and an internal chat, who owns the next step? Before choosing another tool, document how your business wants support requests to be received, assigned and followed through.

This planning guide is for Melbourne and Victorian businesses reviewing their support arrangements. It is not a service-level agreement, technical response procedure or promise about resolution times.

Separate different kinds of work

Atlassian’s IT service management overview describes ITSM as the management of IT service delivery and support. It distinguishes several work types:

• Service request: a request for something, such as approved access or equipment.
• Incident: an unplanned interruption or reduction in service.
• Problem: investigation of the underlying causes of incidents.
• Change: a planned alteration that needs appropriate assessment and control.

These distinctions help frame a conversation with your provider. A new starter’s equipment request is different from an unavailable application. Repeated interruptions may need investigation beyond closing each individual support ticket.

Ask how your provider categorises these situations and who can correct a category when the initial information is incomplete.

Make ownership visible

Prepare a sample request record containing the affected service, a short description, business impact, contact person, assigned owner, current status and next update.

Agree which channel staff should use and how related messages will be linked to the same request. A reference number helps everyone identify the matter, but does not itself establish that work has started.

Ask who owns communication when a request depends on an external software or connectivity supplier. Clarify whether your provider coordinates that relationship or expects your business to do so.

Keep initial information proportionate. Do not put passwords, one-time codes, payment-card details or unnecessary personal information into ordinary tickets. Ask how sensitive diagnostic material should be shared if it becomes necessary.

Clarify hours and expectations

Write down the proposed support hours, applicable time zone, public-holiday arrangements and the route for issues outside those hours.

Discuss acknowledgment, assessment, updates and resolution separately. An automated receipt is not a human assessment; an acknowledgment is not a fix. Ask how priority is determined and how unresolved matters are escalated.

Any response targets, exclusions or service commitments belong in the agreed proposal or contract. Do not assume an advertised support channel means every type of work is included at every hour.

Agree change approvals and costs

Identify who in your organisation can approve access, purchases and changes. Ask what information will be supplied before a proposed change, including its purpose, affected services, dependencies, planned timing and approach if it does not work as expected.

Separate recurring support charges from project work. Ask whether onboarding, migrations, equipment, licences, site visits and after-hours work are included, separately quoted or usage-based. Confirm AUD, GST treatment and the approval process for extra charges.

A monthly fee should be assessed against its written scope, not treated as an unlimited commitment.

Start with a small review

Choose a few recent, anonymised support examples. Identify where ownership, status or expectations became unclear, then prepare questions rather than assigning blame.

Bring that brief to a Bestcomm conversation. Discuss the service scope and suitable next steps before authorising work. Bestcomm’s Australian focus is Melbourne and Victoria; other Australian locations are by agreement.

Cover image is illustrative, not an actual Bestcomm customer support engagement.