Customer empathy that scales
The soft skill that closes tickets and keeps customers. Calm under pressure, patient in long threads, sharp at translating a technical fix into the words a Monday-morning user can actually act on.
I'm Rafiz Sejim, a product & support specialist with seven years across Gravity Forms, Dokan, Directorist, FormGent, HappyAddons, WP Legal Pages and the plugins your team depends on. I read code, reproduce the weird bugs, and translate the fix into something the customer actually feels.
Most days I sit between customers, developers, UX, and product. A ticket lands. I read it twice, reproduce it on a clean install, read the PHP, follow the hooks and filters, find the conflict, then I write the answer the way I'd want to read on a Monday morning.
At SovWare I helped turn a recurring Directorist support pattern into a dashboard that became one of our top premium extensions. I've shipped three plugins of my own on .org (NarrativeForms, SimpleBoards, GF Directory) using PHP, GFAddOn, REST routes, custom tables and Gutenberg blocks, and supported Dokan, HappyAddons, FormGent and WP Legal Pages through thousands of tickets.
Right now I'm looking for a team where support is treated as product work, where repeated questions become better docs, better UX, and quieter inboxes. If that sounds like you, the kettle's on.
A specialist in the seam between a customer who is stuck and the product that should already be working for them. Calm, technical, product-minded.
The soft skill that closes tickets and keeps customers. Calm under pressure, patient in long threads, sharp at translating a technical fix into the words a Monday-morning user can actually act on.
Repeated tickets are a roadmap. At SovWare I helped lead a Directorist dashboard and notification flow that became one of our most successful premium extensions, lifted engagement, and quieted the inbox.
Reproduce on a clean install. Isolate the offender. Write the bug report a developer can actually act on, with steps, environment, screenshots, and customer context.
Rewriting documentation around the question the customer is actually typing, not the feature name. Onboarding flows tuned by what support sees every week.
Honest fit explanations. Improved conversion at SovWare and weDevs by helping prospects see whether a product was the right answer for their use case, instead of pushing the close.
I use Claude and Cursor to draft replies, write documentation, group recurring feedback, and read code faster, always with human review. Empathy and responsibility don't outsource. Technical depth gets faster; customer trust still has to be earned one ticket at a time.
Approved Gravity Forms entries become a frontend directory: cards, filters, search, saved listings, a logged-in dashboard, single-entry pages, a Gutenberg block, shortcode rendering and REST routes. All without touching core.
Per-form settings let admins map fields to title, image, price, rating, badge, meta, CTA, features. Shortcode and block share one render path. Caching is versioned. Output is escaped and nonced. Theme overrides live in /gf-directory/.
Hover any row for a glance. Each one taught me how form-driven WordPress products break, scale, and quietly delight.
SovWare · Directorist, HelpGent, FormGent, HappyAddons, WP Legal Pages
SovWare · multi-product WordPress support
weDevs · Dokan, WP User Frontend, WooCommerce
Minnesota State University, USA
In the age of AI, technical knowledge is easier to access. Empathy, customer trust, and good judgment still matter, and that is where I bring value.
Rafiz · on support workShort essays on Gravity Forms, plugin support, customer empathy, and the strange place where support meets product.
A practical guide to the WordPress request lifecycle and the hooks that fire along the way. This is the lesson that retires the most…
Read noteA practical guide to actions and filters for anyone moving from “I install plugins” to “I extend and fix plugins.” This guide is useful…
Read note