On this page

“Something went wrong” can describe a misspelled order reference, an unavailable verification service or a claim that already completed. Those situations require different customer actions. Reusing the same message leaves the recipient guessing and often encourages a retry that cannot solve the problem.

A useful error catalog begins with the action the customer can safely take. The technical cause informs the message, but the interface should explain the recovery path without exposing sensitive system detail or inventing a capability the program does not provide.

Classify errors by the action the customer can take

Separate errors the customer can correct from conditions that require the service or support team to act. A format error can point to an input field. An unavailable verification service should not tell the customer that their identity information is wrong. An expired session should explain the approved restart route, not declare the underlying reward ineligible.

W3C’s form-notification guidance recommends understandable feedback about submission results and instructions that help users correct errors. The W3C notification tutorial provides the accessibility basis; the catalog below is an original application to a hypothetical reward claim.

Use the actual program’s supported states. If the system cannot tell whether a submission completed, do not write “Nothing was saved” merely to encourage a retry. That statement could be false. The content needs a distinct uncertain-outcome state and an approved way to establish the existing result.

For each error, record four things: what is known, what the customer can do, what they should not do and when support becomes relevant. This structure keeps the recovery decision visible while allowing technical teams to map their own documented conditions to the copy.

Pair each error with a specific recovery instruction

The following fictional catalog includes complete sample messages. Its routes must be replaced by the actual approved actions before use in a live program.

Confirmed condition Sample message Safe recovery action Escalation boundary
Order reference has an invalid format “Enter the order reference exactly as shown in your purchase confirmation.” Correct the identified field Help if the reference cannot be located
Required field is empty “Enter the purchase reference to continue.” Complete the named field Explain why the field is needed if unclear
Verification service unavailable “We cannot complete verification right now. Your information has not been marked incorrect.” Follow the stated retry or support route Provider/service issue if persistent
Session expired before confirmed completion “This session has ended. Use the approved return route to check your claim and continue.” Re-enter through the supported access method Help if access cannot be recovered
Submission outcome unknown “We cannot confirm the result of this submission yet. Check the official claim status or use the support reference below before repeating it.” Establish existing result Responsible support team
Claim already completed “This claim step is already complete. Use your confirmation for the next program instruction.” Stop repeating the completed task Help if the confirmation cannot be found

The distinction between verification unavailable and information incorrect is especially important. A service failure should not create an adverse statement about the recipient. Likewise, “already completed” is a useful state explanation, not necessarily an error the customer must fix.

Keep button text aligned with the recovery action. “Try again” fits only when retrying is the approved next step. “Review claim status,” “Return to the approved access page” or “Contact claim support” may be more accurate in other cases. The label should describe the action’s actual result.

A difficult case is a backend error whose raw message includes a customer identifier, internal path or sensitive reference. The customer-facing copy should use an approved generic description of the relevant problem and a safe support reference. Do not display raw diagnostics merely because they are available to the interface.

Another difficult case involves several correctable fields. Explain the overall result and identify each field that needs attention. The customer should not have to fix one error, resubmit and discover the next hidden issue repeatedly. The implementation must use appropriate accessible associations and focus behavior, which the team should verify in the actual claim surface.

Preserve safe form context without exposing sensitive values

Where the approved design permits it, retain non-sensitive entries that do not need to be re-entered after a correctable error. Do not promise that every field is saved. Sensitive values, security codes or provider-controlled verification data require their own handling and should not be echoed into error text or support logs.

Write a clear statement about context when it changes the customer’s next step. For example: “Your order reference remains entered; review the highlighted date field.” If the form restarts under the actual process, explain what must be entered again. The message should reflect verified behavior rather than a desirable design that has not been implemented.

Review the catalog using scenario cards. In an authorized test setup, submit a malformed reference, trigger a known unavailable-service state, resume an expired session and revisit a completed claim. For each case, record the expected message, observed message, available action and whether the action can actually complete the recovery.

Do not test uncertain-outcome behavior by creating uncontrolled live awards. Use the approved test arrangement and verified scenarios. The content review should establish that the message corresponds to the known state, not manufacture real financial consequences to see what happens.

Include the support team in the review. A button labeled “Contact claim support” should lead to a team that recognizes the safe reference and understands the error category. Otherwise the interface merely moves the confusion into a ticket.

The final deliverable is a catalog in which each error has one truthful explanation and a supported next action. Customers can correct what they control, wait or escalate what they do not, and recognize when the task has already completed. That makes the claim journey easier to recover without exposing internal details or turning uncertainty into an incorrect eligibility decision.

Discuss the recovery messages needed in your approved rebate claim experience.

Discuss customer experience

Source references

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.