The goal is simple: one message, enough context, predictable routing.
Pick a reason, the page shows the clean path, and your draft is built with the details that prevent back‑and‑forth.
Updated: —
• Local time —
• Read time —
• Message ID —
Billing stack used: Outseta (portal/subscriptions) + Stripe (payment processing/receipts).
A different domain is normal for providers — the safe rule is: start from qix.studio, then follow official provider flow.
We do not request payment through DMs. If someone does, treat it as a scam attempt.
PROCESS
What happens after you send it
This is the “no mystery” version. A clean message turns into a clean response because it reduces clarifying questions.
01
Triage
Your topic (support / billing / advertising / security) determines the response path.
The page draft includes context (device, time, URL) to reduce “what browser?” back-and-forth.
02
Verification (when needed)
For billing or account requests, verification may be required to protect you.
The safe pattern is friction on sensitive actions, not friction on simple questions.
03
Next action (clear and specific)
You should get a response that explains what happened and what happens next.
If the issue is platform/provider related, we’ll tell you exactly what part is provider-side.
The design rule: reduce confusion, not add it.
WRITE
Write once. Route it correctly.
This composer generates a clean email draft to hello@qix.studio.
It auto-suggests a template based on topic (no extra buttons), includes optional technical context,
and runs a safety scan to reduce accidental sensitive data leaks.
Auto templatesSafety scanDraft preview
Router (choose your reason)
This doesn’t auto-redirect. It tells you the best route and shapes the draft.
Use “Critical security” only for real security risk (phishing links, account compromise signs).
Best route:
Contact
Use this page for general messages. If you need a fix right now, use Start Intake or Instant Fix.
Quick link check (optional)
Paste any link you were sent. We’ll classify it: official domain, provider portal, or suspicious lookalike.
No “verify” button — it updates as you type.
Keyboard: press / to focus the message box. Press Esc while focused to clear it.
Bonus: Ctrl+K / ⌘K toggles the menu.
Composer (builds your draft)
If something broke, paste the exact URL. “The site” is not a URL.
Billing can involve Outseta + Stripe receipts. IDs help. Card details do not.
This appends non-sensitive context that helps troubleshoot.
Turn off if you prefer a minimal draft.
Best format: symptom → steps → expected → actual → urgency. Topic templates auto-fill if this is blank.
Do not include passwords, 2FA codes, or full card numbers. If you accidentally paste sensitive data,
the safety scan will warn and redact likely patterns — still, double-check before sending.
DRAFT PREVIEW
Auto-updates as you type
Loading…
If your device doesn’t support mailto drafts (or the message is very long), use “Copy draft” and paste into an email to hello@qix.studio.
BILLING
Billing and receipts (Outseta + Stripe)
Billing workflows can involve Outseta (portal/subscription context) and Stripe (payment processing and receipts).
If you’re writing about billing, include the email you used at checkout and any receipt/invoice identifier.
✓Checkout email used for purchase.
✓Receipt/invoice ID (if available).
✓What you expected (receipt, access, cancellation, plan change).
✓What happened (error message or behavior).
If you didn’t receive a receipt, check spam/promotions and confirm the email used at checkout.
Billing safety rules
Never send full card numbers, passwords, or 2FA codes.
QIX doesn’t need them to help you.
If anyone requests payment through DMs, crypto, gift cards, or a domain that isn’t official/provider, stop and verify:
Scam Alert •
Sitemap.
WHAT TO INCLUDE
The details that prevent back‑and‑forth
Most delays are missing context. The draft generator already helps, but this is the checklist
that turns “we’ll look into it” into “here’s the next action.”
✓Exact URL where the issue occurred.
✓Steps to reproduce (even 1–2 steps).
✓Expected vs actual behavior.
✓Receipt/invoice ID if billing related.
✓Timing (when it started, how often it happens).
Good message example: “On /advertising, checkout popup opens blank on Safari iOS 17. Steps: tap Pro → popup opens → white screen.”
Bad message example: “The site is broken.”
SCREENSHOTS
If you attach a screenshot
Screenshots can help a lot — as long as they don’t leak private data.
Before sending:
Blur/redact card numbers, addresses, and personal identifiers.
Hide passwords, OTP/2FA codes, or recovery codes.
If it’s a billing screen, show the receipt/invoice identifier — not sensitive payment data.
The safety scan helps, but screenshots are manual — they can’t be auto-redacted here.
VERIFY
If a link feels off, trust your instincts
Clones rely on speed and confusion. QIX pages are built for brakes.
The safe route is: type qix.studio manually, navigate from the menu, and verify suspicious links before clicking.