Associate Procurement Helpdesk Analyst

Role Purpose & Context

Role Summary

The Associate Procurement Helpdesk Analyst is here to make sure our internal colleagues and external suppliers can actually use our procurement systems without pulling their hair out. You'll spend your days answering questions, troubleshooting basic issues, and guiding people through our Procure-to-Pay (P2P) process. It's a bit like being a detective and a teacher all at once, helping folks understand how to raise a purchase order (PO) or why an invoice might be stuck. This role sits right at the front line of our Procurement Operations team. You're the bridge between our systems and the people who need to use them, making sure everyone follows the rules and gets paid on time. You'll be taking questions on everything from 'How do I create a requisition?' to 'Why isn't my supplier getting paid?' When you do this job well, people feel supported, our processes run smoothly, and suppliers get paid. If it's not done well, colleagues get frustrated, invoices get delayed, and we end up with a lot of 'maverick spend' – that's when people buy things outside of the proper channels, which we really don't want. The challenge? You'll hear the same questions over and over, and sometimes people will be a bit stressed when they call. The reward, though, is genuinely helping someone unblock an urgent payment or finally understand a tricky process. It feels good to be the person who sorts things out.

Reporting Structure

• Reports to: Senior Procurement Helpdesk Analyst
• Direct reports: 0
• Matrix relationships: Junior Procurement Support Coordinator, P2P Helpdesk Assistant, Procurement Operations Associate,

Key Stakeholders

Internal:

• Internal Business Users (e.g., Marketing, IT, Facilities)
• Finance Team (Accounts Payable)
• Procurement Category Managers
• IT Support

External:

• Suppliers (especially Accounts Receivable teams)
• P2P Platform Vendor Support (e.g., SAP Ariba support)

Organisational Impact

Scope: This role directly impacts the efficiency and compliance of our entire purchasing process. By resolving user issues quickly, you keep projects moving, ensure suppliers are paid promptly (which keeps them happy), and help prevent costly errors or non-compliant spending. Essentially, you make sure the wheels of the business keep turning smoothly from a purchasing perspective, even if it's just by explaining 'No PO, No Pay' for the tenth time that day.

Performance Metrics

Quantitative Metrics

1. Metric: Ticket Resolution within SLA
2. Desc: The percentage of helpdesk tickets you manage to resolve within our agreed Service Level Agreement (SLA) times.
3. Target: Above 98%
4. Freq: Weekly & Monthly
5. Example: If we get 100 tickets in a week and you close 99 of them within the 4-hour SLA for priority 2 tickets, that's a 99% success rate. We're aiming for nearly perfect here, as delays can really impact the business.
6. Metric: First Call Resolution (FCR)
7. Desc: The proportion of issues you sort out on the very first interaction with the user, without needing to go back and forth or escalate.
8. Target: Above 75%
9. Freq: Monthly
10. Example: A user calls about a blocked invoice, you quickly identify it's a missing Goods Receipt, tell them exactly who to contact in their team, and the user confirms it's resolved on that first call. That counts as an FCR.
11. Metric: User Satisfaction (CSAT)
12. Desc: How happy users are with your support, measured by a quick survey after their ticket is closed.
13. Target: Average score of 4.5 out of 5.0
14. Freq: Continuous (per ticket)
15. Example: After you help someone, they get an email asking 'How was your experience?' If they consistently give you 5 stars and say 'really helpful', you're hitting the target. It's about being patient and clear.
16. Metric: Knowledge Base Usage
17. Desc: How often you use our existing knowledge base articles to resolve issues, and how often you link them in your responses.
18. Target: Link KB article in over 50% of resolutions
19. Freq: Monthly
20. Example: When someone asks 'How do I get a new supplier set up?', you link them to the 'New Supplier Onboarding Guide' article in Confluence. This shows you're using our tools and helping users help themselves next time.

Qualitative Metrics

