On this page

The store remains open online while the person who approves reward exceptions is away. A customer can still make a qualifying purchase, but the team may be unable to resolve an issue the campaign creates. Year-end planning should address that mismatch before reduced coverage begins.

The question is not whether every reward requires a person. It is which decisions in the actual approved journey may require one, who can make those decisions during the closure and what customers have been told to expect. A coverage grid turns a general holiday notice into a concrete operating decision.

List campaign decisions that may require a person

Start with the campaign’s actual unresolved situations. These might include an eligibility question, an approval exception, a missing record, a funding authorization or a customer complaint needing a named decision owner. List only tasks that belong to the merchant’s approved responsibilities, then identify the corresponding provider handoffs where relevant.

Distinguish routine progression from exceptions. A program may normally move through a step without merchant intervention, yet still require a person when records disagree or an approved limit is reached. A quiet period before the holiday is not proof that the exception path can operate unattended during a larger promotion.

Consider a fictional merchant planning a year-end closure for part of its central operations team. The online store will continue accepting orders. Customer support has limited coverage, but the usual campaign approver will be unavailable and the provider’s holiday arrangements have not yet been confirmed.

The initial review should name those gaps rather than summarize the campaign as mostly automated. If an exception occurs, a support representative may be able to acknowledge it but lack authority to approve the next step. Those are different capabilities and should appear separately in the coverage record.

Review outstanding cases before adding new ones. An unresolved customer promise from an earlier offer may cross the closure even if the merchant pauses new promotion. Pausing advertising does not remove the need to route that existing case to a responsible person.

Confirm coverage during the closure

Ask each owner and backup to confirm the period they cover, the decisions they can make and the route through which cases reach them. A name in a spreadsheet is not evidence of availability. Nor does a backup’s ability to sign in establish that they have authority to approve a particular program decision.

The following grid illustrates the fictional merchant’s review. It is not a statement about any provider’s actual service hours or holiday availability.

Decision or task Proposed owner Coverage evidence needed Customer-facing timing implication
Explain an existing offer Support lead Confirmed access to historical terms Publish only the response expectation this team can meet
Resolve an eligibility exception Program approver or authorized delegate Written delegation and availability Do not promise a decision while authority is unavailable
Approve a funding action Finance decision owner Confirmed authority and operating contact Avoid a delivery promise dependent on an unconfirmed action
Accept a provider escalation Named provider route Provider confirmation for the relevant interval Distinguish case acknowledgment from resolution
Handle a serious customer issue Duty manager Working escalation route and backup Ensure staff know where urgent cases go
Resume ordinary review Returning operations lead Reopening handoff and queue owner Explain the next update without inventing a cleared backlog

Where coverage remains unconfirmed, record an open dependency and the action required to resolve it. The fictional merchant cannot treat the provider escalation line as covered merely because a general contact form remains online. It needs the applicable arrangement for the relevant period and issue type.

Check that the backup can perform the intended work through approved access. They should be able to retrieve the necessary evidence and record a decision without sharing another person’s credentials or creating an improvised process. This is an operational readiness check; it should follow the organization’s existing access and authority controls.

A difficult case involves an owner who is technically reachable but unavailable for routine work. Define what contact is intended to cover. A route reserved for serious incidents should not become the unofficial queue for ordinary approval questions because no other plan exists.

Another difficult case is a handoff between time zones. Record the actual interval and handoff event instead of relying on a date label that each team interprets differently. The aim is to avoid a gap between the last person leaving and the next person accepting responsibility, not to assume that a public holiday has the same effect on every participant.

Choose which new offers can responsibly remain live

Compare the proposed new customer promises with confirmed coverage. An offer may remain appropriate if its approved progression and exception handling are adequately supported. Another may need revised timing, a narrower scope or a pause in new promotion. The decision should reflect the actual dependency, not a blanket assumption that all virtual rewards arrive without human involvement.

For the fictional merchant, suppose support can explain terms and accept cases, but no authorized eligibility approver is available during part of the closure. The merchant could review whether the planned offer’s stated timing can honestly accommodate that arrangement. If it cannot, the team should change the proposed campaign before inviting additional purchases under an unsupported expectation.

Do not solve an internal coverage gap by quietly changing promises already made. Existing qualified customers need an approved handling plan. If a communication adjustment is necessary, it should explain the actual status and next step without implying that the closure removed the underlying commitment.

Review the placements that create expectations about speed. A general holiday banner may not reach someone who enters through a product-specific advertisement or an old email. Make sure the relevant offer explanation reaches the customer at the point where they decide to purchase.

Before the closure starts, run one fictional exception through the handoff. Can the receiving person identify the offer version, obtain the evidence, recognize their authority limit and reach the next owner? If the exercise ends with an unanswered personal message to someone on leave, the grid still contains a gap.

Finally, assign the reopening task. The returning team should receive the outstanding cases, decisions already made and customer update commitments. A return to normal office hours does not automatically resolve work accumulated during the closure.

The completed coverage decision should state which offers remain live, what conditions make that possible and who owns unresolved issues throughout the period. That gives the merchant a practical basis for year-end promotion while keeping customer promises aligned with people who can act on them.

Discuss the campaign timing and handoffs needed during your year-end closure.

Discuss campaign fit

Back to contents

General information only

This guide is general information, not financial, legal, tax or regulatory advice. Eligibility, card availability, permitted use and responsibilities depend on the applicable offer and card terms.