Aqelya support
Aqelya support is designed around the product and payment path that actually exists today. Do not send API secrets, private keys, customer data, card numbers, or production credentials.
Support triage
Each route tells you what to try first and the minimum non-sensitive evidence needed if the issue still requires review.
Try first: Use the Stripe success URL that opens Bridge Preflight Studio. Keep the session_id parameter in that URL.
Keep ready: Product name, purchase email, Stripe receipt, success/access URL, browser/device, and the exact access message.
Try first: Reopen the same paid Studio URL. If the existing report store is configured, Aqelya will attempt to recover the previously generated report automatically.
Keep ready: Purchase email, Stripe receipt, paid Studio URL, and whether a report was generated previously.
Try first: Confirm the input is OpenAPI/Swagger JSON under 1 MB with a version field and paths object, and remove all credentials or secrets.
Keep ready: Non-sensitive API title/version, analyzer error text, number of paths, and whether the spec contains external references.
Try first: Return through the verified Signals access URL that includes the Stripe checkout session reference, then open downloads from that protected page.
Keep ready: Purchase email, Stripe receipt, access URL, failed format, and browser/device.
Try first: Review the policy page and keep the Stripe receipt. Never send card numbers or full payment credentials.
Keep ready: Product name, purchase email, receipt, amount, date, and reason for review.
Try first: Start with Bridge Preflight or the live Bridge Lab, then describe the source scheduling platform, API surface, desired agent channel, and target timeline.
Keep ready: Organization, platform/API name, approximate merchant footprint, booking capabilities, and desired pilot outcome.
Direct routes
The bottom-right Aqelya Concierge provides the same guided routing anywhere on the site.
Concierge boundary
The current Concierge is deterministic product and support routing. Aqelya will only describe it as an AI chatbot after a real protected model backend, abuse controls, data boundaries, and cost controls are operational.