1. Metric: Clarity of Communication
2. Desc: How clearly and patiently you explain complex procurement processes or system errors to users who might not understand the jargon.
3. Evidence: Feedback from users mentioning 'easy to understand' or 'very clear instructions'. Your written ticket notes are concise and easy for others to follow. You can explain '3-way match failure' in plain English.
4. Metric: Adherence to Process
5. Desc: Your ability to consistently follow established helpdesk procedures, including logging tickets correctly, categorising them, and escalating when needed.
6. Evidence: Regular review of your ticket logs shows correct categorisation and complete notes. Your manager rarely has to remind you about a specific step in the helpdesk workflow. You consistently apply our 'No PO, No Pay' policy.
7. Metric: Proactive Problem Identification (Basic)
8. Desc: Your ability to spot patterns in incoming tickets that might suggest a bigger, underlying issue, even if you can't fix it yourself yet.
9. Evidence: You flag to your Senior Analyst that 'we're getting a lot of calls about X from Department Y this week.' You notice that a specific supplier's invoices are always getting blocked for the same reason and mention it.
10. Metric: Team Collaboration
11. Desc: How well you work with the rest of the helpdesk team, sharing information and asking for help when you're stuck.
12. Evidence: You actively participate in team stand-ups, ask questions in the team's MS Teams channel, and offer to help colleagues when your queue is clear. You're not afraid to ask for guidance when you don't know the answer.

Primary Traits

• Trait: Patient Guide
• Manifestation: You're the sort of person who can calmly explain the difference between a P-Card purchase and a PO for the third time in an hour without sounding annoyed. You'll walk a slightly panicked colleague through a multi-step goods receipt process, screen-by-screen, without a hint of frustration. Even when someone's clearly not read the instructions, you'll still guide them through it nicely.
• Benefit: People usually contact the helpdesk because they're stuck, confused, or frankly, a bit frustrated. A patient approach really helps de-escalate that tension. It builds confidence in you and the system, and it stops minor issues from blowing up into major complaints that land on leadership's desk. We need someone who can be the calm in the storm.
• Trait: Process-Driven Guardian
• Manifestation: You'll be the one who can (politely) cite the specific procurement policy when explaining why an after-the-fact PO can't be approved. You follow our ticket documentation template precisely for every single case, no shortcuts. You're good at spotting when someone's trying to bypass a required approval step and know how to gently steer them back to the right path.
• Benefit: Honestly, the helpdesk is our first line of defence for compliance and keeping costs under control. This trait means policies are applied consistently, which creates a clear audit trail and stops those 'special exceptions' that lead to rogue spend and unnecessary risk. You're protecting the business, even if it sometimes feels like you're just saying 'no'.
• Trait: Empathetic Translator
• Manifestation: You'll often start a response with something like 'I understand how urgent this is for your project deadline.' You're good at taking procurement jargon, like '3-way match failure,' and translating it into plain business language, like 'The invoice price doesn't match the price we agreed on the purchase order.' You put yourself in the user's shoes.
• Benefit: Let's be real, Procurement can sometimes feel like a bureaucratic hurdle to people. Empathy makes users feel heard and supported, which turns the helpdesk from a roadblock into a helpful partner. This really helps with user adoption and improves the overall reputation of our procurement function across the company. It's about building bridges, not walls.

Supporting Traits

• Trait: Detail-Oriented
• Desc: You're the person who'll spot the one-digit error in a PO number that's causing an invoice to be blocked. You catch the small things that can cause big problems down the line.
• Trait: Problem-Solver (Basic)
• Desc: You enjoy the challenge of untangling a slightly complex invoicing issue or figuring out why a system isn't behaving as expected, even if you need guidance to get to the full solution.
• Trait: Articulate
• Desc: You can clearly explain a complex process in both written (ticket notes, emails) and verbal (phone calls, Teams chats) communication. You get your point across without confusing people.
• Trait: Resilient
• Desc: You can handle a decent volume of requests and the occasional frustrated user without taking it personally. You bounce back quickly from a tricky call.

Primary Motivators

1. Motivator: Helping Others Succeed
2. Daily: You'll get a real kick out of unblocking a colleague's urgent payment or guiding them through a tricky process so they can get their project moving. It's about being the person who makes things work for others.
3. Motivator: Solving Puzzles
4. Daily: Every ticket is a small puzzle to solve. You'll enjoy figuring out why an invoice is blocked or why a system isn't doing what it's supposed to, even if the answer is often simple.
5. Motivator: Working within Structure
6. Daily: You'll appreciate having clear processes, policies, and a knowledge base to follow. It's about applying known solutions to common problems, and you'll find comfort in that consistency.

Potential Demotivators

