Website Administration Request Coordinator

HRS Talent Solutions; Columbus (OH); Remote; USD 59,000 - 64,000; Full time

Job summary

HRS Talent Solutions is seeking a Website Administration Request Coordinator for a full-time remote role. You will convert incoming website change requests into clear, actionable tickets by identifying the exact URL, section, and proposed update, and ensuring proper approvals and sources are provided.

You will route requests to the appropriate teams, maintain records with the requester’s language, and track status from intake to publication, ensuring privacy and accuracy throughout the process.

Qualifications

• Experience handling customer service or user requests.
• Ability to ask precise clarifying questions when requests are vague.
• Skill in identifying exact URLs, sections and updates.
• Comfort routing requests to the correct teams with minimal guidance.

Responsibilities

• Read assigned online requests for page changes.
• Identify the exact URL, section, and proposed update.
• Check whether approval or a source is supplied.
• Ask a specific question for missing information.
• Route content and technical requests to the right team.
• Keep screenshots and private details in approved systems.
• Record ownership and status until the handoff is accepted.

Skills

Customer service

Attention to detail

Clear communication

Questioning skills

Job description

Website Administration Request Coordinator

A usable website ticket

This remote office administration role starts with an internal request to change a website page. You gather the exact online address, the requested correction, any approved source and the person authorized to decide. The finished work is a ticket the website team can act on, not a page edit made without approval. Customer service experience can help you ask a precise question when a request is vague, although it is not required.

Full-time | Remote

Imagine a colleague writes that the contact page is wrong. The website team still needs to know which section is affected and what verified text should replace it. Ask for the specific page and source; distinguish a broken form from a wording correction before routing. If the change concerns a public promise about availability, the content owner must approve the statement. Keep the requester's language in the record and add a concise summary of what remains missing. A completed intake does not mean the change has already gone live.

Make the request actionable

“Update the contact page” is too vague to assign. Ask which page and section are involved and what approved replacement information should appear. If the requested wording has not been authorized, mark the ticket as awaiting approval. A screenshot can help locate a problem, but check that it does not expose private customer data before adding it to a general tracker. If an urgent broken link prevents people from reaching support, use the employer's priority route.

The job may include distinguishing a content edit from a technical issue. A typo belongs with an editor; a form that does not submit may need the development team. Follow the routing guide and preserve the requester's original description. If a ticket is returned for missing details, connect the reply to the same item rather than opening another one. A clear status lets the requester see whether the work is accepted, pending information, or completed by the website owner.

Responsibilities

• Read assigned online requests for page changes.
• Identify the exact URL, section, and proposed update.
• Check whether approval or a source is supplied.
• Ask a specific question for missing information.
• Route content and technical requests to the right team.
• Keep screenshots and private details in approved systems.
• Record ownership and status until the handoff is accepted.

Describe the requested website change

An internal colleague might report a wrong link, an outdated office-hours statement, or a typo on a public page. Ask for the page address, the current text or behavior, and the approved replacement or source. A screenshot can help when the location is hard to describe, but it may contain private details; follow the employer's handling rules. Do not publish a correction because a request sounds urgent.

Some changes need content-owner approval and others belong to a technical team. Use the intake guide to select the correct route. A broken link and a proposed new feature are not the same kind of ticket. Keep the requester's original wording available to the owner, then add a concise summary of what needs checking. Update the requester when the team confirms a stage, rather than promising a release time.

An intake record should show

• The live page or online path involved.
• The exact section or element described.
• The observed issue and the requested result.
• Any approved source supplied by the requester.
• The owner assigned to review the change.
• A status that distinguishes review from publication.

The employer will teach its website workflow and its approval chain. You do not need design or coding experience. The role rewards clear questions and careful tracking so the web team can act without repeatedly asking for basic context.

Pay: $59,300 - $64,100 per year

A home office with a reliable screen makes it easier to check a live page beside the incoming request.

If this work interests you

Browser navigation and clear notes matter more than a technical title on your resume. The employer can teach the intake tool, approval chain and difference between content and technical tickets. Applicants with little experience are welcome if they are willing to clarify ambiguous instructions. Highlight any work where you turned an incomplete request into a usable handoff.