Administrator - Customer Care
for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Use - for any list of duties/requirements/benefits, and
for prose. Do NOT repeat the job title as a heading. Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. Prefer a few substantive sections over many thin ones.
We need to parse the job description.
Content:
- Job Description paragraph: "As a Administrator – Customer Care, you will be responsible for completing administrative daily tasks for assigned locations in accordance with established levels of service, productivity, and quality, while servicing our customer at the most economical cost."
- Responsibilities: bullet list (but not bullet in source). It's a series of sentences separated by periods. We need to turn into
- list.
Responsibilities items:
1. Performs daily required administrative functions in accordance to written process maps.
2. Interacts with and supports Sales and Sales Management including updating and generating reports, reconciling daily transactions, and assisting in providing customer service.
3. Responds and acts on submittals within Sales Portal in specified time periods of request.
4. Performs timely and accurate completion of branch audit and compliance steps per established guidelines.
5. Maintains high level of organization of tasks between assigned branches.
6. Documents and submits individual task KPI data used for process improvement.
7. Assists Customer Care Manager in development and training of employees.
8. Researches tax and freight claims and runs credit memo when appropriate.
9. Works with Financial Services to clear claims.
10. Adds new customers into WESNET and PACT and runs WESNET user branch security reports.
11. Notifies branch administrative manager if any discrepancies.
12. Performs basic accounting duties such as light accounts receivables and payables and invoice approval preparation.
13. Completes various branch reports such as tax reports and Wesnet security reports.
- Qualifications: list:
"High School Degree or Equivalent required; Associate’s degree preferred
Administrative experience
Ability to multi-task
Strong verbal and written communication skills
Strong computer skills, including in Microsoft Office
Ability to work in a team environment
Attention to detail"
We need to decide sections: Could have "Responsibilities" and "Qualifications". Also "Compensation Details" includes pay range: $19.13 - $26.79 Per Hour. Also mentions bonus, benefits. So we can have a "Pay" section with that range. Also "Benefits" section: mentions benefits program includes paid time off, medical, dental, vision, retirement savings plans. Also mentions bonus or sales incentive plan, commission structure for certain sales roles (but this role is Administrator – Customer Care, not sales; still mention but maybe not relevant). We should include benefits if stated. The posting says: "In addition, Wesco offers a benefits program for eligible employees, which may include paid time off, medical, dental, and vision coverage, and retirement savings plans." So we can include Benefits section.
Also "About The Team" is descriptive about company; could be "About the role"? Actually "About The Team" is more about company. The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We have "About The Team" content; we could map to "About the role" or maybe "About the team". But they said use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should use those exact headings if we have content. We have content for About the team (company description). Could treat as "About the role"? Might be okay. But we need to ensure we don't create sections with filler. The About The Team paragraph is substantive.
We also have "Compensation Details" which includes pay and mention of bonus etc. We'll create Pay section with the hourly range. Also maybe Benefits section.
We also have "Schedule"? Not mentioned. So we should not create Schedule section.
We also have "Skills"? Could be derived from qualifications but we have Qualifications section already. Could also have Skills separate but we can combine. The instruction says prefer a few substantive sections over many thin ones. So we can have sections: About the role (or About the team), Responsibilities, Qualifications, Pay, Benefits. Possibly also Skills? But Qualifications already covers skills. We'll keep Qualifications.
We need to avoid repeating job title as heading. So no Administrator – Customer Care
. Good.
We need to not put Job ID etc. There's none.
We need to remove boilerplate: EEO, equal-opportunity, scam-warning, etc. At end there is EEO statement, Los Angeles County etc. We must drop those.
Also remove "Learn more about Working at Wesco here and apply online today!" etc. That's application instructions; drop.
Also remove "Additional details about benefits are available here ." maybe keep as part of benefits? It's a link; we can drop the link but keep the sentence? The instruction: remove application instructions. That sentence is about benefits details link; maybe we can keep the benefits description but drop the link phrase. Safer to drop the whole sentence "Additional details about benefits are available here ." as it's a link. But we already have benefits description; we can keep the description before that.
Also remove "Founded in 1922 and headquartered in Pittsburgh, Wesco is a publicly traded (NYSE: WCC) FORTUNE 500® company." That's part of About The Team; we can keep as it's substantive about company.
Also remove "Wesco International, Inc., including its subsidiaries and affiliates (“Wesco”) provides equal employment opportunities to all employees and applicants for employment..." That's EEO boilerplate; drop.
Also drop "US applicants only, we are an Equal Opportunity Employer." etc.
Also drop "Los Angeles Unincorporated County Candidates Only: ..." etc.
Also drop "This posting is for a current, active vacancy intended for immediate hire." That's maybe minor metadata; we could fold into a short p or drop. Probably drop.
Now construct HTML.
We'll have:
About the role
As a Administrator – Customer Care, you will be responsible for completing administrative daily tasks for assigned locations in accordance with established levels of service, productivity, and quality, while servicing our customer at the most economical cost.
At Wesco, we build, connect, power and protect the world. As a leading provider of business-to-business distribution, logistics services and supply chain solutions, we create a world that you can depend on. Our Company’s greatest asset is our people. Wesco is committed to fostering a workplace where every individual is respected, valued, and empowered to succeed. We promote a culture that is grounded in teamwork and respect. With a workforce of over 20,000 people worldwide, we embrace the unique perspectives each person brings. Through comprehensive benefits and active community engagement, we create an environment where every team member has the opportunity to thrive. Founded in 1922 and headquartered in Pittsburgh, Wesco is a publicly traded (NYSE: WCC) FORTUNE 500® company.
But note: The "About The Team" includes the first sentence about As a Administrator... Actually that's from Job Description paragraph. We already used that as role description. The About The Team paragraph starts with "At Wesco, we build..." So we should separate.
Thus:
About the role
As a Administrator – Customer Care, you will be responsible for completing administrative daily tasks for assigned locations in accordance with established levels of service, productivity, and quality, while servicing our customer at the most economical cost.
About the team
maybe but they said use headings like About the role, Responsibilities... Not About the team. But we could still use About the role for the first paragraph, and maybe we don't need a separate About the team; we could incorporate company description into About the role? But that would mix. Better to have About the role (the role description) and maybe a separate section "About the company" but not in list. Since they only gave examples, not strict list; they said use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can use those exact headings if appropriate. We have content for About the role (the first paragraph). For company description, we could put under About the role as well, but that may be okay. However, we might also create a section "About the team" but that's not in the examples; risk of being considered not allowed? The instruction: "Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." The "e.g." suggests those are examples, not exclusive list. So we can use other headings if needed, but better to stick to those. We could put company description under About the role as well, making that section longer. That seems fine.
Thus:
About the role
As a Administrator – Customer Care, you will be responsible for completing administrative daily tasks for assigned locations in accordance with established levels of service, productivity, and quality, while servicing our customer at the most economical cost.
At Wesco, we build, connect, power and protect the world. As a leading provider of business-to-business distribution, logistics services and supply chain solutions, we create a world that you can depend on. Our Company’s greatest asset is our people. Wesco is committed to fostering a workplace where every individual is respected, valued, and empowered to succeed. We promote a culture that is grounded in teamwork and respect. With a workforce of over 20,000 people worldwide, we embrace the unique perspectives each person brings. Through comprehensive benefits and active community engagement, we create an environment where every team member has the opportunity to thrive. Founded in 1922 and headquartered in Pittsburgh, Wesco is a publicly traded (NYSE: WCC) FORTUNE 500® company.
Now Responsibilities:
Responsibilities
- Performs daily required administrative functions in accordance to written process maps.
- Interacts with and supports Sales and Sales Management including updating and generating reports, reconciling daily transactions, and assisting in providing customer service.
- Responds and acts on submittals within Sales Portal in specified time periods of request.
- Performs timely and accurate completion of branch audit and compliance steps per established guidelines.
- Maintains high level of organization of tasks between assigned branches.
- Documents and submits individual task KPI data used for process improvement.
- Assists Customer Care Manager in development and training of employees.
- Researches tax and freight claims and runs credit memo when appropriate.
- Works with Financial Services to clear claims.
- Adds new customers into WESNET and PACT and runs WESNET user branch security reports.
- Notifies branch administrative manager if any discrepancies.
- Performs basic accounting duties such as light accounts receivables and payables
for prose. Do NOT repeat the job title as a heading. Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. Prefer a few substantive sections over many thin ones. We need to parse the job description. Content: - Job Description paragraph: "As a Administrator – Customer Care, you will be responsible for completing administrative daily tasks for assigned locations in accordance with established levels of service, productivity, and quality, while servicing our customer at the most economical cost." - Responsibilities: bullet list (but not bullet in source). It's a series of sentences separated by periods. We need to turn into
- list.
Responsibilities items:
1. Performs daily required administrative functions in accordance to written process maps.
2. Interacts with and supports Sales and Sales Management including updating and generating reports, reconciling daily transactions, and assisting in providing customer service.
3. Responds and acts on submittals within Sales Portal in specified time periods of request.
4. Performs timely and accurate completion of branch audit and compliance steps per established guidelines.
5. Maintains high level of organization of tasks between assigned branches.
6. Documents and submits individual task KPI data used for process improvement.
7. Assists Customer Care Manager in development and training of employees.
8. Researches tax and freight claims and runs credit memo when appropriate.
9. Works with Financial Services to clear claims.
10. Adds new customers into WESNET and PACT and runs WESNET user branch security reports.
11. Notifies branch administrative manager if any discrepancies.
12. Performs basic accounting duties such as light accounts receivables and payables and invoice approval preparation.
13. Completes various branch reports such as tax reports and Wesnet security reports.
- Qualifications: list:
"High School Degree or Equivalent required; Associate’s degree preferred
Administrative experience
Ability to multi-task
Strong verbal and written communication skills
Strong computer skills, including in Microsoft Office
Ability to work in a team environment
Attention to detail"
We need to decide sections: Could have "Responsibilities" and "Qualifications". Also "Compensation Details" includes pay range: $19.13 - $26.79 Per Hour. Also mentions bonus, benefits. So we can have a "Pay" section with that range. Also "Benefits" section: mentions benefits program includes paid time off, medical, dental, vision, retirement savings plans. Also mentions bonus or sales incentive plan, commission structure for certain sales roles (but this role is Administrator – Customer Care, not sales; still mention but maybe not relevant). We should include benefits if stated. The posting says: "In addition, Wesco offers a benefits program for eligible employees, which may include paid time off, medical, dental, and vision coverage, and retirement savings plans." So we can include Benefits section.
Also "About The Team" is descriptive about company; could be "About the role"? Actually "About The Team" is more about company. The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We have "About The Team" content; we could map to "About the role" or maybe "About the team". But they said use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should use those exact headings if we have content. We have content for About the team (company description). Could treat as "About the role"? Might be okay. But we need to ensure we don't create sections with filler. The About The Team paragraph is substantive. We also have "Compensation Details" which includes pay and mention of bonus etc. We'll create Pay section with the hourly range. Also maybe Benefits section. We also have "Schedule"? Not mentioned. So we should not create Schedule section. We also have "Skills"? Could be derived from qualifications but we have Qualifications section already. Could also have Skills separate but we can combine. The instruction says prefer a few substantive sections over many thin ones. So we can have sections: About the role (or About the team), Responsibilities, Qualifications, Pay, Benefits. Possibly also Skills? But Qualifications already covers skills. We'll keep Qualifications. We need to avoid repeating job title as heading. So no
Administrator – Customer Care
. Good. We need to not put Job ID etc. There's none. We need to remove boilerplate: EEO, equal-opportunity, scam-warning, etc. At end there is EEO statement, Los Angeles County etc. We must drop those. Also remove "Learn more about Working at Wesco here and apply online today!" etc. That's application instructions; drop. Also remove "Additional details about benefits are available here ." maybe keep as part of benefits? It's a link; we can drop the link but keep the sentence? The instruction: remove application instructions. That sentence is about benefits details link; maybe we can keep the benefits description but drop the link phrase. Safer to drop the whole sentence "Additional details about benefits are available here ." as it's a link. But we already have benefits description; we can keep the description before that. Also remove "Founded in 1922 and headquartered in Pittsburgh, Wesco is a publicly traded (NYSE: WCC) FORTUNE 500® company." That's part of About The Team; we can keep as it's substantive about company. Also remove "Wesco International, Inc., including its subsidiaries and affiliates (“Wesco”) provides equal employment opportunities to all employees and applicants for employment..." That's EEO boilerplate; drop. Also drop "US applicants only, we are an Equal Opportunity Employer." etc. Also drop "Los Angeles Unincorporated County Candidates Only: ..." etc. Also drop "This posting is for a current, active vacancy intended for immediate hire." That's maybe minor metadata; we could fold into a short p or drop. Probably drop. Now construct HTML. We'll have:About the role
As a Administrator – Customer Care, you will be responsible for completing administrative daily tasks for assigned locations in accordance with established levels of service, productivity, and quality, while servicing our customer at the most economical cost.
At Wesco, we build, connect, power and protect the world. As a leading provider of business-to-business distribution, logistics services and supply chain solutions, we create a world that you can depend on. Our Company’s greatest asset is our people. Wesco is committed to fostering a workplace where every individual is respected, valued, and empowered to succeed. We promote a culture that is grounded in teamwork and respect. With a workforce of over 20,000 people worldwide, we embrace the unique perspectives each person brings. Through comprehensive benefits and active community engagement, we create an environment where every team member has the opportunity to thrive. Founded in 1922 and headquartered in Pittsburgh, Wesco is a publicly traded (NYSE: WCC) FORTUNE 500® company.
But note: The "About The Team" includes the first sentence about As a Administrator... Actually that's from Job Description paragraph. We already used that as role description. The About The Team paragraph starts with "At Wesco, we build..." So we should separate. Thus:About the role
As a Administrator – Customer Care, you will be responsible for completing administrative daily tasks for assigned locations in accordance with established levels of service, productivity, and quality, while servicing our customer at the most economical cost.
About the team
maybe but they said use headings like About the role, Responsibilities... Not About the team. But we could still use About the role for the first paragraph, and maybe we don't need a separate About the team; we could incorporate company description into About the role? But that would mix. Better to have About the role (the role description) and maybe a separate section "About the company" but not in list. Since they only gave examples, not strict list; they said usefor section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can use those exact headings if appropriate. We have content for About the role (the first paragraph). For company description, we could put under About the role as well, but that may be okay. However, we might also create a section "About the team" but that's not in the examples; risk of being considered not allowed? The instruction: "Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." The "e.g." suggests those are examples, not exclusive list. So we can use other headings if needed, but better to stick to those. We could put company description under About the role as well, making that section longer. That seems fine. Thus:
About the role
As a Administrator – Customer Care, you will be responsible for completing administrative daily tasks for assigned locations in accordance with established levels of service, productivity, and quality, while servicing our customer at the most economical cost.
At Wesco, we build, connect, power and protect the world. As a leading provider of business-to-business distribution, logistics services and supply chain solutions, we create a world that you can depend on. Our Company’s greatest asset is our people. Wesco is committed to fostering a workplace where every individual is respected, valued, and empowered to succeed. We promote a culture that is grounded in teamwork and respect. With a workforce of over 20,000 people worldwide, we embrace the unique perspectives each person brings. Through comprehensive benefits and active community engagement, we create an environment where every team member has the opportunity to thrive. Founded in 1922 and headquartered in Pittsburgh, Wesco is a publicly traded (NYSE: WCC) FORTUNE 500® company.
Now Responsibilities:Responsibilities
- Performs daily required administrative functions in accordance to written process maps.
- Interacts with and supports Sales and Sales Management including updating and generating reports, reconciling daily transactions, and assisting in providing customer service.
- Responds and acts on submittals within Sales Portal in specified time periods of request.
- Performs timely and accurate completion of branch audit and compliance steps per established guidelines.
- Maintains high level of organization of tasks between assigned branches.
- Documents and submits individual task KPI data used for process improvement.
- Assists Customer Care Manager in development and training of employees.
- Researches tax and freight claims and runs credit memo when appropriate.
- Works with Financial Services to clear claims.
- Adds new customers into WESNET and PACT and runs WESNET user branch security reports.
- Notifies branch administrative manager if any discrepancies.
- Performs basic accounting duties such as light accounts receivables and payables