How Pre-Actions Work
Pre-actions are attached to a workflow action through its pre-hook settings. When a user takes the action, Terros checks for any configured pre-actions first.
If pre-actions are set up, they run before the main workflow action is saved. Confirmed pre-actions are recorded every time they happen, so you can track repeated touches on the same account without flattening everything into a single stage.
For example:
A rep knocks on the same account three different times
Each knock can be counted as its own action in stats
The account can stay in the same stage while the history and stats still reflect every touch
That makes pre-actions useful for activity that happens repeatedly on one account, especially knocks and pitches.
Why Use Pre-Actions Instead of a Stage?
Stages are best for account state.
Pre-actions are best for activity count.
If you use stages to track repeated knocks or pitches, you usually end up with bad history or forced stage changes that do not really mean anything. Pre-actions solve that by keeping the stage where it belongs while still recording every interaction.
Pre-Action Properties
Each pre-action hook has a few core properties:
Action — The action that gets recorded if the pre-action is confirmed
Trigger — Whether the pre-action runs automatically or asks for confirmation
A single workflow action can have multiple pre-actions attached to it. They trigger in the order that you select.
Trigger Types
Pre-actions support two trigger behaviors:
Always — The pre-action is confirmed automatically
Ask — The user gets a quick Yes/No prompt before it is counted
You can mix both on the same workflow action. That gives you flexibility for cases where some tracking should happen every time, while other tracking should be confirmed by the rep.
If the user cancels a pre-action flow, all subsequent pre-actions are canceled too, but not the action that was originally selected.
Pre-Actions and Checkpoints
Pre-actions and checkpoints are not both configurable. If Pre-actions are enabled on your account, you will not be able to configure checkpoints. You can always use pre-actions to replace the job of checkpoints.
Best Use Cases
Pre-actions are a strong fit for:
Knocks
Pitches
Follow-up touches
Any repeated activity you want counted every time on the same account
They’re especially useful when a workflow action can happen more than once and you need accurate activity history without changing the account stage each time.
Reporting
Pre-actions feed into workflow history as separate confirmed activity records.
That means they can support cleaner reporting for repeated actions, since each confirmed pre-action is counted individually instead of being collapsed into a single stage change.
Enablement
If you would like to use pre-actions/pre-hooks in your workflow, reach out to Help and Feedback to have us enable the feature for your company. We are happy to help!