Honestly, this role isn't for everyone. You'll often be the 'policy police', which means being the face of 'no' for colleagues who are just trying to get their work done. You'll deal with users who ignore the process, create a mess (like verbally agreeing to work with a supplier), and then expect you to fix it instantly with an 'emergency' retroactive PO. The constant, thankless task of chasing business stakeholders for Goods Receipt confirmations, knowing a supplier's payment (and your relationship with them) is on the line, can be a grind. You might spend 30 minutes troubleshooting a 'critical system error' only to discover the user had their caps lock on. If you need constant novelty or get easily frustrated by repetition, this might not be your cup of tea.

Common Frustrations

1. Getting caught between an angry supplier demanding payment and a business unit that hasn't approved the invoice yet.
2. Explaining the same five basic concepts every single day because stakeholders refuse to read the knowledge base articles you painstakingly wrote.
3. Dealing with the downstream consequences of messy supplier master data that another team is responsible for maintaining.
4. Users who expect you to magically bypass policies or create 'special' exceptions for them.
5. The sheer volume of tickets, especially during peak times, can feel overwhelming.

What Role Doesn't Offer

1. High levels of strategic decision-making or policy creation (that comes later).
2. Constant new challenges or projects (a lot of it is routine problem-solving).
3. Direct management of people or large budgets.
4. A quiet, uninterrupted work environment (the phone will ring, emails will ping).

ADHD Positives

1. The fast-paced nature of handling multiple incoming tickets can provide varied stimulation, preventing boredom.
2. The clear, structured processes for resolving common issues can offer a helpful framework, reducing cognitive load for task initiation.
3. The immediate feedback loop of solving a user's problem can be highly motivating and rewarding.

ADHD Challenges and Accommodations

1. Repetitive tasks (like chasing GRNs) might become tedious and lead to 'boredom paralysis.' We can look at rotating tasks or using AI tools to automate some of the more repetitive elements.
2. Maintaining focus during long, complex troubleshooting calls might be tricky. We can offer regular breaks or pair you with a Senior Analyst for particularly challenging cases.
3. Managing a high volume of incoming notifications (emails, calls, chat) can be overwhelming. We can help you configure notification settings and prioritise tasks.

Dyslexia Positives

1. The role relies heavily on verbal communication (phone, video calls), which can be a strength.
2. Structured templates for ticket logging and knowledge base articles can reduce the need for extensive free-form writing.
3. Visual aids within the P2P system (e.g., flowcharts, clear UI) can help with process comprehension.

Dyslexia Challenges and Accommodations

1. Reading and interpreting dense policy documents or complex system error messages might take longer. We can provide text-to-speech software or ensure key information is summarised visually.
2. Writing clear, concise ticket notes and email responses is crucial. We can offer grammar and spell-checking tools, and provide templates for common responses.
3. Quickly scanning knowledge base articles for specific information might be challenging. We can ensure our KB articles are well-structured with clear headings and bullet points.

Autism Positives

1. The highly structured nature of helpdesk processes and defined workflows can provide predictability and comfort.
2. The focus on logical problem-solving and adherence to rules ('No PO, No Pay') aligns well with a preference for clear systems.
3. Direct, factual communication is often preferred in a helpdesk context, reducing ambiguity.

Autism Challenges and Accommodations

1. Unexpected changes in user behaviour or system errors might be unsettling. We'll provide clear escalation paths and support during novel situations.
2. Interpreting nuanced social cues from frustrated users over the phone can be difficult. We can offer training on de-escalation scripts and provide a quiet space for taking calls.
3. Sensory overload from constant phone calls or a busy office environment. We can explore noise-cancelling headphones or a hybrid working model with quiet days in the office.

Key Responsibilities

Experience Levels Responsibilities

