Personalized Automations & Trial Governance
Create record-aware follow-ups and operate a focused, safe practice org.
Open interactive lesson and quizWhat you will learn
- Personalize tasks from the triggering record
- Choose live targeting or stored audience snapshots
- Understand relationship and Trial email limits
A team wants each newly created contact to receive a named follow-up task, while learners practise marketing safely without filling their org with unnecessary sample data.
Lesson 1
Use record fields instead of hard-coded task names
The triggering record supplies values for task titles, task descriptions and follow-up draft subjects and bodies. For example, Follow up with {{Contact.Name}} becomes Follow up with Priya Sen when that contact starts the automation. Use Insert Name in the task action or a token for a field already present on the triggering record. {{Name}} and {{Record.Name}} are convenient aliases; the object-qualified form makes the origin explicit.
Use a fallback for optional text, such as {{Contact.FirstName | Customer}}. Blank values must not stop task creation. Tokens are value substitutions, not formulas or executable code. They cannot fetch a record from another BU or read arbitrary related objects. A Company token in a Contact automation only resolves when that value exists on the triggering Contact. Review the execution history and generated task using both complete and partially filled sample records.
Lesson 2
Keep the practice org focused
New Trial orgs contain 25 companies, 50 contacts, 40 deals, 50 tasks, 30 products, 30 service cases and 12 campaigns, with linked deal lines and campaign outcomes. Two contacts share each sample company so learners can practise account relationships and segmentation without hundreds of unnecessary records. Synthetic email addresses are deliberately excluded from marketing delivery.
Older Trial data is compacted carefully: unchanged generated samples can be reduced, but edited samples and samples referenced by customer-created records are retained. This means an established Trial may contain more than the baseline, by design. Practice with addresses you control and keep real confidential information out of demonstration records. The Trial lasts 30 days; a recurring flow does not extend its expiry.
Lesson 3
Work within clear relationship and send limits
An object can have up to 10 configured outgoing relationships. Existing built-in CRM relationships are not removed, and existing configurations above the limit are retained; adding another configured relationship requires room. An audience can traverse up to three related objects. Use clear labels and avoid duplicate lookups that express the same business connection.
Trial marketing allows 100 email delivery attempts per UTC day and 500 over the entire Trial, including test sends. Provider retries of the same delivery do not consume another slot. Up to 10 non-archived email designs and five unfinished Send Flows are allowed, with three running, scheduled or paused at once. Archive unused emails and stop or finish flows to free their slots. Daily limits delay processing; exhausting the total allowance pauses sending. Essential account-provisioning emails are separate. Paid editions do not inherit these new Trial-specific limits.
Practice · Create a record-aware task
- Create an automation with Contact created → Create task.
- Set the title to Follow up with {{Contact.Name}} using Insert Name. Assign it to the record owner.
- Create a contact called Priya Sen and check the generated task title.
- Build an audience with selected columns and, if permitted, save an independent custom-object snapshot.
- Check Trial limits before activating a follow-up flow.