Where to start
Admin Area → Property Management Flow → Zero-Chase
Before you begin
A rule combines a trigger, optional conditions, actions, a cooldown and a review policy. Start with a narrow scope and human approval enabled.
Follow these steps
- Choose New rule and enter a recognisable Rule name.
- Select the trigger and only the thresholds or filters relevant to that trigger.
- Select initial actions and, if needed, a delayed escalation action.
- Keep Require human approval enabled; leave Activate immediately off while preparing the rule.
- Save rule, then choose Preview from the rule library.
- Check the candidate properties, entity IDs and reasons before enabling the rule.
Check the result
Preview shows matching records without executing actions. The saved rule states the intended trigger, filters and review policy.
If something does not look right
Filters can remove every candidate. Check property scope and permissions first. The current builder creates rules; the library exposes Preview and Enable/Disable, not a general edit/delete control.
Questions and answers
Which actions are supported?
Timeline entry, staff notification, landlord email, tenant email, supplier email and task creation. Remedial repair creation is a separate Compliance Autopilot action.
What are the limits?
Cooldown is 60–43,200 minutes; days input is 1–365; hours input is 1–720; attempts are 1–10. Trigger-specific behaviour is explained in the trigger guide.
Are starter rules live immediately?
Seeded rules are disabled and review-first. Enabling a rule must be a deliberate operating decision.
Related technical reference: Britixo's detailed product guide (opens in a new tab). The screens available to you depend on your configured modules, company and permissions.
Useful next steps
- Choose the right Zero-Chase trigger and threshold
- Approve, reject and evaluate automation work
- Investigate automation recipients, failures and retries
Contact the Proplix team if you need help with your setup. Include the page or record reference and a description of the issue; leave passwords and private access tokens out of the message.