Customer Support Specialist

Nummo is hiring a Customer Support Specialist. The opening is fake. There is no queue, no shift, and no manager waiting to see how fast you reply.

This is another sample posting, for a job that talks to customers instead of designing, building, measuring, or planning the product. You will be the person a user writes to when something failed, or when they cannot tell whether it failed. They will describe the screen they saw, often without the steps that got them there.

You will ask for those steps, try them, and answer with what happened and what to do next. The answer should be short enough to use while they are annoyed. A paragraph about how the system is supposed to work is not an answer.

Most tickets are one of a few problems wearing different words. A login that expired. A record that did not sync.

A permission that hides a button. A task that looks stuck because it is waiting on someone else. You will learn those patterns and write replies that name the pattern without making the person feel like a pattern.

You will also notice when a ticket is new. New problems get written up with the account, the time, and what you already tried, and they go to engineering before you invent a workaround and forget to tell anyone. You will not pretend to know.

If you have to check, you will say you are checking. If engineering has to look, you will say that, and you will give a time you will come back. “Soon” is not a time. If the thing cannot be fixed from support, you will say what the person can do in the meantime, including the option of doing it outside the product.

Leaving them with a broken step and a cheerful sign-off is worse than a plain no. Tone is part of the work. People write in a rush, or in anger, or as if you personally deleted their data.

You will answer the problem they have, not the temperature of the email. You will not match sarcasm. You will not hide behind a template when the template does not fit.

Templates are for the repeated cases, and even those get a sentence that shows you read this ticket. A reply that could have been sent without opening the account is a reply you should not send. You will keep notes that the next person can use.

What the user saw, what you found, what you told them, and whether it is resolved. “Customer is confused” is not a note. “The sync for this mailbox stopped on Tuesday, we restarted it, and the missing week did not come back” is a note. Those notes are also how the company learns which failures are common.

If you only close tickets, the same ticket returns with a new subject line. You will know the product well enough to do the task the user is trying to do. Clicking around in front of them and narrating your surprise is not support.

You should know where records live, what a user is allowed to see, and which actions cannot be undone. When you are unsure, you look it up in the product or ask someone who knows, and then you answer. You do not forward the user into a second conversation so you can stay comfortable.

Privacy still applies when someone is upset. You will verify they belong to the account before you describe what is in it. You will not send screenshots of one customer’s data to another.

You will not paste internal thread links, employee names, or guesses about other firms into a reply. The user gets their own facts.