An unclaimed corporate gift is not one clean status. The invitation may have failed to arrive, the recipient may have opted out, the claim window may still be open, or the gift may have been claimed while a downstream order remains unresolved. A useful follow-up process separates those events before anyone sends another message or calls the remaining budget “unused.” This guide gives campaign operations and finance a shared decision method and a downloadable, versioned ledger. It is an operating template, not a messaging system, legal opinion, or promise that every unclaimed balance is refundable.
Start with the decision, not the reminder
The first question is what action an owner needs to take today. “Unclaimed” by itself does not answer it. A campaign operator may need to correct an undelivered invitation. A privacy owner may need to suppress further outreach. A finance partner may need to reconcile a reserved amount against a contract. A support team may need to help someone whose claim succeeded but whose order has an exception. Putting those situations into one follow-up list produces both unnecessary contact and misleading budget reports.
Define a campaign-level policy before processing rows. It should state who is eligible, the invitation channel, the claim deadline and time zone, what counts as a completed claim, whether any reminder is allowed, the maximum number and spacing of reminders, the suppression rules, the source of financial truth, and the person authorized to close the campaign. Record the contract or campaign reference beside the policy. A spreadsheet can flag an apparent due date; it cannot decide whether a message is lawful or whether money is owed back.
For US email, the Federal Trade Commission's CAN-SPAM compliance guide explains that a message's primary purpose matters when classifying it. An invitation or reminder should not be called “transactional” merely because it relates to a gift. The communications and legal owners should review the actual message, audience, sender, and suppression process. Outside the US, use the applicable local rules and your own counsel rather than carrying over a US classification.
The working unit should be a unique invitation ID, not an email address. Link it to a campaign ID and a pseudonymous recipient key. Keep contact details and send capability in the approved system of record, not in the workbook. That reduces unnecessary copying and makes it easier to delete or correct records later. The Giftpack recipient-data operations hub covers the broader lifecycle; this workbook concentrates on the specific decision after an invitation remains open.
Use a state model that can be audited
A row should represent an invitation, while evidence of consent, reminders, claims, expiry, funding, and exceptions stays in separate, linked records. The invitation ID is the common join key. Do not overwrite “sent” with “claimed” and then lose the original send date. Retain occurrence time, recorded time, source, and the person who changed the state. Late-arriving claim or credit evidence can then be reconciled without pretending the original report was always final.
At minimum, distinguish invitation prepared, sent, delivered or delivery unknown, open for claim, claim recorded, expired without claim, canceled, and exception under review. Treat “delivered” as a claim supported by a delivery receipt, not as a synonym for “sent.” Treat “claim recorded” as a recipient action supported by the platform's source event, not as proof of physical delivery. For a more detailed metric dictionary, see the Giftpack redemption-rate guide. A follow-up queue should use those definitions rather than quietly create a second definition of redemption.
| Observed state | Candidate next action | Required evidence before action | Who decides |
|---|---|---|---|
| Invitation not confirmed delivered | Investigate delivery or correct a permitted channel | Send and delivery logs, current contact permission | Campaign and communications owners |
| Delivered, unclaimed, before deadline | Consider one policy-approved reminder | Claim lookup, opt-out lookup, cadence, deadline and copy approval | Campaign and privacy owners |
| Opted out or contact basis withdrawn | Suppress outreach and retain minimal audit record | Suppression event and effective time | Privacy owner |
| Claimed, fulfillment unresolved | Route to support, not a claim reminder | Claim and order references | Operations and support owners |
| Expired without claim | Close invitation and reconcile value | Deadline, claim cutoff, contract terms and ledger entry | Campaign and finance owners |
The table is a decision aid, not a rule engine. For example, “delivery unknown” may reflect missing telemetry rather than a failed email. A local owner can choose investigation, a different approved channel, or no further contact. The acceptance test is whether each action is traceable to a current source event and an authorized policy—not whether every row receives a reminder.
Build a small, governed source ledger
Download the English ten-sheet follow-up workbook and the English UTF-8 invitation CSV. Both are version 1.0, verified on October 16, 2026. The CSV is an invitation-entry template, not an export of personal data or all ten sheets. In the workbook, Instructions sets a fixed as-of date and names the campaign and contract owners. Invitations holds a campaign ID, unique invitation ID, pseudonymous key, market, invitation date, deadline, funding type, and reserved value. Consent, Reminders, Claims, Expiry, Funding, Exceptions, Methodology, and QA have separate purposes so one mutable cell is not asked to explain an entire lifecycle.
Start by importing only the minimum approved identifiers. Use a recipient key that cannot be decoded by a casual reader of the file. Keep the protected mapping in the existing recipient system. On import, check duplicate invitation IDs, blank campaign IDs, missing or inconsistent deadlines, currencies and funding types, and values that have no contract reference. A duplicate may be a re-send of the same invitation, a replacement invitation, or an import error; do not delete it until the source owner decides which. The workbook flags duplicates; the owner resolves them in the source and records the correction.
Keep times and dates explicit. One market's midnight may be another market's previous afternoon. The workbook's as-of date is manually editable and makes a review reproducible, but it does not replace the campaign's actual time-zone rule. If an invitation expires at a particular instant, the approved platform event and time zone must control. A date-only spreadsheet row is insufficient to settle a close-call claim. Freeze the reporting cutoff, identify late arrivals, and rerun the report under a new version rather than changing a previously signed figure silently.
Limit access to people who need to review the queue or reconcile funding. Avoid exporting recipient addresses to a broad operations sheet. Protect the source, define a retention period, and plan deletion or correction. The Taiwan Ministry of Justice's Personal Data Protection Act, Japan's Personal Information Protection Commission guidelines, and Korea's Personal Information Protection Act are primary starting points for local privacy review, not a substitute for market-specific legal advice. The workbook deliberately avoids a universal consent conclusion.
Decide whether a reminder is due—and whether it may be sent
A scheduling flag and a sending authorization are different. The workbook labels a row DUE only when its planned date is on or before the chosen as-of date, its deadline has not passed, reminder permission is marked Y, and the row is not marked opted out, claimed, or already sent. A missing planned date or deadline produces CHECK. A negative permission or a positive suppression state produces SUPPRESS. A later planned date produces WAIT. These are triage labels, not messages, API calls, or legal permissions.
Before sending anything, an operator should re-query the authoritative systems for claim, opt-out and delivery status. A recipient might claim the gift after the morning export but before a scheduled afternoon reminder. A suppression event can arrive from another channel. The owner should review the exact campaign policy, approved message and recipient segment, then record the decision and time. If sending is automated in a separate authorized system, configure that system to repeat the suppression check immediately before dispatch and preserve its own send receipt. Do not wire a spreadsheet formula directly to a mailer.
An executable manual checklist is short enough to be performed for every batch:
-
Confirm the campaign and invitation IDs resolve to one current recipient record in the approved source.
-
Confirm the claim window and time zone from the campaign configuration, not a copied date alone.
-
Refresh claim, opt-out, frequency and prior-send state immediately before outreach.
-
Verify the approved communication basis, sender, language, copy and channel for that market.
-
Record the human approval, sent/not-sent result and evidence reference; route uncertain rows to Exceptions.
Choosing no reminder can be the right decision. When a gift was intended as a low-pressure gesture, a second prompt may diminish the experience. When a recipient has opted out, suppression is not a performance problem to solve by trying another channel. When the deadline is close, the owner may extend it if contract and campaign policy allow, but that is a new controlled decision, not a formula-derived entitlement. Compare a reminder, a support-assisted correction, an approved extension, and no further contact against the same evidence, rather than ranking one tactic by an unverified average response rate.
Treat expiry as a separate event
“Unclaimed at 9 a.m.” does not mean “expired.” Expiry requires the applicable deadline to have passed and no valid claim by that cutoff, subject to the campaign's late-event policy. Record the configured deadline, time zone, any authorized extension, the claim-event cutoff, and the final review time. The workbook marks EXPIRED only when the recorded deadline is before its as-of date and the row is not marked claimed. It marks CLAIMED for a claimed row and CHECK when the deadline is missing. Its date-only flag is a queue for source verification, not the final legal or financial state.
An expiry review should distinguish at least four outcomes. A never-delivered invitation may deserve delivery investigation or a policy-approved remediation. A valid unclaimed invitation can close without recipient contact. A claim that posted late in analytics but occurred before the authorized cutoff may require a correction. A claim submitted after an authorized extension may require a different cutoff and an audit note. Record which outcome applied and who approved it. If two systems disagree, keep both event timestamps and the conflict in Exceptions until resolved.
What if a claim and expiry appear on the same day?
Use the actual configured instant and event time, not alphabetical event order or the workbook's date cell. Preserve the platform receipt, applicable time zone, any extension approval, and the reconciliation decision. Until those facts are resolved, keep the row in Exceptions and do not book it as unclaimed value.
Closing a recipient invitation does not automatically settle a purchase order, vendor credit, or accounting entry. It also does not necessarily mean the person will never receive the gift: support may be resolving an eligible late claim. The operational close and the financial close need distinct owners and evidence.
Reconcile budget without manufacturing a refund
Finance needs to know which amount was funded, which amount remains reserved for open invitations, what was actually claimed or charged, and which refunds or credits have been explicitly confirmed. The workbook's Funding sheet separates those categories. Its available balance is the nonnegative funded amount minus open reserve, claimed amount, confirmed refund, and confirmed credit. An OVER flag identifies a negative raw balance that requires investigation. This is an exposure check, not a general-ledger rule: an organization should adapt categories to the funding contract and ensure the same obligation is not counted twice.
Giftpack's public pricing FAQ says that treatment of unclaimed or unused budgets depends on the contract, campaign and funding type. It also distinguishes points and credits. Therefore a campaign operator should not translate “unclaimed” into “refundable,” “cash available,” or “credit issued.” A booked refund needs a confirmed transaction or contract-supported receivable. A platform credit needs its own terms, date and reference. Gift value reserved for an open invitation is not free to reuse just because the person has not claimed it yet.
Agree on a reconciliation equation for the campaign before comparing reports. One useful control is funded value versus open reserve, settled claim value, confirmed returns, and explicitly unallocated balance. If source systems have different timing, record a reconciling item rather than forcing the numbers to match. Tie each category to its system of record, currency, as-of instant, campaign ID, and finance owner. If currencies differ, use a separately approved conversion policy and preserve both source currency and converted reporting value. This template contains no foreign-exchange assumptions.
The result should support a decision, not merely show a green cell. A negative available balance might mean double-counted reserves, a late claim, a missing funding entry, or the wrong campaign ID. An apparently large balance might mean an unposted claim or a contract restriction. Hold any reallocation until finance identifies the cause and documents the disposition. Do not advertise unused budget savings from a draft reconciliation.
Worked decision one: a reminder that should not go out
Hypothetical case. A regional people team has a gift campaign with invitations open until a recorded deadline. An operator schedules a reminder for a recipient whose invitation still looks unclaimed in yesterday's export. The workbook initially shows DUE: the date is in range, the local row says reminders are allowed, and the prior-send field is N. Before the send, the operator refreshes the source. The recipient had opted out through another channel that morning. The current source event changes the decision to SUPPRESS.
Inputs are the campaign policy, invitation ID, planned date, deadline and time zone, last claim event, last suppression event, prior send receipt, and approved message. The campaign operator owns the queue; the privacy owner owns the suppression rule; the communications owner owns message approval. The operator records the opt-out event reference, cancels the planned reminder, and does not move to a different channel unless separately authorized. The workbook row is corrected, but the authoritative suppression record remains in the protected system.
An alternative would be to send because the previous export showed no opt-out. That would maximize apparent process completion but use stale evidence. Another alternative is to pause every campaign whenever a single row changes; that may be needlessly broad. The bounded choice is to suppress the affected invitation, log the timing gap, and review whether the refresh window or system handoff needs repair. Acceptance evidence is the absence of a send receipt for that row after the opt-out, a timestamped suppression event, an exception or audit note, and a follow-up control test. No response-rate lift is assumed.
Worked decision two: expiry does not release money
Hypothetical case. A client gifting campaign closes with several invitations not claimed by the approved cutoff. Operations marks their invitation rows expired, but finance notices that the funding report still shows a reserved amount. A manager proposes moving the apparently “unused” value to another campaign. The contract owner has not yet confirmed whether the funding model permits a cash refund, platform credit, carry-forward, or no recovery. Expiry is supported; financial disposition is not.
Inputs are the original funding agreement, campaign ID, invitation IDs, claim and expiry events, paid invoices, refund or credit notices, and the funding ledger. The campaign owner confirms the close decision and time zone. Finance reconciles the reserved value against actual claims and payments. The commercial or procurement owner obtains the applicable contract interpretation. Until then, the Funding sheet records the amount as an open reconciling item, not as a confirmed refund or available cash. A later verified credit receives its own date and reference rather than overwriting the expired invitation state.
The alternatives are to reallocate immediately, wait for confirmation, or request an authorized amendment. Immediate reallocation risks double spending or misstating cash; indefinite waiting obscures the issue. The practical route is a dated exception with an owner and review deadline, plus a separate decision when contract evidence arrives. Acceptance evidence is a zero unexplained variance or a documented reconciling item, a contract-supported disposition, and a finance sign-off. No claim is made that Giftpack or any vendor returns all unclaimed value.
Run a weekly control and a final close
A weekly review should start with the exceptions, not a redemption percentage. Identify duplicate invitation IDs, missing deadlines, inconsistent funding types, opted-out rows still marked for reminder, claimed rows still on a reminder queue, reminders after expiry, and negative or unexplained funding balances. Assign each to one owner and a source system. The workbook's QA sheet gives a starting duplicate and over-allocation count; it does not complete the investigation. Keep an exception open until the underlying record is corrected or a documented exception is approved.
Use a simple cadence: operations freezes an as-of export, refreshes claim and suppression evidence, and proposes actions; privacy or communications reviews outreach; support handles access or claim issues; finance reconciles value; the campaign owner signs the cycle. At final close, record the cutoff, counts of invitations by mutually exclusive final state, unreconciled exceptions, funding disposition, deletion schedule and archive location. Version the workbook when definitions, policy, formulas or contract assumptions change. Do not silently replace a signed file and leave links pointing to a different binary.
Public reporting can be narrower than internal reconciliation. Report a claim rate only with its numerator, denominator and observation window, and keep pending delivery or refunds separate. Do not publish recipient-level rows. When a change is material, annotate the prior report and publish a corrected version. A good close is not “every invitation got a reminder”; it is “every invitation received a supported decision and every financial category has an owner and evidence.”
Choose the right implementation path
For a small, time-limited campaign, the downloadable workbook can be an effective governed review surface when exports are controlled and the owner signs each cycle. Its advantages are transparent formulas and low setup burden. Its weaknesses are manual refresh, limited access controls compared with a purpose-built system, and greater risk of stale suppression data. Keep contact details out of it and confirm current events before outreach.
For a recurring, high-volume program, a governed data pipeline and campaign platform may be safer. The platform can maintain current invitation and claim events; the organization's consent and communications systems can maintain suppression; finance can reconcile contract-specific value. Integration reduces copying but creates new failure modes: late events, key mismatch, duplicate sends, and partial sync. Specify ownership, idempotency, alerting, deletion and rollback before automating. A dashboard alone does not resolve those controls.
Giftpack can be considered as one execution option where its verified gifting workflow fits the organization's recipient experience and campaign needs. Compare any vendor—including Giftpack—using the same criteria: recipient choice, invitation and claim evidence, local delivery fit, export capability, privacy responsibilities, funding and expiry terms, support escalation, and total cost. Ask each vendor for the exact contract and data-flow evidence. Do not rank vendors by fabricated scores or assume that a feature present in one market is present in every market. The organization still owns audience, legal, payroll or tax decisions, outreach policy and financial accounting.
Conclusion: close the loop with evidence
The useful output of follow-up is a defensible decision for each invitation: investigate delivery, send one authorized reminder, suppress contact, support a valid claim, close an expired invitation, or resolve a financial exception. Keep those decisions separate so a missed claim never becomes an invented refund and a scheduling flag never becomes permission to contact someone. The v1.0 workbook and CSV provide a starting ledger; the campaign's actual policy, source events and contract must supply the facts.
If your team is evaluating an execution layer for recipient choice and campaign delivery, review Giftpack's approach alongside your own privacy, communications and finance controls. Use it only where the verified service and contract fit the decision you have already defined.