Operational Notices
How HeartBadge communicates temporary service issues and what to do when a workflow is delayed.
Operational notices cover temporary conditions that can affect checkout, payment confirmation, email delivery, membership finalization, gifts, group seats, wallet activity, or security actions.
What a notice should include
- Affected area. The product surface or workflow involved.
- Observed impact. What members or operators may see.
- Safe action. Whether to wait, retry, use another supported path, or contact support.
- Last updated. The most recent confirmed information.
- Resolution. A clear statement when normal behavior is restored.
During a payment or finalization delay
Do not create a duplicate order, submit a second payment, issue another gift, or assign another group seat simply because a record remains pending. Open the existing record in HeartDash and follow the available action shown there.
During an email-delivery delay
Check spam and filtered folders, confirm the displayed email address, and wait for the resend control before requesting another code or invitation. Use the most recently delivered verification code. Never share a verification code, authenticator code, backup code, or full claim link with support.
Account-specific status
A general notice explains a broad condition. Your order, membership, gift, group, wallet, or security record in HeartDash remains the source of truth for your specific status and available next step.
When to contact support
Contact support@heartbadge.com when a record shows needs attention, an instructed retry repeatedly fails, or the displayed state does not match what you completed. Include the membership email, relevant order or record reference, approximate time, and exact message shown.