Skip to content

Product areasCRM

MOD-CRM-REG

Regions

  • Draft

Regions gives the customer a shared catalogue for its geographic groups and a policy for placing contacts and organizations within them. Staff maintain coverage, preserve deliberate exceptions and apply changed policy to existing records through recalculation. The planning layer distinguishes observed behavior from recorded product authority and remaining questions.

Features 4

A feature names and groups its key concepts, capabilities, journeys and acceptance test sets, and its acceptance suite when one is written. Open a feature to read them.

  1. FEAT-CRM-REG-01Regional CatalogueThe regional catalogue gives the customer a shared vocabulary for its chapters and territories. It groups the work of maintaining definitions, retiring them, authorizing changes and sharing the catalogue.1 concept5 capabilities1 journey5 acceptance sets
    • Draft
  2. FEAT-CRM-REG-02Geographic Assignment PolicyThe assignment policy brings the customer’s geographic coverage and placement choices together. It groups configuration, individual policy maintenance, matching and saved-address preview.1 concept5 capabilities1 journey5 acceptance sets
    • Draft
  3. FEAT-CRM-REG-03Record PlacementsRecord placements connect regional configuration with day-to-day contact and organization work. This feature groups address-driven updates and deliberate regional exceptions.1 concept2 capabilities2 journeys2 acceptance sets
    • Draft
  4. FEAT-CRM-REG-04Policy RecalculationRecalculation gives staff a controlled way to apply policy changes to existing records. This feature groups the need signal, processing and run monitoring.1 concept3 capabilities1 journey3 acceptance sets
    • Draft

Examination Reports 2

What was observed about this module on a date. Evidence, never product authority.

The Markdown files under specs/ in rhythmsoftware/rhythm-v2-docs are the canonical source of truth. This reader is a generated, read-only projection of them.