Group (agent) Subscriptions

A group (agent) Subscription delivers documents to a group (business) Mailbox: a single account that can receive and manage documents for many properties or accounts in one place. It's commonly used by real estate agents and property managers who receive notices for the properties they act for, but it's also used by organisations that receive their own documents in volume and want the bulk tools a group Mailbox offers.

A group Mailbox behaves like any other Mailbox subscription. The difference is the account type, which unlocks bulk registration and download tools.

How a group subscription works

• The agent registers once, using a verified email address (for example an agency email).
• Accounts whose Contact details match are linked to the group Mailbox, so their notices all arrive in one place. This is keyed off a Group Code (also called a Notice ID), which ties an account's documents to the agent.

Keeping a group subscription up to date

An agent's Subscriptions can be kept current in one of two ways:

• Self-managed: the agent maintains their own Subscriptions, adding newly managed properties and removing ones they no longer manage as their portfolio changes.
• Mailer-managed: you keep the agent's Subscriptions current for them, once the agent has authorised it. Because it's keyed off the Group Code, updating your Contacts then keeps the agent's Subscriptions in step with your records automatically. See Understanding Agent Authorisations for how to set this up, and How Contact changes affect Subscriptions for how the automatic updates flow through.

When ownership or the managing agent changes

If a property's owner or managing agent changes, the affected Subscriptions are flagged for your review in the Deregister? view, so documents aren't sent to the wrong recipient. See Managing "Deregister?" Subscriptions.

Third-party property systems

Integrations such as PropertyMe and other property-management systems can affect how these Subscriptions behave. If your customers use one, confirm how it interacts with Payreq before relying on the standard behaviour above.