Peak-Season Service Cloud Scale-Up and Handover for Harborline Retail
Engagement summary
ForceFolks embedded a project manager, Salesforce administrator, developer and QA engineer with Harborline Retail from 2 September 2024 to 28 February 2025. The client’s Senior Director of Customer Care retained priorities and release approval. Harborline handled 3.1× its prior-year peak case volume from 25 November to 31 December. The client accepted the handover in February, and ForceFolks ended its allocation by 28 February 2025.
Client and Engagement Facts
| Field | Engagement detail |
|---|---|
| Client | Harborline Retail |
| Client and industry | Harborline Retail, retail and ecommerce |
| Location and overlap | Toronto, Canada. Nearshore ForceFolks staffing with seven hours of daily Eastern Time overlap. |
| Salesforce products | Service Cloud, Commerce Cloud and Marketing Cloud Engagement |
| Delivery tools | Jira, GitHub, Copado and Salesforce CLI |
| Term and allocation | 2 September 2024 to 28 February 2025. Project manager at 100% September to December and 50% January to February. Administrator at 100% September to January. Developer at 100% September to December and 50% in January. QA engineer at 100% October to December and 50% in January. |
| Client ownership | The Senior Director of Customer Care owned priorities, release approval and milestone acceptance. Harborline’s internal team took over operations in March. |
Why the Client Added Capacity
Harborline’s three-person internal team faced peak-season demand and a new returns policy scheduled for November. It needed temporary engineering and QA capacity alongside its existing staff. Harborline agreed an exit schedule in October and required the pod to leave a runbook, test coverage and clear ownership for the client’s team.
Client corroboration
“Our team took the platform back in March with a runbook, an ownership matrix and a test suite we did not have in September.”
Role Contributions and Acceptance
| ForceFolks role | Work and outputs | Client review or acceptance |
|---|---|---|
| Project manager | Coordinated dependencies, a 96-scenario UAT plan, readiness reviews for three releases and the handover schedule. | Senior Director of Customer Care at each milestone. |
| Salesforce administrator | Updated returns and order-status queues, routing rules, permissions and dashboards for three care teams. | Client care operations manager. |
| Salesforce developer | Built the returns policy in Apex and Flow and linked Commerce Cloud orders to Service Cloud cases. The client reviewed 12 merged pull requests. | Client platform lead via pull request. |
| Salesforce QA engineer | Automated 214 regression scenarios for permissions, flows and integrations. Retested 63 defects and recorded client-approved deferrals. | Client platform lead at each release. |
Outcomes and Evidence
| Measure | Baseline | Result | Window | Source |
|---|---|---|---|---|
| Peak case volume handled | 1.0× the prior-year peak | 3.1× the prior-year peak | 25 November to 31 December 2024 | Harborline Service Cloud analytics |
| Critical production defects | Client severity criteria | 0 critical defects during peak operations | November to December 2024 | Client defect log |
| Regression scenarios automated | 0 automated scenarios | 214 automated scenarios | September 2024 to January 2025 | Client Copado test records |
| Releases accepted | 3 releases in scope | 3 accepted | September 2024 to January 2025 | Client release log |
| Allocation and handover | 4 FTE at peak allocation | Runbook and ownership matrix signed 21 February. ForceFolks allocation ended by 28 February. | February 2025 | ForceFolks allocation and client handover records |
Related roles and delivery services
Discuss the work your team needs
Share the Salesforce work, roles and client review responsibilities. ForceFolks will assess the staffing requirement against that scope.
Discuss your staffing requirement