1. Level: Entry Level (L1) - Associate Procurement Helpdesk Analyst
2. Responsibilities: Answer incoming calls and respond to emails/chat messages from colleagues and suppliers (yes, even the silly ones) about our Procurement systems and processes. You're the first line of defence, so a friendly tone is key.
3. Log all incoming helpdesk tickets accurately and completely in ServiceNow (or Jira Service Management). This means categorising them correctly and adding all the necessary details, so we can track everything and learn from it.
4. Troubleshoot basic P2P system issues, like guiding a user through a password reset or helping them find a specific field in SAP Ariba. Most of the time, it's about following a script or a knowledge base article.
5. Follow up on open tickets to ensure users are getting the support they need and that issues are actually resolved. Sometimes you'll be 'chasing the GRN' (Goods Receipt Note) to get invoices paid, which can be a bit of a hunt.
6. Escalate more complex or unusual issues to a Senior Procurement Helpdesk Analyst or the relevant IT team. You'll know when something is beyond your current scope and needs an expert eye.
7. Maintain and update our knowledge base (Confluence/SharePoint) by flagging outdated articles or suggesting new content based on common questions you're getting. Future-you, and everyone else, will thank you for it.
8. Assist with basic supplier onboarding queries, like guiding a new supplier on how to use the Aravo portal to register their details. You won't be doing the full onboarding, but you'll help them get started.
9. Supervision: You'll have daily check-ins with your Senior Procurement Helpdesk Analyst, especially when you're starting out. Most of your work will be reviewed, and you'll often work in a paired setting for trickier issues. We're here to support your learning, so don't worry about asking for help.
10. Decision: Honestly, at this level, you won't be making independent decisions. All work, especially anything outside of standard, scripted responses, will be reviewed before delivery. You'll need to escalate any client contact or issues that deviate from our established procedures to your supervisor. It's about learning the ropes and understanding the boundaries.
11. Success: You'll know you're doing well when your ticket resolution times are consistently within our SLAs, users give you positive feedback, and you're confidently resolving common issues without constant supervision. We'll also be looking at how quickly you pick up new processes and how well you contribute to the team's overall efficiency.

Decision-Making Authority

• Type: Resolving a standard P2P query (e.g., 'How do I raise a requisition?')
• Entry: Execute based on documented knowledge base articles or scripts. No independent decision-making; follow the process exactly.
• Mid: N/A
• Senior: N/A
• Type: Escalating a complex system error
• Entry: Identify the issue as non-standard and immediately escalate to the Senior Procurement Helpdesk Analyst or IT Support. Do not attempt to resolve independently.
• Mid: N/A
• Senior: N/A
• Type: Approving a retroactive Purchase Order (PO)
• Entry: No authority to approve. Explain the 'No PO, No Pay' policy and guide the user through the correct (and often more difficult) process, escalating to a Senior Analyst for policy enforcement advice if needed.
• Mid: N/A
• Senior: N/A
• Type: Updating a knowledge base article
• Entry: Suggest edits or new article ideas to the Senior Procurement Helpdesk Analyst. Do not edit or publish independently.
• Mid: N/A
• Senior: N/A
• Type: Prioritising your daily ticket queue
• Entry: Follow the established priority rules in the ticketing system. Consult with your Senior Analyst if you're unsure about a specific ticket's urgency.
• Mid: N/A
• Senior: N/A

Competency Requirements

Foundation Skills (Transferable)

These are the basic human skills that make you great at any job, but especially one where you're helping people all day. We're looking for someone who can communicate clearly, solve problems, and generally be a good egg.

• Category: Communication & Interpersonal Skills
• Skills: Active Listening: Really hearing what the user is asking, not just waiting for your turn to speak.
• Clear Written Communication: Writing emails and ticket notes that are easy to understand, even for someone who knows nothing about procurement.
• Verbal Articulation: Explaining processes patiently and clearly over the phone or video calls.
• Customer Service Mindset: Always aiming to help and make the user's experience as smooth as possible, even when you have to say 'no'.
• Category: Problem-Solving & Initiative
• Skills: Basic Troubleshooting: Following a logical path to figure out what's gone wrong, using our guides and your common sense.
• Resourcefulness: Knowing where to look for answers (knowledge base, team members) before escalating.
• Attention to Detail: Spotting small errors in PO numbers or invoice details that can cause big headaches.
• Task Prioritisation: Managing your incoming tickets and knowing what needs to be done first, even if it's just following the system's priority.
• Category: Teamwork & Adaptability
• Skills: Collaboration: Working well with your helpdesk colleagues, sharing tips, and asking for help when you're stuck.
• Openness to Feedback: Taking on board advice from your Senior Analyst to improve your approach.
• Learning Agility: Quickly picking up new system features or process changes. Things do change, so you'll need to roll with it.

Functional Skills (Role-Specific Technical)

These are the more specific bits of knowledge and the tools you'll be using day-in, day-out. Don't worry if you're not an expert in everything; we'll teach you the ropes, but a basic understanding helps.

Technical Competencies

