Variable-Driven Document Templates

Crove templates hold placeholders for details that change from one document to the next, such as a client name, price, or date, so the same layout can be reused. A Beam agent triggers when a new deal or client record is ready, reads the relevant data, and applies the customer's approved template to fill those variables and assemble the document. Where a variable is missing, blank, or falls outside the expected format, the agent stops before finishing the document and sends the record to a person to complete first.

Conditional Clause Logic

Crove templates can include or leave out whole clauses depending on conditions a customer sets, such as a different payment term for a certain deal size or region. A Beam agent reads the relevant details on a case and applies the customer's approved conditions to decide which clauses belong in the document being assembled. Where a case doesn't clearly meet or fail a condition, or two conditions conflict with each other, the agent leaves the clause choice unresolved and sends it to a person to decide before the document is finished.

Document Filing and Notification

Once a document is assembled in Crove, it usually needs to be stored against the right client or deal, and someone on the team needs to know it's ready. A Beam agent applies the customer's approved filing rule to store the finished document against its record and notifies the person who originally requested it. Where the document is unusually long, missing an expected section, or tied to a record the filing rule doesn't cover, the agent holds it back and flags it for a person to check first.