How Actions Work
Actions are attached to specific pipeline stages. When a user is viewing an account, they see only the actions available for that account's current stage. Taking an action can optionally move the account to a different stage. For example:
An account is in the "Lead" stage.
The user takes the "Appointment Set" action.
The account moves to the "Set" stage.
Actions don't have to change the stage. You can create actions that record an interaction without moving the account forward — for example, a "Not Home" action on a "Lead" stage that keeps the account in "Lead."
Action Properties
Name — The display name of the action (e.g., "Pitched," "No Show," "Rescheduled").
Short Code — A short label for compact views.
Plural Name — The plural form for reports (e.g., "Pitches," "No Shows").
Description — An optional description of what this action represents.
Icon — A visual icon displayed on the action button. Supports emoji, Material icons, or your company logo.
From Stages — Which stages this action is available from. An action can be available from multiple stages.
Target Stage — The stage the account moves to when this action is taken. If left blank, the account stays in its current stage.
Schedule Appointment
Actions can be configured to automatically open the appointment scheduling flow after the action is taken. This is useful for actions like "Appointment Set" where the next step is always booking a time.
Conditions
Actions can have conditions that must be met before a user can take them. There are five condition types:
Action Count — Requires a previous action to have been taken a certain number of times. For example, "Pitched must have been taken at least 1 time" before a "Close" action becomes available.
Distance from Property — Requires the user to be within a certain distance (in meters) of the property. Useful for ensuring field reps are on-site before recording an outcome.
Distance from Action — Requires the user to be within a certain distance of where a previous action was taken.
Time Since — Requires a minimum amount of time to have passed since a previous action was taken. For example, a "Follow Up" action may only be available 24 hours after the initial pitch.
Time of Day — Restricts the action to a specific time window. For example, an action may only be available between 8:00 AM and 8:00 PM.
Checkpoints
Actions can have checkpoints configured per stage. A checkpoint is a confirmation step shown to the user before the action is completed. Checkpoint behavior options:
Always — Always show the checkpoint confirmation.
Ask — Prompt the user to confirm.
Never — Skip the checkpoint.
Role Restrictions
Actions can be restricted to specific roles. When role restrictions are set, only users with the specified roles can take the action.
Report Configuration
Actions can be configured to track metrics in reports:
Count — Count how many times this action has been taken.
Days Since — Track the number of days since this action was last taken.
Time of Day — Track what time of day this action is typically taken.
AI Configuration
Actions can optionally enable AI-powered conversation grading. When enabled, Terros can evaluate recorded conversations against configurable criteria and provide automated feedback.