• Skill: Procure-to-Pay (P2P) Lifecycle Mastery (Basic)
• Desc: Understanding the very basics of how we buy things: from someone needing something (requisition) to us paying for it (invoice and payment). You'll learn the steps like requisition creation, PO dispatch, goods receipt, and invoice processing.
• Level: Basic
• Skill: Root Cause Analysis (RCA) - Basic
• Desc: The ability to ask 'why' a few times to get past the immediate problem and understand what might be causing it. You won't be fixing systemic issues yet, but you'll learn to spot patterns and flag them.
• Level: Basic
• Skill: Knowledge-Centered Service (KCS) - Basic
• Desc: Understanding that every interaction is a chance to improve our knowledge base. You'll learn to use existing articles and flag when new ones are needed, helping everyone find answers faster.
• Level: Basic
• Skill: SLA/OLA Management (Basic)
• Desc: Knowing what our Service Level Agreements (SLAs) are for ticket resolution and understanding why hitting those targets is important for keeping our colleagues happy and operations smooth.
• Level: Basic
• Skill: Supplier Onboarding & Data Management (Basic)
• Desc: A basic grasp of what's involved in getting a new supplier set up in our system, like guiding them to the right portal or explaining why we need their bank details. You'll understand the importance of accurate supplier data.
• Level: Basic

Digital Tools

• Tool: SAP Ariba or Coupa (P2P Platform)
• Level: Intermediate
• Usage: You'll be guiding users through standard requisition-to-PO-invoice processes, looking up PO statuses, and troubleshooting basic mismatches. You'll be in this system all day, every day.
• Tool: ServiceNow or Jira Service Management (Ticketing System)
• Level: Intermediate
• Usage: You'll be logging, categorising, and resolving tickets, following our defined SLA protocols. This is where you'll manage your workload and communicate with users.
• Tool: Confluence or SharePoint (Knowledge Base)
• Level: Basic
• Usage: You'll be searching and using existing articles to resolve user issues and flagging any outdated content or gaps you spot. It's your go-to for answers.
• Tool: Microsoft Excel
• Level: Intermediate
• Usage: You'll use `VLOOKUP`, `INDEX/MATCH`, and Pivot Tables to cross-reference PO data, supplier lists, or basic ticket data. It's for quick data checks, not complex analysis.
• Tool: MS Teams or Slack (Collaboration)
• Level: Intermediate
• Usage: You'll use this for real-time communication with your team, sharing ticket updates, and participating in team channels. It's how we stay connected.
• Tool: Aravo or Graphite (Supplier Management)
• Level: Basic
• Usage: You'll guide users on how to use the portal for new supplier registration and check the status of an onboarding request. You're helping people get started with new suppliers.

Industry Knowledge

• Area: Basic Procurement Terminology
• Desc: Understanding common terms like 'Purchase Order (PO)', 'Invoice', 'Goods Receipt Note (GRN)', 'Supplier', and 'Maverick Spend'. You'll pick these up quickly.
• Area: Company Purchasing Policies
• Desc: A general awareness of our internal rules for buying things, such as 'No PO, No Pay' and when to use preferred suppliers. You'll be enforcing these daily.

Regulatory Compliance Regulations

• Reg: Internal Procurement Policies
• Usage: You'll be applying our internal purchasing policies, such as the 'No PO, No Pay' rule and guidelines around supplier selection, to helpdesk queries. You're the first line of defence in ensuring compliance.
• Reg: Data Protection (GDPR) Basics
• Usage: Understanding the basics of handling personal or sensitive supplier data (e.g., bank details) in line with GDPR. You'll know not to share information inappropriately and how to keep it secure.

Essential Prerequisites

• A genuine desire to help people and solve problems, even if they're repetitive.
• Excellent communication skills, both written and verbal, in English.
• Basic computer literacy, including experience with Microsoft Office (especially Excel for simple data tasks).
• The ability to learn new software systems quickly – we'll teach you ours, but you need to be a quick study.
• A structured approach to work; you can follow a process and pay attention to details.
• Experience in a customer service or support role, even if it wasn't in Procurement, is a big plus.

Career Pathway Context

We're looking for someone with the right attitude and a foundational set of skills. We don't expect you to be a procurement expert on day one. We'll provide all the training you need on our specific systems and processes. What we can't teach is a helpful, patient, and process-driven mindset. If you've got that, you're off to a great start for a career in Procurement Operations.

Qualifications & Credentials

Emerging Foundation Skills

