Every capability, with its real status.

Customer records

The shared identity every other module attaches to.

• Customers

  Staging verified

  One customer record per person or business, owned by a Brand, referenced by every module rather than copied into each one.

• Contacts

  Available in staging

  Multiple people per customer with their own roles and contact details — the tenant who is home during the visit is not always the person who pays.

• Tags and segmentation

  Available in staging

  Brand-defined tags applied across customers and other records, usable as a filter.

• Notes

  Available in staging

  Notes attached to customers, properties, and jobs, with internal notes gated by staff capability so field-visible text and office-only text are not the same thing.

• Custom fields

  Available in staging

  Brand-defined typed fields on core records, so a business can capture what it actually tracks.

• Duplicate merge

  Planned

  Merging two records that turn out to be the same customer is not built yet.

Leads and intake

• Leads

  Staging verified

  Enquiries as first-class records with source, status, and conversion into a customer.

• Lead sources and lost reasons

  Available in staging

  Brand-defined vocabularies, so where work comes from and why it is lost are reportable rather than free text.

• Lead activity

  Available in staging

  A dated trail of what happened on a lead, kept after conversion.

• Public intake forms

  Staging verified

  Brand-defined public forms on the Brand's own host that create a lead with its source page recorded. Validated and rate limited server-side.

Communication and history

• Email

  Available in staging

  Outbound customer email through the platform's configured provider, recorded against the customer.

• Message templates

  Available in staging

  Brand-defined reusable message bodies rather than staff retyping the same note.

• Threads and participants

  Available in staging

  Conversations tied to a customer and, where relevant, to a job — with who was on them.

• SMS and voice

  Provider integration required

  The channel adapters exist and refuse to transmit until a provider is connected and approved. They record a suppressed delivery and say why rather than reporting a success that never happened.

• Activity timeline

  Foundation only

  Events are recorded per record; a single unified customer timeline screen is still being built.

Automation, reporting and data

• Typed automations

  Available in staging

  Trigger and action pairs defined per Brand, with a recorded run per execution so an automation that misfires is auditable.

• Reporting metrics

  Available in staging

  Computed metric snapshots over customer, lead, and work data, recomputable on demand.

• Exports

  Available in staging

  Dataset exports scoped to the requesting Brand.

• Imports

  Available in staging

  Batch import with per-row results, so a partial failure tells you which rows and why.

• Audit trail

  Staging verified

  Privileged actions are recorded through one audit path across the platform.