Technical Support Specialist (Part-Time)

Heads up first: GPTease builds software for adult content creators. Our customers sell on OnlyFans, Fansly, LoyalFans, and Fanvue. You will be reading and answering their support tickets daily. If that is not for you, no hard feelings. If you have already worked in or around this industry, lead with that.

About GPTease

An AI inbox, CRM, and writing assistant for adult content creators. The product drafts, the creator approves, nothing sends by itself. Profitable, bootstrapped, small team.

The Role

You own the support inbox. Every email ticket that comes in is yours: answer it, or prove it is a bug and hand engineering a case they can act on without asking you anything.

This is not a macro-and-escalate job. Most support roles stop at "I'll pass this to the team." You don't. You reproduce the issue in the product yourself, open DevTools, capture what is failing, and use Claude to work out what it means before anyone else hears about it.

Our founder ran support himself for years before handing it off. The bar is his: most tickets die at first reply, and nothing reaches engineering without repro steps.

What you will do

• Work the inbox in two passes a day, roughly 12 hours apart, so every ticket gets a same-day reply. Timed for US customer hours

• Draft with Claude, review, send. Same rule as our product: AI drafts, human approves, nothing sends by itself

• Reproduce reported issues in the product yourself before calling anything a bug

• Investigate in DevTools: console errors, the network tab, failed requests. Export a HAR, hand it to Claude, and read what comes back critically

• File verified bugs to engineering via Jira: repro steps, expected versus actual, console and network evidence. Not vibes

• Write replies in simple, plain English. Our customers are creators, not engineers. No jargon back at them

• Keep a running log of ticket patterns. Three tickets about the same confusion is a product problem, and you say so

At 3 months: every ticket at same-day replies, engineering trusts your bug reports enough to skip re-verification, and a ticket-pattern log that product actually reads.

Must-haves

• 1 to 3 years in QA, technical support, or support engineering for a software product. A CS degree is fine as background; the test is what you do with a broken page, not the credential

• Comfortable in Chrome DevTools: the console, the network tab, and what a 4xx versus 5xx response tells you

• Already use Claude or an equivalent AI assistant in real daily work. You will investigate with it, and you need to know when it is wrong

• Written English that is simple, precise, and calm. You will be explaining technical problems to non-technical customers

• Can hold the schedule: two short inbox passes a day, seven days a week

• Professional comfort working in and around the adult industry

Bonus (any one moves you up the pile)

• You have written production code, even briefly. You will read Claude's analysis with better judgment

• Chatter, VA, or OFM agency experience. You already know the customer

• Have debugged subscription or billing issues (failed payments, plan states, renewals)

• Have filed bugs an engineering team actually thanked you for

What We Offer

• Flat $200–$250/month, contract, remote

• About 2 hours a day, split into two passes. You propose the exact windows; we agree on them together

• Small team: your bug reports go straight to the engineers who fix them, and your ticket patterns go straight to the founder

• Claude provided for the workflow