Reviewing a vendor's support and escalation process

Review the support entitlement in the proposed offer by tracing a critical marketing incident from first report to recovery. At each stage, identify the channel, owner, timing or trigger, next action and evidence the customer will receive. A portal or service-level heading alone does not show that the route can handle the incident.

Choose an incident that matters

Use a plausible incident: a campaign blocked before launch, a stopped customer-data transfer, or loss of access during a live send. State who would notice, the business effect and the systems involved, then trace the route under the support package actually proposed.

Separate routine help from urgent incidents. Establish who assigns severity, whether the supplier can change it, and how a disputed classification is escalated. The proposed terms should make clear which route applies to the incident you chose.

Follow the route

Contact: identify which authorised user can report the incident, through which channel, and during what relevant Australian local hours. Check coverage outside business hours and across the team's time zones.

Triage: establish what information the report must include, who assigns severity and how the supplier handles a disputed classification. Identify any paid support tier and the roles of a reseller, integrator or software provider.

Response: determine whether a target means acknowledgement, human engagement or an update, and when its clock starts. Require the applicable terms to state the response and resolution targets; without a stated target, you cannot assess a time commitment.

Escalation: identify the trigger for each hand-off, who takes responsibility next and what fallback applies if that contact is unavailable. If the contract is through an integrator, establish whether the buyer can contact the provider directly or must use that intermediary.

Recovery: identify who can apply a workaround and who confirms restoration. Follow-up: establish what incident record and explanation the customer will receive.

Reviewing a vendor's support and escalation process for a critical marketing incident

Check the written commitment

Locate the support policy, service-level terms and escalation route that would apply to the purchase. Match them to the proposed support package, including hours, severity definitions, exclusions, update frequency and conditions for a remedy. A response target is not a resolution commitment.

Treat a stage as unresolved if the terms do not identify its channel, owner, timing or trigger, next action and customer-facing record. Record differences between a sales explanation and the proposed terms rather than assuming an explanation is a contractual commitment.

For a personal-information breach likely to result in serious harm, the Notifiable Data Breaches (NDB) scheme under Part IIIC of the Privacy Act 1988 (Cth) requires covered organisations and agencies to notify affected individuals and the Office of the Australian Information Commissioner (OAIC). Establish how the supplier's route connects to the organisation's privacy and security contacts; a support ticket alone does not establish that notification has occurred.

Support and escalation clarity: proposed offer vs. actual contract terms

Key support metrics from vendor’s proposed terms

Check the hand-off

For the campaign incident, write down the actual route in order: the authorised reporter and contact channel, triage and severity owner, response commitment, escalation hand-offs, recovery responsibility and follow-up record. Use the proposed support policy and service-level terms to fill each stage; leave a stage marked unresolved if they do not establish it.

The route is assessable when the terms let an internal owner tell who contacts whom, through which channel, during which hours, what happens if the case is escalated, and who can confirm recovery. Keep the resulting record accessible to the people who will operate the tool.