Most people only ever see the public side of a dating and community platform.

Profiles appear. Photos get approved or declined. Support emails get answered. Problems get fixed. The site stays online.

But behind all of that are several very different roles, each with its own good points, frustrations and things they wish users understood a little better.

So, what do moderators, customer support staff and server administrators actually like about what they do — and what would they happily never deal with again?

Moderation

What do moderators like about the job?

One of the most satisfying parts of moderation is keeping the community safe and usable.

Removing fake profiles, dealing with scammers, stopping abusive behaviour and making sure public content remains appropriate all make a visible difference to the quality of the site.

There is also a certain satisfaction in spotting something that does not look quite right before it becomes a bigger problem.

Experienced moderators get very good at recognising suspicious behaviour, copied photos, spam, fake accounts and people trying to work around the rules.

What do moderators dislike?

There are some things moderators would be very happy never to see again.

Unwanted nudity is one of them.

Moderators have to review uploaded content, which means that when somebody uploads something obviously inappropriate, somebody still has to look at it before it can be declined.

Another common frustration is the same declined image being uploaded repeatedly.

If a photo has already been rejected because it breaks the rules, uploading exactly the same image again does not normally result in a different decision.

It simply means it has to be reviewed again.

The same goes for repeatedly trying to sneak contact details, prohibited content or other rule-breaking material into a profile after it has already been removed.

What makes moderation easier?

Reading the reason something was declined.

If an image or piece of profile content has been rejected, there is usually a reason for it.

Correcting the problem before submitting it again saves time for everybody.

And if you genuinely believe a moderation decision was wrong, contacting support and explaining why is far more useful than repeatedly resubmitting the same thing.

Customer Support

What do customer support staff like about the job?

The best part of customer support is solving a genuine problem.

Someone contacts support because they cannot log in, something is not working correctly or they are confused about a feature.

The problem gets identified, fixed or explained, and the user can carry on.

Simple.

Support staff also appreciate messages that explain the problem clearly from the beginning.

A good support request can sometimes be dealt with in one reply.

What do customer support staff dislike?

Very short messages that do not actually explain the problem.

For example:

"It doesn't work."

Or:

"Why can't I use my account?"

Or simply:

"Help."

Those messages usually create another round of emails because support then has to ask what the problem actually is.

  • What were you trying to do?
  • What happened?
  • What did you expect to happen?
  • Did you receive an error message?
  • What device are you using?
  • What browser are you using?
  • Can you provide a screenshot?

If that information is included in the first message, the problem can often be investigated much more quickly.

Why should you use the support form for a new issue?

Because each support case is tracked separately.

When you start a new support request through the proper form, the case is given its own reference number, usually shown in the email subject line.

That number helps keep the conversation attached to the correct issue.

Problems can arise when somebody replies to an old support email about a completely different matter. It can mix unrelated issues together and make it harder to understand what the current problem actually is.

If you are replying about the same issue, keep using the existing conversation.

If you are contacting support about something new, start a new request using the support form.

It keeps everything much clearer.

Do screenshots really help?

Yes. A lot.

A screenshot can immediately show an error message, layout problem, missing button or something else that might otherwise take several emails to explain.

Exact error messages are useful too.

Saying:

"I received an error."

is not nearly as useful as providing the actual wording of the error.

What else makes support difficult?

Rude or aggressive messages.

It is completely reasonable to be frustrated when something is not working.

But insulting the person answering the message does not make the problem easier to diagnose and it does not make a technical fix happen faster.

Clear information is useful.

Anger without information usually is not.

Another frustration is receiving several separate support requests about exactly the same issue.

Keeping everything in one conversation makes it much easier to follow what has already been tried and what still needs to be done.

Does support have to answer every question about how the business is run?

No.

Customer support is there to help with the service, accounts, technical problems, reports and other matters where assistance is appropriate.

That does not mean every internal business decision, operational process or administrative choice is open for discussion.

Occasionally, support receives questions that are less about solving a problem and more about demanding explanations for how the business is operated.

Users are of course free to ask questions, but support is not obliged to discuss internal procedures, staffing, commercial decisions, security arrangements, moderation methods or other internal matters simply because somebody wants that information.

There is an important difference between asking for help with your account and expecting access to the inner workings of the business.

Some information may also be deliberately kept private for security, abuse-prevention or operational reasons.

A user is entitled to receive the service they have been promised and to raise genuine concerns.

That does not mean they are entitled to an explanation of every internal decision or process behind it.

Server Administration

What do server administrators like about the job?

Strangely enough, one of the best things that can happen is nothing.

If the servers are running properly, pages are loading quickly, databases are behaving themselves and nobody is reporting problems, that is a good day.

A well-run system is supposed to be largely invisible.

There is also a lot of satisfaction in solving difficult technical problems.

Finding the cause of an unusual error, fixing a performance issue or tracking down something that has been misbehaving can feel surprisingly similar to detective work.

What do server administrators dislike?

Problems that appear without warning.

A server can be perfectly happy and then suddenly decide it no longer wants to cooperate.

Software updates can occasionally cause unexpected problems.

Third-party services can fail.

Traffic can suddenly increase.

Databases can become overloaded.

Something somewhere can break at the least convenient possible moment.

And when something does go wrong, users understandably notice immediately.

Is every technical problem caused by the server?

No.

"The server is down" is often used as a general explanation whenever something does not work, but there can be many other causes.

The problem might involve a browser, device, internet connection, mobile network, DNS provider, external service, cached data or something else entirely.

That is another reason why detailed reports are helpful.

Knowing exactly what happened, when it happened and what the user was doing at the time can make it much easier to identify the actual cause.

What Do All Three Roles Have in Common?

Although moderation, customer support and server administration are very different jobs, they have one important thing in common:

Good information makes everything easier.

  • If something is declined, read the reason.
  • If something is broken, explain exactly what happened.
  • If there is an error message, include it.
  • If something looks wrong, send a screenshot.
  • If you are reporting another member, provide enough information for the issue to be properly investigated.
  • If you are contacting support about a new issue, use the proper support form so it receives its own case reference.

And if you are frustrated, it is perfectly fine to say so — but being clear and constructive will usually get you much further than simply being angry.

A Few Things We Would Happily See Less Of

Moderators would happily see less inappropriate content being uploaded.

They would also appreciate not having to review the same rejected photo several times.

Customer support would happily see fewer messages consisting entirely of "it doesn't work."

They would also appreciate more screenshots, fewer abusive emails, fewer unrelated issues being added to old support cases and fewer demands for explanations about internal business matters that support is not required to discuss.

Server administrators would probably like fewer unexpected problems at inconvenient times, although that may be asking a little too much.

And What Do We Like Seeing More Of?

  • Clear reports.
  • Useful screenshots.
  • People reading the information they have already been given.
  • Users who explain problems properly.
  • People who use the correct support form for new issues.
  • People who report genuine safety concerns.

And, occasionally, a simple message saying:

"Thanks, that's fixed it."

Those are always nice.

The People Behind the Platform

Dating and community sites can sometimes feel completely automated, but there is a lot happening behind the scenes.

Content needs reviewing.

Questions need answering.

Reports need investigating.

Servers need maintaining.

Problems need fixing.

Most users will never need to think about any of that, and ideally they should not have to.

But when you do need help, providing useful information, keeping separate issues in separate support cases and remembering that somebody has to read, review or investigate what you send can make the whole process much quicker and easier.

For everyone involved.