Support

Aqelya support triage.

Use this page to resolve access, delivery, download, product-use, policy, or business questions. A secure AI support assistant is planned, but this triage path works now without collecting secrets or exposing private product files.

Support assistant

Choose the closest issue.

Each support path tells you what to try first and what context to keep if escalation is needed.

Support path

I paid but cannot access files

Try first: Open the after-payment link from Stripe. It should include a checkout session reference in the URL.

Keep ready: Product name, purchase email, Stripe receipt, access URL, browser/device, and a screenshot of the access message.

Support path

One download format failed

Try first: Try another format first: PDF for reading, text for assistant use, Markdown for reference, JSON for machine workflows.

Keep ready: Which format failed, what opened instead, purchase email, device/browser, and whether the other formats worked.

Support path

I do not know which file to use first

Try first: Start with the PDF Library Guide, then use the Prompt Library Text inside your assistant, then use Markdown/JSON only if needed.

Keep ready: Product goal, buyer type, and what you are trying to evaluate.

Support path

Product did not match expectations

Try first: Write down what you expected, what you received, and which product page or checkout message created the expectation.

Keep ready: Product name, purchase email, receipt, expectation gap, and whether you downloaded all formats.

Support path

Policy or refund question

Try first: Review the policy page. Duplicate charges, failed delivery, and broken access can be reviewed with receipt evidence.

Keep ready: Receipt, purchase email, product name, date, and reason for request.

Support path

Business or partnership question

Try first: Describe the product, audience, market, and whether you need licensing, enterprise use, or custom product support.

Keep ready: Organization, intended use, number of users, and timeline.

Useful routes

Open the right page faster.

Use these links to resolve most access and delivery questions before escalation.

Secure assistant roadmap

Bottom-right AI support requires a protected backend.

The next support build should add a secure assistant widget with rate limits, abuse controls, no payment-key exposure, no secret collection, clear data boundaries, and support-event logging. Until that is built, Aqelya should not pretend a real AI chatbot is active.