customers and properties
Customers and properties
Use customer and property records as the anchors for site context, field history, and follow-up work.
Why customers and properties matter
HeyFlora uses customers and properties as the anchors for field observations, knowledge, proposals, reports, and follow-up work.
Customers identify the account relationship. Properties identify the physical site where conditions, preferences, risks, services, and field history accumulate.
Where to work
Use /crm for customer lists. Open a customer detail page to review the account. Open a property detail page for site-specific context.
Property-linked pages are where related field observations, plant-health work, huddles, and future business outputs become useful because they connect to a real site.
Before asking Flora
Open the customer or property when the question depends on a specific site. This helps Flora use the right context and reduces back-and-forth. If you are not sure which record to use, ask Flora to look up matching customers or properties.
Flora chat behavior
When a workflow depends on a customer or property, Flora should look up available records and present grounded choices. It should not ask you to type names from memory when the product can show actual records.
Current scope
The beta docs describe customer and property lookup and context usage. They do not claim HeyFlora replaces a customer's existing ERP, CRM, job-costing, payroll, or fleet systems.
Related docs