About Account Management

Whoever manages a programme for a multi-site customer: a retailer with a fire alarm contract across forty stores, a property manager with a portfolio.

The programme is a spreadsheet of which stores are covered, which inspection types are in scope and which are billed extra. It drifts from the customer records, and a store that was added last month is inspected under the wrong pricing.

A grid of accounts with customer count, building count, inspection types and service types. Add National Account takes a name, the account's vendor ID for you, and an address. An account opens to a dashboard with tabs for Dashboard, Details, Customers, Coverage, Contacts and Publishing: cards for Customers Covered, Buildings Covered, Jobs and Revenue over 12 months, with Revenue by Month and Revenue by Customer. Coverage lists the customers and covered buildings with per-building overrides, and the Inspection Types and Service Types the account's pricing includes. An Invite Portal page invites the account's contacts into the Customer Portal.

• Coverage is a record, not a memory. Which customers, which buildings, which types, with per-building overrides where one site is different.
• The programme has a P&L. Revenue by month and by customer, for the account as a whole, without adding up forty invoices.
• The account's people see their own portal. Invite Portal gives the national contact a view across every covered site.

Everyone in the office. The customer record is where most days start.

A customer's jobs are in the scheduler, their invoices in accounting, their deficiencies in a report folder and their contacts in a phone. Answering "how are we doing with this customer?" means opening four systems.

The customer grid with search, a Tags filter and actions. Add Customer is a modal; Merge Customer folds a duplicate into the record you keep; Import loads a spreadsheet. The customer record is the richest screen in the module: a header with an actions row, a stats strip (Buildings, Locations, Assets, Active Jobs, Open Quotes), and a pill bar of Overview (Job Activity and Quote Pipeline charts, Recent Jobs, Open Quotes, Quick Notes, Tags, Custom Fields, and a Create group for Inspection, Service, Service Quote and Quote), Activity, Locations, Buildings, Jobs, Reports, Deficiencies, Svc Quotes, Quotes, Contacts, Billing (Total Billed, Paid, Outstanding, Invoices), Documents, and More (Coverage, Contracts, Defaults, Portal Publishing). A Working Window page sets scheduling windows per inspection and service type, and Invite Portal invites the customer's contacts.

• The whole relationship on one record. Jobs, reports, deficiencies, quotes, invoices, contacts and documents are pills on the same page.
• Create from the record. An inspection, service, service quote or quote started from the customer's Overview is already pointed at the right customer.
• Duplicates are merged, not deleted. Merge keeps one record and folds the other's history into it.
• Scheduling windows live with the customer. "Not before 7am, not on Fridays" is set once and honoured by every job.

The office, the scheduler, and every technician who has ever asked "which riser room?".

A building is an address on a job ticket. Its systems, its sections, its site contact and its last report are wherever the previous technician left them.

The building grid with search by name, customer or address, Metro and National Account filters, and an Add Building modal (name, customer, address). Import loads a spreadsheet. A building record mirrors the customer record: a header, stats (Systems, Assets, Active Jobs, Inspections Due), and pills for Overview, Sections (named areas such as North Wing or Basement Level 1), Activity, Systems (by type with asset counts and a Generate Inspection Form modal), Assets (filter by type, system and floor), Inventory, Jobs, Reports, Deficiencies, Svc Quotes, Quotes and Contacts, with Coverage, Documents and Defaults under More. Systems, assets and contacts each have an Import page.

• The building is the unit of inspection. Systems and assets are recorded once and every inspection form is generated from them.
• Sections give findings a place. A deficiency on "Basement Level 1" is findable by the next technician, and by the customer in the portal.
• Filters that match how the company works. Metro and National Account filters slice the estate the way routes and programmes are actually run.

The office keeping the device inventory straight, and the estimator who needs to know how many extinguishers a site really has.

The device count on the quote and the device count on the last report disagree, and nobody knows which is right. A recalled device model cannot be found across the estate.

Every asset across every building in one grid: search by address, customer, building, device type, floor or location, with an Asset Type filter and an Add Asset modal (system, address, asset type, floor, location). All Assets is the read-only cross-customer version with device type, sub type, system, building, customer and location.

• One inventory across the estate. Every device, every building, one search.
• Quotes and reports count the same devices. The asset list is what inspection forms are built from, so the count is the count.
• Find a model anywhere. Device type and sub type across every customer answers a recall or an end-of-life notice in one query.

The office, for the places that need service but are not buildings.

A fuel depot, a yard or a remote pump house is forced into the building model and then confuses every report that expects floors and sections.

A grid of service locations with search by name, customer, address or type, a Location Type filter, and an Add Location modal (name, customer, address, type). A location's dashboard shows its details (type, address, coordinates) and its contacts with roles.

• The right shape for the site. A location has a type, an address, coordinates and contacts, and nothing it does not need.
• Coordinates for routing. A location with a lat and long can be placed on a route like any building.
• Contacts with roles. The person to call at the site is on the record, with what they are responsible for.