• Skill: AI-Assisted Problem Solving
• Why: AI is getting better at suggesting solutions and identifying patterns in helpdesk tickets. Analysts who can effectively use these tools will be much faster and more accurate than those who don't.
• Concepts: [{'concept_name': 'Prompt Engineering (Basic)', 'description': 'Learning how to ask AI tools the right questions to get the best answers for your users or to summarise complex information quickly.'}, {'concept_name': 'Output Validation', 'description': 'Knowing when to trust an AI-generated answer and when to double-check it. AI is a tool, not a replacement for your judgment.'}, {'concept_name': 'Contextual AI Usage', 'description': 'Understanding which AI tool is best for which task – e.g., one for drafting emails, another for summarising policy documents.'}]
• Prepare: This week: Start using AI tools (like ChatGPT or Claude) for drafting simple emails or summarising long documents in your personal life.
• This month: Experiment with using our internal AI helpdesk tools for drafting responses to common queries, always reviewing the output.
• Month 2: Share your 'best prompts' with the team and learn from others' experiences.
• Month 3: Actively flag any instances where AI output was incorrect or misleading to your Senior Analyst, helping us improve the tools.
• QuickWin: Start using our internal AI-powered knowledge base suggestions today—it's there to help you find answers faster without any extra effort.
• Skill: Data Literacy for Helpdesk Trends
• Why: As more data is collected from our ticketing systems, understanding basic trends will help you spot recurring issues and contribute to proactive problem-solving, rather than just reactive ticket closing.
• Concepts: [{'concept_name': 'Basic Data Interpretation', 'description': "Understanding what simple charts and graphs (e.g., 'tickets by category' or 'resolution time trends') are telling you."}, {'concept_name': 'Pattern Recognition', 'description': 'Spotting when a certain type of ticket is increasing or coming from a specific department, which might indicate a larger issue.'}, {'concept_name': 'Impact of Data Quality', 'description': 'Understanding why logging tickets accurately is crucial for any future analysis.'}]
• Prepare: This week: Pay extra attention to how you categorise tickets – think about how that data might be used later.
• This month: Ask your Senior Analyst to show you some of the basic helpdesk reports and explain what they mean.
• Month 2: Try to identify a recurring issue based on your own ticket volume and flag it to your team.
• Month 3: Learn to use basic Excel functions to sort and filter ticket data for simple trend spotting.
• QuickWin: Make sure every ticket you close has the correct category and sub-category. Good data in means good insights out.

Advancing Technical Skills

• Skill: Advanced P2P Platform Navigation & Troubleshooting
• Why: As our P2P platform (SAP Ariba/Coupa) evolves with new features, you'll need to understand more complex workflows and be able to troubleshoot issues beyond the most basic ones. This includes understanding approval hierarchies and basic system configurations.
• Concepts: [{'concept_name': 'Approval Workflow Logic', 'description': 'Understanding how different types of requisitions or invoices get routed for approval and why they might get stuck.'}, {'concept_name': '3-Way Match Details', 'description': 'Deepening your understanding of how purchase orders, goods receipts, and invoices need to match up, and common reasons for failure.'}, {'concept_name': 'Basic User Role Permissions', 'description': "Knowing what different user roles can and can't do in the system, which helps in diagnosing access issues."}]
• Prepare: This week: Pay close attention when a Senior Analyst helps you troubleshoot a complex P2P issue; ask 'why' they're doing what they're doing.
• This month: Take a deeper dive into the P2P platform's training modules, focusing on approval workflows.
• Month 2: Shadow a Finance colleague to understand their side of the invoice processing, particularly for blocked invoices.
• Month 3: Propose a new knowledge base article based on a complex P2P issue you've helped resolve.
• QuickWin: Spend 15 minutes each week exploring a new section of the P2P platform you don't usually use, just to see what's there.
• Skill: Enhanced Ticketing System Configuration (Basic)
• Why: You'll move beyond just logging and resolving tickets to understanding how the system itself is configured. This will help you suggest improvements and become more efficient.
• Concepts: [{'concept_name': 'Ticket Routing Rules', 'description': 'Understanding how tickets get assigned to different teams or individuals based on their category or keywords.'}, {'concept_name': 'Basic Reporting & Dashboards', 'description': 'Learning how to pull simple reports from the ticketing system to see your own performance or common ticket types.'}, {'concept_name': 'Service Level Agreement (SLA) Configuration', 'description': 'Understanding how SLAs are set up and triggered within the ticketing system.'}]
• Prepare: This week: Ask your Senior Analyst to walk you through how our ticket categories and routing rules are set up.
• This month: Try building a very basic personal dashboard in ServiceNow/Jira to track your own ticket volume and resolution times.
• Month 2: Suggest a small improvement to a ticket template or a common response based on your daily experience.
• Month 3: Learn how to use the search functions in the ticketing system to find similar past issues more effectively.
• QuickWin: Customise your personal view in the ticketing system to show you the most relevant information at a glance, making your daily work quicker.

