The customer is seeking enhanced support for multi-site customer structures, specifically concerning HaloPSA Sites. Their current HaloPSA setup involves a parent company with multiple locations configured as Sites beneath it. The customer requires the ability to create opportunities, quotes, and reporting directly against these individual HaloPSA Sites, rather than solely against the parent Company record. Salesbuildr's current architecture anchors all opportunities, quotes, and reporting to Company entities, treating HaloPSA Sites primarily as delivery/shipping addresses. The recommended solution from Salesbuildr's automated responses was to restructure each site into a separate child Company record within HaloPSA, linked to the parent. The customer views this as a significant functional gap, as restructuring their HaloPSA hierarchy would involve a large-scale change impacting customers, contracts, assets, tickets, and reporting. They inquired whether this limitation is due to HaloPSA API constraints or Salesbuildr's product design, and if any workarounds (e.g., custom fields, tags) exist to identify billing sites without full restructuring.
Please authenticate to join the conversation.
New
Feature Request
4 days ago
Get notified by email when there are changes.
New
Feature Request
4 days ago
Get notified by email when there are changes.