{"type":"video","version":"1.0","html":"<iframe src=\"https://www.loom.com/embed/603e6454cd894be28a77470a134e4194\" frameborder=\"0\" width=\"1778\" height=\"1333\" webkitallowfullscreen mozallowfullscreen allowfullscreen></iframe>","height":1333,"width":1778,"provider_name":"Loom","provider_url":"https://www.loom.com","thumbnail_height":1333,"thumbnail_width":1778,"thumbnail_url":"https://cdn.loom.com/sessions/thumbnails/603e6454cd894be28a77470a134e4194-765edea6fbbfad24.gif","duration":578.417,"title":"Breaking down how an Automation works in Chariot","description":"This Loom explains the anatomy of an automation in Chariot, using a blueprint example of messaging a customer when the move date is 3 days away and the job is still not done. It covers four parts: when the automation enrolls leads or jobs (for example, when a lead is created), enrollment conditions (such as residential, distance, tags, timing, and deposit or stage-related events), restart conditions (like restarting when job time changes after a customer delays a move), and steps/actions (such as sending an email and text). The Loom also distinguishes action conditions to prevent reminders in cases like when a job is booked or when a lead was created less than a day ago. It emphasizes that viewers do not need to be expert because blueprints and support are available."}