Template population

A template population job fills a Spondyr correspondence template with data taken from a source record. When a triggering event arrives, such as a new account or a status change, a Beam agent reads the relevant record fields and applies the approved mapping rule that assigns each field to its placeholder in the chosen template. The agent renders the finished letter or notice and stores the output where account permissions allow. If a required field is empty, a value looks inconsistent, or no template matches the record type, the agent leaves the correspondence unrendered and routes the case to a person.

Distribution runs

Distribution covers moving a rendered piece of correspondence to its recipients through the channels Spondyr supports. Once a document is approved for release, a Beam agent reads the recipient details on the record, applies the account's sending rule, and passes the item to the connector for delivery. It then writes the delivery status back to the originating record so downstream steps can proceed. When a recipient address fails a format check, a delivery is rejected, or a send falls outside the approved rule, the agent holds the item and notifies the responsible team member for a decision.

Template library upkeep

The template library holds the reusable layouts that Spondyr populates for each correspondence type. A Beam agent watches for requests to add a new template reference or point a workflow at an updated version, then reads the current library entries and applies the approved rule for which template serves which record type. It records the mapping so later population jobs select the right layout on their own. Where a request would replace a template still tied to active workflows, or two versions could both apply, the agent pauses the change and asks a person to confirm the intended version.