How automated outreach batches are built and who they go to
Automated Outreach goes out in batches. When recurring services come due and their automation is set to Automated Outreach, Essential builds the outreach per contact: it gathers that contact's due recurring services and combines the ones whose due dates fall close together (within the business's outreach batch window) into a single batch, so the customer gets one message covering several due services instead of a separate message for each.
A batch ties one contact to the recurring service schedule(s) it covers, and it runs as those services come due. Who a batch goes to is decided by contact role: Essential uses the property's approvals contact first, and if there isn't one it falls back in order to the scheduling, then onsite, then billing contact.
Within a role it prefers a property-level contact over a customer-level (account-wide) one, and a primary contact over a secondary one. If no contact holds any of these roles for the property, the automation can't send - that's the "Add a contact role to this property to enable outreach" blocker.
Where to find it: Built automatically from due recurring services; the recipient and timing show on the asset group's Next Automation card and on the Automated Outreach page
Related guides
Last updated
Was this helpful?