What the team needed after submission
A project request can start on any of several service pages. The team needs to know what the customer asked for, where the request came from and who should respond.
This project connected intake, record creation, assignment and follow-up. The business could keep its other systems in place.
Eight forms, one place to review requests
We connected eight website forms to a lead CRM and kept the inquiry details with each record. Staff could review requests in a queue and track the next action.
Ownership and follow-up needed to be clear even when an optional connection to another system was switched off.
- Form submissions enter a consistent record structure.
- Service and source context stay attached to the inquiry.
- Staff can organize work and identify the next action.
- Connections to other systems can be enabled separately.
What was tested
The September 4, 2026 release record documents CRM version 1.0.3 and checks across all eight forms through internal entry interfaces. Those checks established the recorded capture and workflow behavior.
The record did not establish a complete public form-to-inbox test for every route. Internal API checks leave those external steps to be verified separately.
Start with one reliable lead record
Keep one record for each lead and update it as the work moves between people and systems. A reliable intake queue and a clear assignment rule can be a useful first release. Later connections should add to that record without creating competing copies.
Try the interactive example to capture a fictional inquiry, assign it and prepare a project handoff. The example does not mean every HTSG regional system shares a live CRM.