Education Requirements

• Level: Minimum
• Req: GCSEs (or equivalent) including English and Maths at grade C/4 or above.
• Alts: We're open to candidates who can demonstrate equivalent practical experience in a customer service or administrative role, even if you don't have formal qualifications at this level. Show us you can do the job!
• Level: Preferred
• Req: A-Levels or a relevant vocational qualification (e.g., Business Administration, Customer Service) at Level 3 or 4.
• Alts: While not essential, these qualifications show a foundational understanding of business operations or customer interaction, which is always a plus.

Experience Requirements

You'll ideally have 0-2 years of experience in a customer service, administrative support, or helpdesk role. This could be anything from retail customer service to an office administrator. What really counts is that you've dealt with people, solved their problems, and used computer systems. We're looking for someone who's comfortable working with processes and can communicate clearly, even if you've never touched a procurement system before.

Preferred Certifications

• Cert: ITIL Foundation
• Prod: Axelos
• Usage: Shows a basic understanding of IT service management best practices, which aligns well with our helpdesk operations and how we manage tickets and services.
• Cert: Customer Service Practitioner (Level 2/3 Apprenticeship)
• Prod: Various (UK Apprenticeship Standards)
• Usage: Demonstrates a solid foundation in customer interaction, problem-solving, and communication skills, which are absolutely essential for this role.

Recommended Activities

• Completing internal training modules on our P2P platform (SAP Ariba/Coupa) to deepen your system knowledge.
• Shadowing colleagues in Finance (Accounts Payable) to understand the full invoice-to-payment process.
• Participating in webinars or online courses on customer service excellence or basic business administration.
• Actively contributing to the team's knowledge base by suggesting improvements or new articles.
• Seeking feedback regularly from your Senior Analyst and acting on it to improve your skills.

Career Progression Pathways

Entry Paths to This Role

• Path: Customer Service Representative / Call Centre Agent
• Time: 0-2 years
• Path: Office Administrator / Junior Administrator
• Time: 1-2 years
• Path: Recent Graduate (Non-Procurement Degree)
• Time: 0-1 year

Career Progression From This Role

• Pathway: Procurement Helpdesk Analyst (Level 2)
• Time: 18-36 months

Long Term Vision Potential Roles

• Title: Senior Procurement Helpdesk Analyst (Level 3)
• Time: 3-5 years
• Title: Lead Procurement Systems Analyst (Level 4)
• Time: 5-8 years
• Title: Procurement Operations Specialist / Manager (Level 5)
• Time: 8-12 years

How Zavmo Delivers This Role's Development

DISCOVER Phase: Skills Gap Analysis

Zavmo maps your current competencies against all requirements in this job description through conversational assessment. We evaluate your foundation skills (communication, strategic thinking), functional skills (CRM expertise, negotiation), and readiness for career progression.

Output: Personalised skills gap heat map showing strengths and priorities, estimated time to competency, neurodiversity accommodations.

DISCUSS Phase: Personalised Learning Pathway

Based on your DISCOVER results, Zavmo creates a personalised learning plan prioritised by impact: foundation skills first, then functional skills. We adapt to your learning style, pace, and neurodiversity needs (ADHD, dyslexia, autism).

Output: Week-by-week schedule, each module linked to specific job responsibilities, checkpoints and milestones.

DELIVER Phase: Conversational Learning

Learn through conversation, not boring modules. Zavmo uses 10 conversation types (Socratic dialogue, role-play, coaching, case studies) to build competence. Practice difficult QBR presentations, negotiate tough renewals, and handle churn conversations in a safe AI environment before facing real clients.

Example: "For 'Stakeholder Mapping', Zavmo will guide you through analysing a complex enterprise account, identifying key decision-makers, and building an engagement strategy."

DEMONSTRATE Phase: Competency Assessment

Zavmo automatically builds your evidence portfolio as you learn. Every conversation, practice scenario, and application example is captured and mapped to NOS performance criteria. When ready, your portfolio supports OFQUAL qualification claims and demonstrates competence to employers.

Output: Competency matrix, evidence portfolio (downloadable), qualification readiness, career progression score.