Set Up a Platinum Call Count Automation
How to Set Up a Platinum Call Board and Automatically Increment Call Counts
A Platinum call board should do more than organize contacts for dialing. Every completed call attempt should also create a reliable activity record by updating the last-call date, increasing the contact’s call count, and preserving the selected disposition.
This requires the call board and the CRM workflow to work together. Each disposition must apply a temporary trigger tag. That tag launches a reusable workflow, the workflow updates the date and count, and then the tag is removed so the next call can trigger the process again.
Watch the Training Video
Use the video for the on-screen setup. The written procedure below explains the logic, configuration, and testing standard staff should follow.
What the Finished System Should Do
Whenever a caller selects a valid disposition from the Platinum call board, the system should:
Record the selected disposition.
Apply the temporary Tool WAVV Call Count tag.
Trigger the call-count workflow.
Update the contact’s last-call date.
Increase the call-count field by one.
Remove the temporary trigger tag.
Allow the same process to run again after the next call.
The temporary tag is the key to making the counter reusable.
Why the Original Disposition-Tag Method Fails
A normal disposition tag, such as WAVV No Answer or WAVV Left Voicemail, is intended to remain on the contact as useful history. That creates a problem if the call-count workflow uses the permanent disposition tag as its trigger.
The first time WAVV No Answer is added, the workflow may run correctly. The next time the caller selects No Answer, the tag is already present. Because it is not being newly added, the workflow does not trigger again.
Removing the permanent disposition tag is not the right solution. Staff may need to know that a contact previously had no answer, received a voicemail, had a bad number, or produced another outcome.
The correct design separates two functions:
Permanent disposition tag: Preserves what happened.
Temporary call-count tag: Triggers the reusable counter workflow and is then removed.
Part 1: Confirm the Required CRM Fields
Before configuring the call board, confirm that the contact record contains the fields the workflow will update.
At minimum, the system needs:
A Last Call or WAVV Last Call date field
A numeric Call Count or WAVV Call Count field
The count field must support a mathematical increment operation. Confirm that it is configured as the correct numeric field type before building the workflow.
Part 2: Create or Confirm the Temporary Trigger Tag
Create or locate the tag:
Tool WAVV Call Count
Use the exact approved spelling throughout the call board and workflow. A nearly identical tag with different spacing, capitalization, or wording will not trigger the intended automation.
This is an operational tool tag. It should not remain permanently attached to the contact.
Part 3: Set Up the Platinum Call Board
Open the WAVV dialer and select the Platinum call board.
Open the call board’s Settings.
Go to Automations or the disposition-automation area.
Review every disposition available to the caller.
Confirm that each meaningful call outcome has its own disposition configuration.
Common dispositions may include:
No Answer
Left Voicemail
Appointment Set
Not Interested
Bad Number
Disconnected
Call Back
Contacted Today
The exact dispositions may vary. The important rule is that every disposition representing a completed call attempt must participate in the call-count process.
Part 4: Configure Each Disposition
Each disposition should perform two functions:
Apply or preserve the disposition-specific tag.
Apply Tool WAVV Call Count.
For example, the No Answer disposition should:
Add WAVV No Answer
Add Tool WAVV Call Count
The Appointment Set disposition should preserve its appointment-related action and also add Tool WAVV Call Count.
The Not Interested disposition should preserve the not-interested outcome and also add Tool WAVV Call Count.
The Bad Number disposition should apply its outcome tag, add Tool WAVV Call Count, and then perform any required removal from call boards.
Action order matters
When a disposition also removes the contact from a board, perform the tracking actions first:
Add the disposition tag.
Add Tool WAVV Call Count.
Perform other required actions.
Remove the contact from the applicable call board or all boards.
This keeps the tracking action from being skipped when the contact exits the board.
Part 5: Include the Disposition Across All Applicable Stages
A contact may be called from different stages of the Platinum board. If the No Answer disposition is configured for only one stage, calls made from another stage may not increment properly.
Review every stage where the disposition can be selected and include the required setup in each one.
Do not assume that configuring No Answer once automatically covers every board stage. Verify the complete stage list individually.
Part 6: Configure the Reusable Call-Count Workflow
Open the applicable workflow, such as WAVV Update Last Call, within the Platinum or call-pipeline automation folder.
Replace permanent disposition triggers
Remove the collection of permanent disposition-tag triggers from the workflow. The workflow should not depend on tags such as No Answer, Left Voicemail, Appointment Set, or Not Interested being newly added.
Create one trigger:
Trigger type: Contact Tag
Condition: Tag Added
Tag: Tool WAVV Call Count
Open the saved trigger again and verify that the selected tag is correct.
Allow multiple workflow runs
Enable the workflow option that permits a contact to enter or run the workflow multiple times.
This setting is essential. Even though the temporary tag is removed, a workflow restricted to one entry per contact will still prevent future calls from being counted.
Part 7: Configure the Workflow Actions
The workflow should perform these actions in order:
Update the last-call date to the current call date or current date/time, according to the approved field design.
Perform a math operation that increases the call-count field by one.
Remove the Tool WAVV Call Count tag.
The final removal resets the trigger condition. When a disposition applies the temporary tag after the next call, it is genuinely being added again and the workflow can run again.
Do not remove the permanent disposition tag as part of this workflow.
The Complete Automation Flow
The intended sequence is:
Caller selects disposition → Save disposition tag → Add Tool WAVV Call Count → Run workflow → Update last-call date → Increase call count by one → Remove temporary tag
This design preserves the outcome while creating a fresh trigger for every future call.
Part 8: Audit Every Disposition
Return to the Platinum call board and inspect each disposition one at a time.
Confirm that:
The correct permanent outcome tag or action is present.
Tool WAVV Call Count is added.
Any board-removal action occurs after the tracking actions.
The disposition exists in every applicable call stage.
Do not stop after checking the most common dispositions. A single missing call-count action will cause reporting gaps whenever callers use that outcome.
Part 9: Test the Setup
Use a designated test contact rather than a live client lead.
First test
Record the test contact’s current call count.
Record the current last-call value.
Place or simulate a call from the Platinum board.
Select No Answer.
Wait for the automation to process.
Refresh the contact record.
Confirm that:
The WAVV No Answer disposition tag is present.
The call count increased by exactly one.
The last-call field updated.
Tool WAVV Call Count was removed after processing.
Repeat-run test
The repeat test proves that the solution actually works.
Note the new call count.
Run a second test call or disposition on the same contact.
Select No Answer again or another configured disposition.
Refresh the contact after the workflow processes.
Confirm that the call count increased by one again. If the first call counts but the second does not, check whether:
Multiple workflow runs are disabled.
The temporary tag was not removed.
The disposition did not add the temporary tag.
The wrong tag was selected in the workflow trigger.
Cross-disposition test
Test at least one disposition that keeps the contact on the board and one that removes the contact, such as Bad Number. Confirm that both increment the count before any board-removal action takes effect.
Troubleshooting Guide
The first call counts, but later calls do not
Likely causes:
The workflow is triggered by a permanent disposition tag.
Multiple workflow runs are not enabled.
The temporary trigger tag is not being removed.
One disposition does not increment the count
Likely causes:
That disposition does not add Tool WAVV Call Count.
The action is missing from one or more call-board stages.
The contact is removed from the board before the call-count tag is applied.
The workflow never runs
Check:
The exact tag selected in the workflow trigger
Whether the workflow is published and active
Whether the disposition actually adds the tag
Whether the test contact qualifies for the workflow
The count increases more than once per call
Check for:
Duplicate actions adding the temporary tag
Multiple workflows triggered by the same tag
Duplicate triggers inside the workflow
More than one disposition automation firing for the same click
The last-call date changes but the count does not
Review the math action and confirm that it targets the correct numeric call-count field and adds exactly one.
Common Mistakes to Avoid
Using permanent disposition tags as repeatable workflow triggers.
Removing disposition tags that should remain as contact history.
Forgetting to enable multiple workflow runs.
Forgetting to remove the temporary trigger tag at the end.
Adding the call-count action to some dispositions but not all.
Configuring a disposition in one stage while missing it in other stages.
Removing a contact from all boards before applying the tracking tag.
Selecting a similarly named but incorrect tag.
Testing only the first workflow run.
Testing only one disposition.
Making changes directly on a live lead without first using a test contact.
Final Setup Checklist
Before releasing the Platinum call board to callers, confirm:
The last-call field exists and is the correct field type.
The call-count field exists and supports math operations.
The Tool WAVV Call Count tag exists with the approved spelling.
Every qualifying disposition applies the temporary tag.
Every disposition preserves its correct outcome tag or action.
Dispositions are configured across all applicable board stages.
Tracking actions occur before removal from call boards.
The workflow trigger is Tag Added: Tool WAVV Call Count.
Permanent disposition tags are not used as the workflow’s repeat trigger.
Multiple workflow runs are enabled.
The workflow updates the last-call field.
The workflow increments the call-count field by exactly one.
The workflow removes the temporary tag after processing.
A first-call test passed.
A repeat-call test on the same contact passed.
At least two different dispositions were tested.
The workflow is active and published.
Final Takeaway
The Platinum call-count system works when permanent history and repeatable automation are kept separate.
Disposition tags document what happened during the call. The temporary Tool WAVV Call Count tag tells the system that one new call attempt occurred. The workflow updates the date and count, removes the temporary tag, and becomes ready for the next attempt.
Once every disposition and stage follows that pattern, staff should be able to select any valid call outcome and see the last-call date change and the call count increase every time.
