Support that answers
Here’s how support works at RFF right now: you email, and the person who built the product answers. Usually within hours, often faster.
- In the app: click the ? in the top-right and send a message. It lands in my inbox with your reply-to set, so the answer comes straight back to your email.
- By email: brian@getrff.com - yes, the founder’s actual inbox.
No ticket number. No tier-1 script asking if you’ve rebooted. No chatbot standing between you and someone who can actually fix it.
Why this is a feature, not a gap
RFF is built by someone who ran Windows endpoint management for a hospital fleet - tens of thousands of devices on SCCM, Tanium, Intune, and PDQ. When you describe a problem, the person reading it has probably lived it, can reproduce it, and can often ship the fix the same week. Ask anyone who’s filed a ticket with a big RMM vendor what their median time-to-real-answer looks like.
That’s the trade at this size: you don’t get a 24/7 call center. You get the engineer.
What to include (so the first answer is the fix)
- What you were doing, and what happened instead
- The device hostname and rough time it happened
- A screenshot if it’s visual - the job log text if it’s a deploy
Security issues
Found something security-relevant? Email brian@getrff.com with “SECURITY” in the subject and it goes to the top of the pile. Details on how RFF handles your data are on the security page.
Before you write
The guide covers first deploy, policies, and remote desktop. The changelog shows what shipped recently. And the live demo is the fastest way to check “does RFF do X?” yourself - no signup.