Service History Notes Assistant

Hrstalentsolutions; Dunedin; Remote; NZD 58,000 - 61,000; Full time

Job summary

HRSTALENTSOLUTIONS is seeking a Service History Notes Assistant to work remotely in a full-time office-administration role focused on keeping accurate, verifiable service records.

You will enter confirmed milestones from approved sources, flag discrepancies, and ensure notes are concise, factual, and compliant with privacy rules.

Experience in customer service, data entry, or written records helps, but full training is provided.

Qualifications

• Experience with customer service or office administration.
• Ability to compare sources and describe facts without embellishment.
• Comfortable with browser-based records and privacy rules.

Responsibilities

• Review assigned correspondence and forms in an online case system.
• Enter confirmed dates and service milestones in the correct record.
• Distinguish a request received from a request completed.
• Write concise factual notes using the employer's conventions.
• Flag conflicting dates, duplicate cases, or missing source material.
• Connect a new update to the existing case when appropriate.
• Follow access and privacy requirements for customer information.
• Provide a short exception list to the team reviewing uncertain cases.

Skills

Attention to detail

Data entry

Customer service

Job description

Service History Notes Assistant

Office Administration / Service History Notes / Remote / Full-time
58,240–61,360 per year

Make a service record tell the truth

A customer contacts a team weeks after an earlier request. The record should show when that request arrived, what standard steps were completed, and which issue remains open. The Service History Notes Assistant helps maintain that timeline. In this remote position, you enter confirmed milestones from approved sources into an online customer record and flag gaps or contradictions. You do not invent a resolution or alter a customer's account of what happened.

A case may contain an email, a completed form, and an internal note with different dates. Check what each item actually represents: submitted, reviewed, replied to, or closed. If the sources conflict, mark the discrepancy for a reviewer. A useful entry is short and factual, with enough context to find the source. Avoid copying entire sensitive messages into a general note field. When a status changes, make sure the change is supported by the documented event.

This is office administration that directly supports customer service. A colleague answering the next question should be able to use the record without misleading the customer. Your work may involve batches of closed cases, or active records awaiting one more confirmed update. If someone supplies a correction, preserve the original context according to the company's rules rather than quietly rewriting the history.

Typical assignments

• Review assigned correspondence and forms in an online case system.
• Enter confirmed dates and service milestones in the correct record.
• Distinguish a request received from a request completed.
• Write concise factual notes using the employer's conventions.
• Flag conflicting dates, duplicate cases, or missing source material.
• Connect a new update to the existing case when appropriate.
• Follow access and privacy requirements for customer information.
• Provide a short exception list to the team reviewing uncertain cases.

A private home office or comparable setting helps protect these records. The employer will train you on its status labels and note standards. Experience with customer service, office administration, data entry, or written records is an asset, but no prior case system is required. Beginners who can compare sources and describe a fact without embellishment are welcome. You should be comfortable with browser-based records and willing to ask when a timeline does not make sense.

This remote role is full-time, with its hours set for the actual opening. The employer will explain its software and coverage requirements.

A status field and a narrative note serve different purposes. Use the approved status for a confirmed stage, then write a note only if it adds context that the status cannot capture. When an email says a request was sent but there is no evidence it was received, do not turn that into a confirmed receipt. If the customer later disputes the sequence, the team should be able to trace each entry to a source. Accurate chronology is more useful than a tidy but unsupported story.

During a batch review, mark which records were checked and which still need a second look. If a customer name appears in two similar cases, compare case identifiers before adding a milestone. An accurate note on the wrong case can still mislead the team. You may be asked to correct a permitted entry after a reviewer identifies an error; make that correction according to the audit rules rather than concealing the change.

A service history should separate an action taken from a suggestion still awaiting approval. If an online message says a customer was offered a call, do not record that a call occurred unless the source confirms it. Connect a new note to the correct case and date, and avoid copying unrelated private details from another conversation. When two updates disagree, flag the conflict for the service owner. A later customer service colleague should be able to read the timeline and understand what actually happened.