Support

HELP, ONBOARDING, AND SUPPORT

Use this page to reach the right Aurelia team for onboarding, billing, product questions, card issues, profile publishing, or rollout planning.

Contact lanes

Reach the right team the first time.

A production-ready product site should make support feel clear. Aurelia uses separate paths for general conversations, product support, and public documentation.

General

Product conversations

Walkthroughs, partnerships, founder deployments, sales conversations, and general brand enquiries.

Support

Account and product help

Account help, onboarding questions, billing issues, bugs, and card or profile support.

Coverage

Docs, FAQ, and support

Public answers for cards, NFC cards, hosted profiles, pricing, product behavior, and legal basics.

Best for the support centre

  • Account access and sign-in issues
  • Card and hosted profile publishing questions
  • Billing, renewals, and plan corrections
  • Bug reports, incidents, or broken flows
  • Questions about what data is visible on a public profile

Best for the contact page

  • Product walkthroughs and demos
  • Strategic partnerships and integrations
  • Press, brand, and community enquiries
  • Founder and enterprise discussions
  • Early access or rollout conversations for teams

When you write in

What to include so support can help faster.

Good support pages reduce back-and-forth. If you contact Aurelia, a little context will make the resolution path much cleaner.

The email tied to your Aurelia account or plan
A short description of what went wrong or what you need
The relevant card, profile URL, or shared link if the issue involves a public page
Your device, platform, or plan details when the issue is account-specific

Coverage

A good product site should answer the basics and make human help easy to find when you need it.

Aurelia uses documentation, FAQ, and support together. The site should help users self-serve where possible and reach the right person quickly when they need a real reply.