Docs / LinkQR
Signup

Support

Open tickets and follow support conversations.

Estimated reading: 2 minutes

Support

Support lets users create tickets and follow replies from the support team. Admins can manage categories, labels, comments, and ticket state from the admin support area.

Good support requests

  • Include the affected Bio page, QR campaign, or domain.
  • Describe the expected result and the actual result.
  • Add screenshots or scan URLs when possible.
  • For billing issues, include invoice or transaction context.

Support - Detailed Feature Guide

Feature Purpose

Open tickets and follow support conversations. This feature is part of the LinkQR workflow and should be documented as an operational tool, not just a menu item.

Main Capabilities

  • Creates a structured help workflow between users and administrators.
  • Supports ticket review, categories, labels, types, comments, and status management.
  • Useful for billing issues, domain setup, QR scans, account access, and technical problems.
  • Keeps support history attached to the user request.

Typical Workflow

  1. Open the Support page from the sidebar.
  2. Review the existing records, settings, or campaign state.
  3. Create or update the required item.
  4. Validate important fields before saving.
  5. Preview or test the public/user-facing result when applicable.
  6. Use analytics, logs, or reports to confirm the feature is working as expected.

Admin Configuration Notes

  • Confirm the feature is enabled in the correct plan.
  • Check workspace ownership when users work inside a team.
  • Review related limits such as credits, storage, QR count, scan count, or team members.
  • Clear cache and test again after changing global settings.

Customer-Facing Benefits

  • Reduces manual work and makes campaign setup faster.
  • Keeps campaign assets organized and easier to maintain.
  • Improves reliability by keeping important setup steps inside one workflow.
  • Supports better reporting and troubleshooting after launch.

Troubleshooting Checklist

  • If the feature is not visible, check plan permission and user role first.
  • If saved data does not appear publicly, verify publish/status settings.
  • If a public URL is involved, test the URL in a private browser session.
  • If team workspaces are involved, confirm the item belongs to the correct owner workspace.
  • If tracking or analytics is involved, confirm the visitor action uses the tracked dynamic URL.