> ## Documentation Index
> Fetch the complete documentation index at: https://help.propexa.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Suggestion Types

> Understand the property, contact, and relationship improvements Propexa can suggest in Rex CRM.

Propexa checks Rex CRM records for clear opportunities to improve formatting,
remove stale details, and restore missing property relationships. Each
suggestion contains a proposed change. Depending on your workspace workflow,
an eligible suggestion can be applied automatically or made available for
review in **Queue**.

Propexa considers the available record context and only makes a suggestion when
the evidence is strong enough. Ambiguous or incomplete records are left
unchanged.

<Info>
  The examples below are representative. The suggestion you see will reflect
  the information available in each record.
</Info>

## Property details

### Property street expansion

Expands a recognised Australian street-type abbreviation at the end of a
property's street name. It can also remove a suburb, state, and postcode that
were accidentally included in that field. A leading `St` is preserved when it
belongs to a place or saint name.

Propexa leaves complex building names, commas, and quoted text alone when a safe
change is not clear.

| Before        | Suggested change  |
| ------------- | ----------------- |
| `St John St`  | `St John Street`  |
| `Gregory Tce` | `Gregory Terrace` |

### Property suburb casing

Standardises capitalisation and extra spacing in the property's suburb or
locality. Hyphenated and slash-separated names are supported, and no other part
of the address is changed.

| Before               | Suggested change     |
| -------------------- | -------------------- |
| `new farm`           | `New Farm`           |
| `mount gravatt-east` | `Mount Gravatt-East` |

### Property address format

Repairs safe formatting problems across the separate property-address fields.
For example, a street-number suffix that has been split into the street-name
field can be moved back to the street number. Propexa can also handle other
clear address casing or structure issues.

The existing Rex address fields remain separate, and Propexa does not invent
address parts when the available information is insufficient.

| Before                                               | Suggested change                                    |
| ---------------------------------------------------- | --------------------------------------------------- |
| Street number `1` and street name `B Example Street` | Street number `1B` and street name `Example Street` |
| Street number `2` and street name `a Example Street` | Street number `2A` and street name `Example Street` |

## Contact details

### Contact address format

Converts a clear physical or postal address into a consistent multiline postal layout. It also infers missing data, like state or postcode, from an address based on record context. Allowing Propexa to automatically link contacts to properties.

| Before                                  | Suggested change                                   |
| --------------------------------------- | -------------------------------------------------- |
| `unit 1 2 example rd new farm qld 4005` | `1/2 Example Road`<br />`New Farm`<br />`QLD 4005` |
| `po box 1 brisbane qld 4000`            | `PO Box 1`<br />`Brisbane`<br />`QLD 4000`         |
| `55 oxlade drive new farm`              | `55 Oxlade Drive`<br />`New Farm`<br />`QLD 4005`  |

### Past owner address clear

When a contact is linked as a Past Owner, Propexa compares their current
physical and postal addresses with that former property. If an address matches,
it suggests clearing the stale contact address. When both fields match, they
can be cleared together instead of also suggesting a formatting change.

| Before                                                       | Suggested change              |
| ------------------------------------------------------------ | ----------------------------- |
| Physical address matches a property linked as Past Owner     | Clear the physical address    |
| Physical and postal addresses both match the former property | Clear both addresses together |

### Contact email invalid cleanup

Reviews email entries that Rex marks as invalid. Obvious punctuation, spacing,
and common provider-domain errors can be repaired. Propexa can also split
multiple email addresses or move a phone number that was pasted into an email
entry into the contact's phone numbers.

| Before                             | Suggested change                                                |
| ---------------------------------- | --------------------------------------------------------------- |
| `jane.citizen @example.com`        | `jane.citizen@example.com`                                      |
| Invalid email entry `0404 123 456` | Remove it from emails and add `0404 123 456` as a mobile number |

### Contact email name link

