Get a reply from this employer — a resume and cover letter tailored to exactly what they’re hiring for.
Hrstalentsolutions is seeking a Service Request Intake Assistant for remote, full-time work. The role centers on reading customer messages, capturing accurate details, and routing requests to the appropriate teams.
The intake process emphasizes recording customer concerns without promising resolutions, while maintaining privacy and accuracy across systems. If details are missing, you will ask focused questions to complete records.
Customer Service / Request Intake / Remote
Full-time
Compensation: 62,400–65,520 per year
A customer asks for help with a service, but the team needs a clear record before it can act. The Service Request Intake Assistant reads the initial message or online form, identifies the type of request, and records the details supplied. This is the beginning of a service process, not a position that promises a resolution or decides whether a request will be approved.
For example, a message may say that an earlier request has changed. Review the existing record before opening another case. If the change belongs to that case, add the new information where the team can see it. If the message raises a different issue, keep it distinct. This small judgment keeps the queue understandable and avoids making customers repeat their history.
A reviewer should be able to tell what the customer asked, which details were available, what you requested, and what remains pending. You would not fill gaps with an assumption or rewrite a complaint to make it sound simpler. This work requires careful handling of private information using the employer’s approved tools and instructions.
An intake message can describe two different needs. If one part is a straightforward request and another asks for an exception, capture both without treating the exception as approved. The receiving team should be able to see the customer’s own words and the routine details you checked. If a person adds information later, update the existing case when appropriate and make the addition visible. This is how a clean intake record prevents a second conversation from starting with no context.
A request may contain a practical question and a separate complaint. Record both parts so the next team does not treat a simple acknowledgement as resolution of the whole matter. If a customer supplies screenshot or document, check that it is attached to the correct case and that the receiving team can open it. An incomplete request can still be acknowledged while a missing detail is sought. You will not promise approval, repair or reimbursement at intake; your record should explain the requested outcome and the next authorised step.
You should be comfortable reading messages closely, entering information into online forms, and writing short replies. Customer service experience is valuable because you may need to acknowledge a concern without predicting the answer. Office administration experience is valuable because the record needs to be accurate and easy to track. Neither background is required. Newcomers can learn the team’s request categories and workflow after joining.
You will not decide whether a service is covered, authorize an exception, or offer a deadline that has not been confirmed. Questions outside routine intake should go to the appropriate colleague. The ability to recognize that boundary matters more than having used a particular software system.