5 reasons to use Inflowwww when chatting with fans. Reason 5 is the price.

Chatting is where most of an account's time goes, and it gets messy the moment two people work the same inbox. Here are five things Inflowwww does about that today, each with the screen it lives on.

1. One chat list for the whole team

Messages Pro (/messages-pro) is the inbox: a chat list on the left, the thread in the middle, fan insights on the right. On a phone it shows one pane at a time, so a chatter away from a desk can still answer.

How to set it up for a shared inbox:

1. Open Messages Pro and use the Owe reply filter as the shift's default view: it lists every chat where the fan wrote last, even if someone already opened it. Unread only shows what nobody has opened.
2. Use Sort by to put the most recent conversations first during a shift, and switch the order when you sweep for old threads.
3. Pop a conversation out into its own window when you want one fan on a second monitor.

Agree on one rule: whoever opens a thread finishes it or leaves a note. Two people answering the same fan is worse than a slow answer.

2. Find the right content without leaving the chat

Content lives in Growth > Vault Pro, where the owner sorts media into folders and gives each item tags, a description and a one-line caption. Chatters then attach media from the vault straight from the composer.

What makes this work in practice:

• Name folders by what a chatter is looking for mid-conversation ("new this week", "customs delivered", "teasers"), not by shoot date.
• Write the caption field as the sentence you would actually send. It saves typing later.
• Re-check folders once a week. A vault that nobody prunes becomes a search problem again.

3. Reuse the replies that already work

Growth > Scripts holds saved replies. Each one has an optional title (it shows in the picker), the text, and optional vault media and price. The same screen manages the account's welcome message.

Start with five scripts, not fifty:

1. A first reply to a new subscriber.
2. A check-in for a fan who has gone quiet.
3. A thank-you after a purchase.
4. A polite no for a request the creator does not do.
5. A short line that introduces a paid item.

Scripts are a starting point. Ask the team to change at least one phrase before sending, so fans never get the same paragraph twice.

4. Keep a fan snapshot next to the thread

The fan insights rail shows what a chatter needs before they type: Lifetime spend, Tips, Sub status, Sub price, Subscribed at, Renewed at, Last seen and Last purchase, plus the fan's recent PPV purchases. There are free-text Notes, Tags, a Custom nickname and Pinned messages.

Use notes for facts the fan has told you: time zone, what they like to talk about, what they asked you not to bring up. Use tags for anything you want to filter on later. A good handover note is two lines long.

5. It costs $0

Inflowwww is MIT-licensed and runs on your own server with Docker Compose. There is no per-creator fee, so adding a fifth or a fiftieth creator does not change the software bill. Under $500: $0. Over $75,000: still $0.

What you do pay for is the server and, if you turn them on, optional LLM provider keys, billed by that provider. The dashboard works without them.

Your first week

• Day 1: install it and capture one creator's session.
• Day 2: sort that creator's vault into five folders.
• Day 3: write the five scripts above.
• Day 4: invite one chatter from Employees > Manage employees.
• Day 5: run a shift and read the Message dashboard afterwards.

The pitch. Everything above runs on a server you control. Setup is a few commands from the README; after that, the team works in a browser. Deploy it yourself.