What SAM schedules
Activities before or after a key date, from the start of a Routine, or on a month and day. Offsets can use days or business days. Confirm the account calendar before you rely on a holiday.
Business Plans
SAM does not ask you to adopt a national script. It gives you places to put the dates, the owners, the checks, and the consequences you already believe in.
The educational name for the way you work. It is not a SAM record type and it is not a pricing tier.
One record type, one scheduling anchor, conditions, and repeat or stop rules you set.
A scheduled step: when it happens, what kind of work it is, and who owns it.
A Checklist verifies. An Action is a configured consequence, such as a message, call-list entry, or field update.
Related Routines for one record type, such as several listing dates you want to manage together.
A cross-record story, such as listing to transaction to past client. Handoffs are descriptive. They do not create the next record or start the next Workflow.
The way you already serve a seller, a buyer, or a past client, written down so someone else could follow it.
Listing launch is the plan. It may use more than one Routine if the appointment date and the go-live date move separately.
A playbook tied to one kind of record and one scheduling anchor.
A transaction Routine anchored to closing, with rules for when it starts or stops.
One scheduled piece of work with a time and an owner.
A walkthrough the day before closing, assigned to the buyer agent.
The question "is this actually done?" attached to that work.
A file check for the executed contract, or a field check that the closing date is filled in.
The consequence you allow when the Activity runs.
A template message, a call-list entry, a notification, or a field update.
Activities before or after a key date, from the start of a Routine, or on a month and day. Offsets can use days or business days. Confirm the account calendar before you rely on a holiday.
Checklist items for a field, a tagged file, a URL, a party member, a connection, or a simple completed step.
Supported Actions such as a template message, a call-list entry, a notification, a field update, or an integration you have connected.
The objective, the steps, the send, and the moment a Routine becomes active. A website example approves nothing.
A Routine organizes Activities around one anchor on one type of record. A Workflow groups related Routines for that same record type so you can see the larger process. A Journey can describe how a listing process hands off to a transaction and later to retention. The handoff names the event and the person responsible. It does not create the downstream record, and it does not launch the next Workflow.
Timing options include an offset from the key date, an offset from when the Routine started, a month and day, business-day units, and a setting to skip Activities that would already be past due when a run begins. Weekend and holiday behavior follows the business calendar configured for the account. This page does not promise that every holiday is skipped.
Use a new Routine when the work has a different scheduling anchor or a different record type. Activities that share one anchor belong together. A Workflow can group the Routines that belong to one record.
Activities anchored to that closing date. Work anchored to the contract date, to the start of the Routine, or to a month and day stays where it is. SAM does not invent a new contractual deadline.
The assignee you configure: yourself, another eligible user, or a role your account can assign. Ownership is part of the setup. It is not guessed from the job title in this example.
Pricing, consent, inspection negotiations, wire checks, and any message you are not willing to send from a template. A Checklist can show evidence. It does not make the decision.
Only if you configured a message Action, with a template and channel, and your review rules allow it. Exploring a page or copying a brief does not send anything.
No. These pages are illustrations. Creating a Routine happens in SAM, or through a connected assistant after you confirm the save.
Bring one listing or one closing. We can separate the anchor, the checks, and the messages that should wait.