Questions, made
legible.

ResolutionHub is a private, structured intake portal for consumer and merchant reports involving disputed coupons, offers, redemptions, and merchant listings. It helps users organize the relevant facts, provide useful evidence, and understand a potential next review step.

No. The portal does not make a legal finding, guarantee a remedy, or decide a dispute simply because a report is submitted. It captures information for review and can support an authorized routing or follow-up process.

Choose the consumer path if you were trying to use an offer, coupon, or redemption benefit. Choose the merchant path if your business is listed without permission, its offer terms are wrong, redemption activity appears abusive, or an active offer should be corrected or paused.

The current intake is designed for a denied coupon, a merchant that says it does not participate, inaccurate offer terms, failed app or QR redemption, unauthorized business listings, listing corrections, suspected redemption misuse, and requests to pause or remove an offer.

Use the consumer report path. Identify the merchant and location, explain what was shown and what occurred, and attach a receipt, screenshot, offer ID, or other supporting material if available. The report should focus on the specific event rather than general dissatisfaction.

That situation may be important for both parties. A consumer can report the attempted use and the merchant’s statement. A merchant can use the merchant path to report an unauthorized or inaccurate listing. ResolutionHub should treat the two reports as private, related intake records rather than public accusations.

Yes. Use the merchant path and identify the business, location, listing or offer details, what is inaccurate, and the correction or withdrawal requested. Include documentation showing your authority to speak for the business when it is relevant.

A merchant should provide a specific, factual description of the suspected duplicate, altered, expired, or abusive redemption activity. Do not include accusations that go beyond the information available. Attach the relevant offer, transaction context, date, location, and any internal reference that can help review the event.

No. The current report form is private by default and is not a public complaint board. A report should not be published as an allegation merely because it was submitted.

Useful evidence may include a receipt, offer screenshot, listing link, offer ID, written communication, date and location, or an image that shows the relevant terms. The goal is to make a specific event reviewable; you do not need a perfect case file to begin.

Yes. A clear description of what happened, the merchant or listing involved, the date or location, and the requested review can still be helpful. If you later obtain a receipt or screenshot, preserve it for follow-up.

Do not upload passwords, security codes, full payment-card numbers, unnecessary government ID, Social Security numbers, or files you are not authorized to share. If your account or card may be compromised, contact the relevant provider through its official support channel first.

The portal is designed for private intake. Authorized operational reviewers and configured service providers may process information needed to operate the case flow. A report or attachment should only be routed externally with the authorization or other lawful basis described in the intake and privacy materials.

The current standalone portal does not yet provide a self-service correction or deletion screen. Before public launch, ResolutionHub should publish a functioning request channel and a retention schedule. Do not use a second report merely to share sensitive replacement information.

No. Triage Chat is a guided six-step intake tool. It helps identify the appropriate path, issue category, whether the merchant or listing is known, whether evidence is available, and the next action. It does not promise an immediate response or a live agent.

The chat asks for consent and an email address before recording a handoff request. This creates a private request for potential human follow-up, but it does not guarantee a response time or a particular outcome. The portal should publish staffing coverage before claiming a review window.

Protect your account first. Do not share passwords or security codes in chat or uploads. Use the relevant bank, card issuer, account provider, or other official channel promptly. If there is an immediate safety risk, contact local emergency services. ResolutionHub cannot secure an account or investigate an emergency in progress.

A submitted report receives a reference so the report can be distinguished from other submissions. A case reference is not proof that the report has been resolved, independently verified, or accepted for a particular remedy.

Yes. After a completed report or consented handoff request, the portal provides a plain-text private summary download. Keep that file private because it may contain contact information and details of the incident.

The private admin workflow supports status management for submitted reports and handoff requests. A status represents a process stage, not a conclusion about who is right. Public case-status lookup and reporter notifications remain a future enhancement.

The Terms of Service and Privacy Statement pages explain the portal role, permitted use, evidence handling, forwarding authorization, and current implementation limits. Both are draft materials that require qualified legal review before public reliance.