Links an unassigned, valid email entry to the right existing person on a
multi-person contact when its description or address contains a clear first- or
full-name signal. Less obvious matches are only suggested when the available
evidence is still strong.

| Before                                               | Suggested change               |
| ---------------------------------------------------- | ------------------------------ |
| Email description `Jane`, address `jane@example.com` | Link the email to Jane Citizen |
| `john.citizen@example.com`                           | Link the email to John Citizen |

### Contact phone number format

Standardises recognised Australian mobile and landline numbers, including
international `+61` forms, without changing the phone type. If a clear person
label or initial appears with a number, Propexa can remove the label and link
that phone entry to the matching existing person.

Labels are preserved when they do not match one person clearly.

| Before                | Suggested change                       |
| --------------------- | -------------------------------------- |
| `+61 404 123 456`     | `0404 123 456`                         |
| `0404 123 456 (Jane)` | `0404 123 456`, linked to Jane Citizen |

### Contact name duplicate clean up

Removes a clearly repeated first name or a duplicated full name embedded in the
surname, then standardises the repaired name. Legitimate short repeated names are protected.

| Before                                           | Suggested change |
| ------------------------------------------------ | ---------------- |
| First name `JaneJane`, surname `citizen`         | `Jane Citizen`   |
| First name `Jane`, surname `CitizenJane Citizen` | `Jane Citizen`   |

### Contact name casing

Standardises simple uppercase or lowercase person-name parts, including common
hyphens and apostrophes, while preserving initials and recognised mixed-case
forms. It can also repair a small number of clear punctuation issues and more
complex names when the correct change is clear.

| Before                              | Suggested change |
| ----------------------------------- | ---------------- |
| `JANE JP O'NEIL`                    | `Jane JP O'Neil` |
| First name `jane`, surname `obrien` | `Jane O'Brien`   |

### Contact name split

Turns one primary name containing two people joined by “and” or “&” into two
person-name entries in Rex, preserving surnames and middle names where the
structure is clear. More complex punctuation is handled only when the intended
names are clear.

Names with important metadata or an ambiguous structure are left unchanged.

| Before                                                         | Suggested change                       |
| -------------------------------------------------------------- | -------------------------------------- |
| First name `Jane`, surname `Citizen and John Citizen`          | Jane Citizen + John Citizen            |
| First name `Jane`, surname `Mary Citizen & John James Citizen` | Jane Mary Citizen + John James Citizen |

## Property relationships

### Listing owner missing property owner

When a person is an owner on a current or otherwise non-sold listing but has no
relationship to that property, Propexa suggests adding an Owner relationship.
If any relationship between that contact and property already exists, no new
relationship is suggested.

| Before                                                       | Suggested change |
| ------------------------------------------------------------ | ---------------- |
| Current listing owner with no relationship to the property   | Add Owner        |
| Current listing owner with an existing property relationship | No suggestion    |

### Sold listing owner missing past owner

When a person is an owner on a sold listing but is not linked to its property as
a Past Owner, Propexa suggests adding that relationship. If the same
contact-property relationship has another type, Propexa can suggest changing it
to Past Owner.

| Before                                           | Suggested change           |
| ------------------------------------------------ | -------------------------- |
| Sold-listing owner with no property relationship | Add Past Owner             |
| Sold-listing owner linked as Owner               | Change Owner to Past Owner |

### Contact address matches property owner

Uses a contact's physical address to look for an exact property match in Rex.
An Owner relationship is suggested only when exactly one property matches and
the contact is not already linked as its owner. If that contact and exact
property have a different relationship, Propexa can suggest changing it to
Owner. A postal address by itself is not used as evidence of ownership.

| Before                                                                                                                           | Suggested change |
| -------------------------------------------------------------------------------------------------------------------------------- | ---------------- |
| Physical address `1/2 Example Road`<br />`New Farm`<br />`QLD 4005` exactly matches one Rex property, with no Owner relationship | Add Owner        |
| The exact matching property is already linked as Owner                                                                           | No suggestion    |