Veterinary Receptionist
DNA Vetcare Ltd · Kent, WA · 1 mo ago
HealthcareFull-time
We need to output HTML fragment with sections only where there is real content. Use for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to extract content from posting.
Let's parse the posting:
- "About The Role" heading: description about role: "A fantastic opportunity has arisen for a Veterinary Receptionist to join our fantastic team at Pinebank Vets. This is a fantastic opportunity to join our team in Maidstone. We are a lovely little practice, growing day by day with all your usual basic equipment. We have a great vet, nurse, and support team and the caseload is really growing. We are known for treating every one of our exceptional support team with the value, respect and praise they deserve."
Then "Your Day At Pinebank Vets Could Include" list of duties: bullet points.
Then "Ideally You Will Have" list of requirements/qualifications/skills.
Then "This is a full time position, working 30-35 hours per week with a share of 1:3 Saturday mornings." That's schedule info.
Then "This role will be a dual role between supporting the vet and nurse teams with patient care, and then time on Reception. You will be required to maintain a clean and hygienic environment at all times, assist with animal handling, answer the phone, book appointments, taking payments and deal with client queries alongside other duties You must have a professional and kind phone manner and be capable at working both on your own and within a team."
Then "Interested? Apply now!" (application instruction, to be removed).
Then "About You" heading? Actually after that there is "About You About Us DNA Vetcare is a proudly independent group..." This seems like "About Us" content. The posting includes "About You About Us DNA Vetcare..." Might be two sections: "About You" and "About Us". But we only have headings list: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We should not create headings not in list. So we should not output "About You" or "About Us". However we need to preserve substantive information. Where to put that info? It might be considered "About the role" or maybe "About Us" is not a standard heading; we could incorporate into "About the role" or maybe ignore? The instruction: "Use
for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to extract content from posting.
Let's parse the posting:
- "About The Role" heading: description about role: "A fantastic opportunity has arisen for a Veterinary Receptionist to join our fantastic team at Pinebank Vets. This is a fantastic opportunity to join our team in Maidstone. We are a lovely little practice, growing day by day with all your usual basic equipment. We have a great vet, nurse, and support team and the caseload is really growing. We are known for treating every one of our exceptional support team with the value, respect and praise they deserve."
Then "Your Day At Pinebank Vets Could Include" list of duties: bullet points.
Then "Ideally You Will Have" list of requirements/qualifications/skills.
Then "This is a full time position, working 30-35 hours per week with a share of 1:3 Saturday mornings." That's schedule info.
Then "This role will be a dual role between supporting the vet and nurse teams with patient care, and then time on Reception. You will be required to maintain a clean and hygienic environment at all times, assist with animal handling, answer the phone, book appointments, taking payments and deal with client queries alongside other duties You must have a professional and kind phone manner and be capable at working both on your own and within a team."
Then "Interested? Apply now!" (application instruction, to be removed).
Then "About You" heading? Actually after that there is "About You About Us DNA Vetcare is a proudly independent group..." This seems like "About Us" content. The posting includes "About You About Us DNA Vetcare..." Might be two sections: "About You" and "About Us". But we only have headings list: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We should not create headings not in list. So we should not output "About You" or "About Us". However we need to preserve substantive information. Where to put that info? It might be considered "About the role" or maybe "About Us" is not a standard heading; we could incorporate into "About the role" or maybe ignore? The instruction: "Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It says e.g., meaning those are examples, but we should only use those headings? It says "Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." Likely they expect us to use those headings when appropriate. So we can use those headings for sections we have content for. If we have content about the company, maybe we could put under "About the role"? But that seems odd. However we could also omit that content if it doesn't fit any heading? But we must preserve ALL substantive information; do NOT invent or summarize away detail. So we need to include that info somewhere. Perhaps we can treat "About You About Us" as part of "About the role" or maybe as a separate section not in the list but we could still use for it? The instruction says use for section headings (e.g. About the role, Responsibilities...). It doesn't forbid other headings, but suggests using those. Safer to stick to those headings; we can put company info under "About the role" as part of role description. That would preserve it.
Thus sections:
- About the role: include the introductory paragraph plus maybe the "About You About Us" content.
- Responsibilities: list of duties from "Your Day At Pinebank Vets Could Include" plus maybe other duties mentioned later (maintain clean environment, assist with animal handling, answer phone, book appointments, taking payments, deal with client queries). Those are already covered.
- Requirements / Qualifications / Skills: we have "Ideally You Will Have" list: previous experience as Veterinary Receptionist, exceptional communication and interpersonal skills, strong organisational abilities, multitask, genuine love for animals, commitment to outstanding client service, proficient in computer systems, experience using RxWorks is a massive plus, must enjoy cuddling pet (pets are everything). Also later: must have professional and kind phone manner, capable of working alone and within a team. Those could be skills/requirements.
We need to decide which headings to use: Responsibilities, Requirements, Qualifications, Skills. We could combine into one section "Requirements" or separate. The instruction: prefer a few substantive sections over many thin ones. So we could combine Requirements, Qualifications, Skills into one section maybe "Requirements". But we have separate headings allowed; we could use "Requirements" for experience and skills, "Qualifications" maybe not needed. Better to use "Requirements" for the list of desired attributes, and "Skills" maybe for technical skills like RxWorks. But to avoid thin sections, we can combine into "Requirements". Let's see.
We also have schedule: "This is a full time position, working 30-35 hours per week with a share of 1:3 Saturday mornings." That's schedule info. So we can create a Schedule section.
Pay and Benefits: not mentioned. So we omit those sections.
Thus final HTML:
About the role
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." Likely they expect us to use those headings when appropriate. So we can use those headings for sections we have content for. If we have content about the company, maybe we could put under "About the role"? But that seems odd. However we could also omit that content if it doesn't fit any heading? But we must preserve ALL substantive information; do NOT invent or summarize away detail. So we need to include that info somewhere. Perhaps we can treat "About You About Us" as part of "About the role" or maybe as a separate section not in the list but we could still use for it? The instruction says use for section headings (e.g. About the role, Responsibilities...). It doesn't forbid other headings, but suggests using those. Safer to stick to those headings; we can put company info under "About the role" as part of role description. That would preserve it.
Thus sections:
- About the role: include the introductory paragraph plus maybe the "About You About Us" content.
- Responsibilities: list of duties from "Your Day At Pinebank Vets Could Include" plus maybe other duties mentioned later (maintain clean environment, assist with animal handling, answer phone, book appointments, taking payments, deal with client queries). Those are already covered.
- Requirements / Qualifications / Skills: we have "Ideally You Will Have" list: previous experience as Veterinary Receptionist, exceptional communication and interpersonal skills, strong organisational abilities, multitask, genuine love for animals, commitment to outstanding client service, proficient in computer systems, experience using RxWorks is a massive plus, must enjoy cuddling pet (pets are everything). Also later: must have professional and kind phone manner, capable of working alone and within a team. Those could be skills/requirements.
We need to decide which headings to use: Responsibilities, Requirements, Qualifications, Skills. We could combine into one section "Requirements" or separate. The instruction: prefer a few substantive sections over many thin ones. So we could combine Requirements, Qualifications, Skills into one section maybe "Requirements". But we have separate headings allowed; we could use "Requirements" for experience and skills, "Qualifications" maybe not needed. Better to use "Requirements" for the list of desired attributes, and "Skills" maybe for technical skills like RxWorks. But to avoid thin sections, we can combine into "Requirements". Let's see.
We also have schedule: "This is a full time position, working 30-35 hours per week with a share of 1:3 Saturday mornings." That's schedule info. So we can create a Schedule section.
Pay and Benefits: not mentioned. So we omit those sections.
Thus final HTML:
About the role
for section headings (e.g. About the role, Responsibilities...). It doesn't forbid other headings, but suggests using those. Safer to stick to those headings; we can put company info under "About the role" as part of role description. That would preserve it.
Thus sections:
- About the role: include the introductory paragraph plus maybe the "About You About Us" content.
- Responsibilities: list of duties from "Your Day At Pinebank Vets Could Include" plus maybe other duties mentioned later (maintain clean environment, assist with animal handling, answer phone, book appointments, taking payments, deal with client queries). Those are already covered.
- Requirements / Qualifications / Skills: we have "Ideally You Will Have" list: previous experience as Veterinary Receptionist, exceptional communication and interpersonal skills, strong organisational abilities, multitask, genuine love for animals, commitment to outstanding client service, proficient in computer systems, experience using RxWorks is a massive plus, must enjoy cuddling pet (pets are everything). Also later: must have professional and kind phone manner, capable of working alone and within a team. Those could be skills/requirements.
We need to decide which headings to use: Responsibilities, Requirements, Qualifications, Skills. We could combine into one section "Requirements" or separate. The instruction: prefer a few substantive sections over many thin ones. So we could combine Requirements, Qualifications, Skills into one section maybe "Requirements". But we have separate headings allowed; we could use "Requirements" for experience and skills, "Qualifications" maybe not needed. Better to use "Requirements" for the list of desired attributes, and "Skills" maybe for technical skills like RxWorks. But to avoid thin sections, we can combine into "Requirements". Let's see.
We also have schedule: "This is a full time position, working 30-35 hours per week with a share of 1:3 Saturday mornings." That's schedule info. So we can create a Schedule section.
Pay and Benefits: not mentioned. So we omit those sections.
Thus final HTML:
About the role
... (intro + about you/about us)
Responsibilities
- Welcoming clients and their pets upon arrival
- Book appointments and arrivals
- Help to promote our Healthcare Plan so that pets are receiving premium discounted preventative treatment
- Booking in follow up appointments for the pet once they have left their initial consultation
- Help the Vet and Nurse team with queries
- Being responsible for paperwork being scanned onto pets digital records
- Liaison with clients regarding queries for appointment booking and medication collection
- Ordering food and medication
- Taking payment following treatment
- Managing an extremely busy reception desk with efficiency and professionalism
- Maintain a clean and hygienic environment at all times
- Assist with animal handling
- Answer the phone
- Book appointments
- Take payments
- Deal with client queries
heading and then content. For About the role: we need a
containing the prose. We'll combine multiple sentences into maybe multiple
? The instruction: use
for prose. Could be multiple
paragraphs. We'll create maybe two paragraphs: first intro, second about company/dual role. Let's craft: Paragraph 1: "A fantastic opportunity has arisen for a Veterinary Receptionist to join our fantastic team at Pinebank Vets. This is a fantastic opportunity to join our team in Maidstone. We are a lovely little practice, growing day by day with all your usual basic equipment. We have a great vet, nurse, and support team and the caseload is really growing. We are known for treating every one of our exceptional support team with the value, respect and praise they deserve." Paragraph 2: "Your day at Pinebank Vets could include a dual role between supporting the vet and nurse teams with patient care and time