Designing a Jira Service Management Solution for a Field Engineering Business

After we delivered a Free Wellness Check, a UK communications and networking company identified several opportunities to improve how their support operation worked. They were already using Jira Service Management internally, but didn’t have a customer-facing service platform that reflected how their field engineers actually worked.

The company handles installation, maintenance, and tech support across the UK, with engineers visiting customer sites regularly. Their old setup made it hard to separate internal work from customer support and caused problems with ticket visibility, communication, and managing workflows for field engineers.

Following the Wellness Check, the company asked us to carry out a deeper assessment of their service operations and support processes. Through a series of workshops with service desk staff, engineers, and key stakeholders, we reviewed existing workflows, request management processes, customer communications, reporting requirements, and integration points.

This assessment provided a much clearer picture of how work flowed through the business and highlighted several opportunities for improvement. The collaborative workshop approach also helped build confidence in Sourcesense as a delivery partner, as stakeholders could see recommendations being shaped around their operational requirements and challenges rather than a generic Jira Service Management implementation.

Using the findings from the assessment workshops, we developed a project to build a scalable Jira Service Management (JSM) solution that improved the customer experience, supported field operations, and kept administration and licensing costs under control.

Understanding the Operational Challenges

One big challenge was adapting Jira Service Management to fit a field engineering business instead of a regular helpdesk. Many support requests needed engineers to visit customer sites, give updates remotely, and work closely with the service desk team. But giving every engineer full JSM agent access would have raised licensing costs a lot and made daily management more complicated.

During the assessment workshops, we also reviewed customer request forms, email-based support processes, engineer handoffs, SLA management, and how external customer issues were being tracked. This helped identify several areas where existing processes were creating additional effort for both customers and internal teams.

The Wellness Check and subsequent assessment workshops identified several usability and process challenges, including:

• Not enough separation between customer-facing and internal workflows

• Request forms were too complicated and ticket visibility was poor

• Workflow stages didn’t match how engineers actually work

• Updates and SLA tracking had to be done manually

• Customer communications and notifications were inconsistent

• A lot of external customer issues were being managed by spreadsheets

• Customer email requests required significant manual processing before work could be assigned correctly

• Existing forms collected too much information from customers while still missing key details needed by internal teams

Designing the Solution

Using the findings from the assessment, we built a dedicated Jira Service Management setup based on how the company actually works, rather than relying on a standard template. The new service desk added custom request types, workflows, SLAs, automations, and portal designs that fit both customers and internal teams.

The main goal was to make things simple for customers while keeping all the details the team needed. We redesigned the portal forms so customers only saw what mattered to them, while internal and billing info stayed hidden. This made support look cleaner and more professional without losing any features for the team. We also changed workflows to match real engineering work better.

New statuses like “Preparing” and “Pending Approval” helped track ticket progress more clearly. Some existing statuses were renamed to make updates clearer for customers and agents. For example, “With Engineer” became “Work Scheduled” to better show the actual work stage.

Supporting Field Engineers Without Additional Agent Licences

A key part was finding a way for field engineers to work with Jira Service Management without needing full agent licences. Instead of making engineers agents, we set them up as portal customers with limited access to the tickets they needed.

This let them securely see requests, give updates, and comment through the portal, while the service desk team kept admin control. The lead engineer kept full control over queues, workflows, tickets, and customer communication, while field engineers could update work in real time from the field.

This setup clearly separated engineering work from service management tasks and kept licensing costs manageable as the business grew.

Automation and Communication Improvements

Automation helped cut down on manual administration in the new JSM setup. Using Jira Service Management’s built-in email channel and automation capabilities, we created rules to process incoming customer emails, populate and update fields automatically, and route requests to the correct teams. This removed the need for additional apps, reduced manual triage effort, and made requests more consistent. Building these automations took extensive testing and fine-tuning to handle different customer email formats and reliably extract information using smart values, conditions, and string matching.

Customer communication was also improved through branded email templates and simplified notification layouts, creating a more professional experience and reducing follow-up queries caused by unclear updates.

The Outcome

The final setup gave the company a customer support platform that really fits how a field engineering business works.

By separating customer support from internal work, the company got clearer workflows, better SLA tracking, and a more organised support process that matches their daily work.

The new system also improved teamwork between service desk staff and field engineers, cut down manual admin with automation, and gave the business a more scalable and cost-effective licensing model for the future.