# Contact FanaticFactory.

- Canonical: https://fanaticfactory.com/contact
- Markdown: https://fanaticfactory.com/markdown/contact.md
- Type: contact
- Title: Contact FanaticFactory | Questions and Support
- Description: Contact FanaticFactory with questions, concerns, setup help, billing questions, partnership ideas, or Factory support needs.

## Summary

Questions, concerns, billing weirdness, setup confusion, partnership ideas, or a Factory that needs a human? Send it here.

## What this desk routes

_Best reasons to reach out_

## Details

- **Owner support**: Bring the creator, audience, niche, proof, first-community idea, and what feels unclear so the answer can lower risk before the owner commits energy to the community.
- **Creator fit**: Ask for help when the audience signal, community promise, return loop, revenue path, or trust boundary still needs a sharper pass.
- **Pricing and revenue**: Ask about paid access, events, products, services, coaching, marketplace paths, fee step-downs, and how to keep the community from feeling like a checkout counter.
- **Owner and customer support**: Bring the route, factory context, member state, account context, what happened, what you expected, and whether the issue is setup, support, payments, hosting, or distribution.
- **Concierge and partnerships**: Use contact context when the work needs an operator read: community floor plan, launch help, education, support load, product distribution, or a partnership conversation.

## Send context that makes the next answer useful

_What to include_

## Details

- **If it is a question**: Tell us what you are trying to understand and what decision the answer will help you make.
- **If something broke**: Include the Factory name or slug, page route, account/member context, what you expected, and what actually happened.
- **If it is billing or payments**: Tell us whether this is about paid access, purchases, refunds, payout questions, receipts, or a payment flow that behaved strangely.
- **If it is a Factory idea**: Name who the Factory is for, what they should do together, and what is unclear before you build it.

## Related Links

- [Pricing](https://fanaticfactory.com/pricing): Review the no-platform-fee transaction model.
- [Use cases](https://fanaticfactory.com/for): Choose the audience shape first.
- [Features](https://fanaticfactory.com/features): Map the request to product surfaces.
- [Guides](https://fanaticfactory.com/guides): Read owner education before or after contact.
- [Compare](https://fanaticfactory.com/compare): Clarify the platform bet.
- [Create or sign in](https://fanaticfactory.com/login): Use the app flow for account-specific context.