Skip to main content

Client Portal for Repair Services Company

Salesforce Field Service solution implementation to improve the efficiency of the online order and billing processes for customers

Published by jetbi
30 March 2023
Salesforce

Project description 

Client, a company providing home repair services for individual and corporate customers across London (UK), has implemented the Salesforce Field Service solution. To improve the efficiency of the online order and billing processes for customers, desktop and mobile access for Technicians to featured information it was decided to use Communities.

 

Goals 

  • Give customer efficient tool for online orders creation;
  • Make the transition to a new community invisible to the client;
  • Save look and feel of Client’s website;
  • Get rid of old mobile application;
  • Give Technicians access to basic reports and dashboards

 

Tasks

  • During developing the front-end part of the customer community, fully reproduce the version of the client's booking system before the community;
  • Implement custom domain;
  • Make Communities mobile optimized;
  • Brand Technicians’ community, create reports and dashboards

 

JET BI services performed

  • Created, configured, and Designed Customer Community;
  • Created and configured Technician Community;
  • Implemented a mobile-optimized version of Customer Community;
  • Implemented logic for image compression during Work Order creation;
  • Created logic for video adding during Work Order creation;
  • Developed custom calendar;
  • Integrated with address population service to assist the customer to fill in the address;
  • Redesigned Customer Community in line with current trends;
  • Implemented logic to block the possibility of creating Work Orders by debtors;
  • Developed 46 Customer Community web automation tests to test the Customer Community scenario of order booking;
  • Configured scheduler for a daily test run;
  • Created reports to be sent to the customer and team members at the end of the test run;
  • Ongoing maintenance and support services.

 

The core business scenario on the Customer

Community:

  1. Customer logins/registers to the Community;
  2. The customer chooses Work Types, describes jobs that need to be done, adding photos/videos of the issue;
  3. Adds Work-site Address, rough estimate the visit will need, selects Technician, suitable date from the calendar, available start time, adds Payment Card;
  4. Completes Booking;
  5. Reviews Order Details

salesforce-field-service-case

Picture 1: Select Service Page of Customer Community

 

salesforce-field-service-case-1

Picture 2.1: Choose Address and Time Page of Customer Community - Address selection

 

salesforce-field-service-case-2

Picture 2.2: Choose Address and Time Page of Customer Community - Calendar

 

salesforce-field-service-case-3

Picture 3: Booking Summary Page of Customer Community 

 

salesforce-field-service-case-4

Picture 4: Home Page of Technician Community

 

Results:

  • More than 50% of orders are made using Customer Community;
  • Reduced number of bookings via email/phone;
  • Continuous Community quality reports are available for the customer and team daily without manual testing iterations;
  • Technicians have portal where up-to-date statistical information can be found
Start your project now
Expertise
JET BI TEAM
  • 2 Salesforce Developers
  • 1 Salesforce Consultant
  • 1 Salesforce Administrator
  • 1 QA ISTQB Certified Specialist
TECHNOLOGIES
  • Salesforce
  • Field Service
  • APEX
  • Apex Classes and Triggers
PROJECT TIMELINE
  • 6 months
Question to the expert
image

We have available resources to start working on your project within 5 business days

1 UX Designer

image

1 Admin

image

2 QA engineers

image

1 Consultant

image
Related Articles
All articles
image
Is Salesforce Winning the Public Sector Race?
An analysis of Salesforce's rapid expansion into the U.S. public sector, tracing its path from cautious early government licensing deals in the 2010s through the launch of Government Cloud in 2012, its pivotal role in COVID-19 vaccine rollouts, and its 2025–2026 push into military and intelligence work via Agentforce and Missionforce. The piece covers major 2026 contracts — including a $5.6 billion Army deal, a $1.6 billion VA agreement, and Pentagon Impact Level 5 authorization — alongside real-world case studies like California's REAL ID processing and the UK's NHS back-office operations. It also examines the structural obstacles still facing Salesforce and other vendors in government tech: legacy IT systems decades old, outdated federal procurement rules, budget constraints, and organizational caution around AI adoption, plus the competitive pressure from Palantir, Microsoft, and Oracle in the race for public sector AI spending.
28 August 2026
image
Why Your Salesforce Flows Are Agentforce's Biggest Problem
This article argues that the most underestimated risk in Agentforce deployments isn't data quality — it's the automation layer: years of overlapping Flows, Process Builder processes, Apex triggers, and managed package logic that no one has reviewed end-to-end. It explains why AI agents inherit automation complexity without the tribal knowledge human admins carry, why technical debt only becomes visible after an agent hits it in production, and why a clean demo is no indicator of production readiness. The article closes with a concrete, tool-by-tool inventory approach using Flow Trigger Explorer, Salesforce Optimizer, Setup Audit Trail, Apex Debug Logs, Agent Builder, and Health Check — scoped to the specific processes the agent will actually use rather than the whole org.
23 July 2026
image
How to Wire Multiple Salesforce Projects in One Org Without Breaking Everything
This article maps the real integration patterns that emerge when multiple Salesforce projects — both managed packages and unpackaged code — share a single org. It covers four concrete patterns: attaching custom triggers to package-owned objects, calling global members exposed by managed packages, writing directly into another project's objects, and runtime-guarded reads of package data. It then addresses access control for authenticated and guest users, including the Master-Detail wall and the without sharing elevation pattern. The piece closes with eight concrete risks (compile-time dependencies that block uninstall, upgrade coupling, silent cascade failures, access invisible to admins) and six actionable recommendations for keeping cross-project coupling manageable.
08 July 2026