Support

Email support@amazifypro.org — response times by plan: Starter 24h · Growth 6h · MAX 1h on business days.

What to include in your email

The faster we know what's happening, the faster we fix it. Please include:

• Your license key (or order ID from Paddle) — or say you're on the free trial.
• Your Amazify Pro version (shown at the bottom of the sidebar, e.g. "v1.0.6") and your Windows version (10 or 11).
• The project or job that failed (if applicable) and the pipeline step it failed at — scrape, script, narration, render, thumbnail, or publish.
• A screenshot or copy of the error — the job log inside the project view shows the exact failing step.
• What you've already tried.

Common issues — try these first

Installation on Windows 10/11

Download the installer from GitHub Releases and run it — FFmpeg and Chromium ship inside, so nothing else needs installing. If Windows SmartScreen shows "Windows protected your PC", click More info → Run anyway; the warning appears simply because the installer is newly published. The installer drops a desktop and Start Menu shortcut, and the 3-day free trial starts on first launch — no card, no signup.

License activation says "wrong machine" — moving your seat

One license = one PC: your key is bound to the hardware it was first activated on. To move it, open Amazify Pro on the OLD computer → sidebar → License → Deactivate & release seat, then activate the same key on the new machine. If the old machine is dead, stolen, or reformatted, email us with your license key and we'll release the seat manually after verifying ownership.

AI provider setup — scripts won't generate

Amazify Pro is bring-your-own-keys. Open Settings → AI Providers and pick one: the built-in Template engine works offline with zero setup, Claude CLI is free with a Claude Max subscription, and Claude API, OpenAI GPT-4o, Gemini, Groq, OpenRouter and LongCat need an API key pasted under Settings → API Keys. If generation fails with a 401/403, the key is wrong or out of credit — test it in the provider's own dashboard. Keys are stored encrypted on your machine, so we can't check them for you.

Publishing connection failed (YouTube / TikTok / Instagram / Facebook)

Platform connections use OAuth tokens you authorize, stored locally. If an upload fails with an auth error, disconnect and reconnect the channel inside the app to mint a fresh token. Remember your plan's channel quota (Starter 1, Growth 5, MAX unlimited) is a lifetime count — removing a channel doesn't free the slot. TikTok and Meta tokens expire faster than YouTube's; reconnecting is the fix nine times out of ten. If the platform itself rejected the video (policy, duration, aspect ratio), the job log shows the platform's own error message.

Render fails or produces a black/silent video

Renders run on bundled FFmpeg, so codec packs aren't the issue. Check: (1) enough free disk space in your output folder — long-form renders can need several GB of temp space; (2) narration finished — if TTS failed the render has no audio track, so re-run the narration step; (3) B-roll sources — if Pexels/Pixabay keys are missing, disable B-roll auto-insert or add the free keys; (4) captions burn-in errors usually mean the caption step was skipped — re-run captions first. The job log names the exact FFmpeg step that failed; attach it to your email and we can usually diagnose in one reply.

Amazon scrape keeps failing or returns no products

Amazon throttles automated traffic in waves. Wait 10–30 minutes and retry, try a different storefront domain, or paste ASINs manually instead of searching by keyword. Make sure your affiliate tag is set in Settings so links are generated correctly.

I want a refund

Sure — we offer a 14-day full refund, no questions asked. Email us your license key and we'll deactivate the license and process the refund through Paddle. Money typically lands back on your card in 5–10 business days.

Response times by plan

• Starter — within 24 hours on business days.
• Growth — within 6 hours on business days.
• MAX — within 1 hour, priority queue.
• Refunds and lock-outs (can't activate, paid but no key) — top of the queue for every plan.

What we can't help with

A few things genuinely fall outside our reach. We'll redirect you to the right place:

• AI provider errors and billing — 429 rate limits, quota exhaustion, or charges from Anthropic, OpenAI, Google, Groq, OpenRouter, LongCat, or ElevenLabs are upstream issues. Check the provider's status page and dashboard.
• Platform account decisions — YouTube strikes, TikTok restrictions, Meta account reviews, demonetisation, or Amazon Associates account standing are between you and the platform. We can confirm the app did its part; we can't appeal on your behalf.
• Earnings strategy — we build the production pipeline; niche selection, thumbnails A/B testing, and channel strategy are your craft. The blog has our best playbooks.

Office hours

We respond Monday–Friday, 09:00–22:00 UTC. Weekends are slower — usually 12–24 hour turnaround. Urgent license issues (can't activate, paid but no key received) get bumped to the top of the queue regardless of plan.

Feature requests & bug reports

Got an idea or hit a bug? Email support@amazifypro.org with the subject line starting with "[Feature]" or "[Bug]". We read every message. The changelog shows what's shipped recently.

Contact

One inbox for everything: support@amazifypro.org. Use a clear subject line — "Refund request", "Privacy request", "Security disclosure", "Partnership", etc. — and it gets routed correctly.