Chat inbox, synced with Fanvue
Every conversation from every model in one place, updating in realtime as messages arrive. Conversations are stored by the CRM, so a thread opens instantly instead of waiting on the platform.
sentryq is the CRM we built to run our own creators' inboxes: every conversation, every payment, every shift, in one place. Now it runs yours — your own database, your own login, your own address, provisioned while you watch.
An example of what you will see. Nothing is provisioned until at least one of your models has subscribed through Fanvue.
Since 2025-09.
One agency.
Including the night.
Webhook to inbox.
What you get
Everything below is the software we run our own creators on. You get the same build, on your own infrastructure, updated when we update ours.
Every conversation from every model in one place, updating in realtime as messages arrive. Conversations are stored by the CRM, so a thread opens instantly instead of waiting on the platform.
Subscriptions, tips, pay-per-view and referrals, cut against your own timezone, per model and per chatter. The numbers reconcile against what Fanvue shows you.
A weekly planner, a clock your chatters punch, break and away rules, and two pay-period surfaces: what the platform attributes and what the team reports.
Score real conversations against your own rubric, leave coaching notes on the message they refer to, and track whether a chatter is getting better month over month.
Your openers, your offers and your hard limits, in front of the chatter at the moment they are writing — with a forbidden-words check before anything sends.
Segment by what a fan has actually done, send a blast, and see what it earned. Sends are attributed back to the chatter or campaign that made them.
A new subscriber gets the first message within seconds, in your voice, without anybody being awake. One engine, so there is never a double welcome.
Expiring promotions are watched and re-created before they lapse, so a discount campaign does not quietly stop at 3am on a Sunday.
Whales, quiet spenders, fans at risk, new subscribers. Built from spend and behaviour the CRM already records, not from a tag somebody forgot to apply.
Every asset, organised per model, with the same picture resolved once across every conversation it was sent to rather than re-fetched per fan.
Per-link attribution for paid traffic, a postback receiver for your ad platform, and a fan journey that survives the move from click to subscriber.
Shift goals with bonuses your chatters can see while they work, so the target is in the same screen as the conversation that hits it.
sentryq Cloud is a web app. It runs in any modern browser on desktop and tablet. The desktop companion app that ships with our single-agency install is not part of v1.
Isolation
Every agency gets its own database, its own storage and its own address. That is a deployment decision, not a policy — the separation is structural, so nothing we could get wrong in code exposes one agency to another.
A Postgres instance created for you, with its own credentials.
There is no shared table with a tenant column, so there is no forgotten WHERE clause that could return another agency's rows.
A private bucket holding your vault and your message attachments.
Keys are scoped to your prefix, so a bug in one workspace cannot list, read or overwrite another's files.
Your chatters' accounts exist in your workspace and nowhere else.
There is no global user table and no cross-workspace session, so an account cannot be pointed at a different agency.
Your tokens are sealed with AES-256-GCM before they touch a disk.
They are decrypted only inside your own container, for your own requests, and never appear in a log or an API response.
A subdomain of your own with its own certificate.
Your chatters' bookmarks, and the cookies behind them, belong to a host nobody else uses.
How it works
Creating a workspace is free and asks for no card. Nothing is provisioned, and nothing is charged, until one of your models subscribes through Fanvue.
Pick a subdomain and a timezone. This takes a minute and costs nothing — there is no card field anywhere in this flow.
One consent screen on Fanvue. We read your roster so we know which models exist, and we ask for the scopes the CRM needs to run their inboxes.
Open the sentryq listing in the Fanvue App Store from the Fanvue account of the model you want covered, and subscribe. $100 per month, billed by Fanvue to that account. Repeat for each model.
The hub asks Fanvue which of your models now hold a licence. As soon as one does, provisioning starts.
Fourteen steps, live on screen. At the end you get the address of your own CRM and the owner login for it.
Pricing
You pay for the models you want covered. Chatters, managers and QA reviewers are unlimited and free.
Per model
$100per month
Billed through the Fanvue App Store. Each model's own Fanvue account subscribes to the sentryq app, and Fanvue charges that account. No card details ever reach us.
Creating a workspace is free. Nothing is charged until a model subscribes.
One model's inbox, media, earnings and fans inside your workspace, for as many chatters as you want to put on it. Licence a model and they appear; let the licence lapse and their data stays, but their inbox stops syncing.
Your database, your media storage, your subdomain and certificate, every update we ship to our own install, and nightly backups with restore drills. There is no infrastructure line on top of the $100.
FAQ
If yours is not here, write to us before you pay for anything.
Through Fanvue, not through us. Each model's own Fanvue account subscribes to the sentryq app in the Fanvue App Store at $100 per month. Fanvue bills that account and pays us; no card details ever reach sentryq. If you manage five models, five subscriptions are started from those five accounts, and each can be cancelled independently.
Yes. Every agency gets its own Postgres database, its own media bucket, its own login system and its own subdomain. There is no shared table with a tenant column in it, so there is no query anyone could write that reads across agencies. The hub you sign up on stores only your account, your subdomain and which models are licensed.
Minutes, not days. Once at least one model has subscribed and you have connected your Fanvue agency account, provisioning runs fourteen steps and you watch them happen. You get a link to your own CRM at the end of it.
You connect the Fanvue account that manages your models, and grant read and write scopes for chat, media, posts, creators, insights and tracking links. That is what lets the CRM read conversations and send on your behalf. You can revoke it from Fanvue at any time; the CRM keeps working for everything already stored and stops syncing.
Any time, per model, from that model's Fanvue account. The licence runs to the end of the period already paid for. When the last licence lapses, the workspace is suspended rather than deleted, and your data is kept for 30 days so an accidental cancellation is recoverable.
Yes. Your workspace has an export that produces your conversations, fans, earnings and shift records as files you keep. It is yours; we do not hold it hostage to a subscription.
On dedicated servers in Germany, operated by Hetzner. Nothing is hosted outside the EU except the services listed on our subprocessors page, each of which is named there with what it does.
No. You pay per model, not per person. Add as many chatters, managers and QA reviewers to your workspace as you need; the price does not move.
Signing up costs nothing and asks for no card. You will see your own subdomain, your roster read straight from Fanvue, and exactly what each model would cost — before anybody subscribes to anything.
Replies monday to friday, 09:00-18:00 cet.
Already know you want it?
Subscriptions are started from each model's own Fanvue account, in the App Store. You can do that before or after creating your workspace — the hub picks the licence up either way.
Available on the Fanvue App Store