🥳 Celebrate Our Launch With a $200 LIFETIME Discount OFF The Premium Plan Use: BIRTHDAY2024

This offer expires 9/30/2024, at 11:59 PM EST

BizStackPro all-in-one digital marketing platform dashboard.
How To Create A Basic Campaign – BizStackPro Help

BizStackPro Campaign and Workflow Help Guide

How To Create A Basic Campaign

Build a simple legacy Campaign sequence for nurturing, onboarding, or follow-up while learning the structure you can apply to current BizStackPro Workflows.

Quick Answer

How do you create a basic campaign?

Open Campaigns, click Create Campaign, enter a name, and save it. Open Campaign Configuration to set delivery windows, users, Stop On Response, Allow Multiple, and any next-campaign behavior. Add events in the order they should run, configure each event’s relative timing, test the sequence, and change the status from Draft to Published.

How a Basic Campaign Works

A basic campaign is a sequence of events that run in a defined order after a contact enters the campaign.

Each event can send a message, create a manual task, place a voicemail step, or perform another available campaign action.

The timing of each event is normally based on the event before it. This creates a sequence that moves contacts through follow-up over minutes, hours, or days.

A clear campaign structure helps prevent messages from running in the wrong order, sending at unsuitable times, or continuing after the contact has already replied.

Campaigns are deprecated

BizStackPro’s legacy Campaigns feature has been replaced by Workflows. Use this guide when maintaining an older campaign or when translating a campaign sequence into a current Workflow.

Basic Campaign Setup at a Glance

Start Create Campaign
Settings Campaign Configuration
Message Timing Relative to Previous Event
Common Events Email, SMS, Voicemail, Manual
Testing Status Draft
Live Status Published

Before You Begin

Define the outcome and message sequence before opening the campaign builder.

  • Decide what should cause the contact to enter the campaign.
  • Choose one clear campaign outcome.
  • List the messages or actions in the order they should occur.
  • Decide how long the campaign should run.
  • Choose acceptable message delivery days and hours.
  • Decide whether contacts may enter more than once.
  • Decide whether a reply should stop later events.
  • Identify any users responsible for manual actions.
  • Prepare a test contact before publishing.

Common Uses for a Basic Campaign

Lead Nurturing

Welcome the lead, provide useful information, send a reminder, and present an appropriate next step or offer.

Customer Onboarding

Send confirmation, getting-started information, training resources, check-ins, and the next onboarding step.

Re-Engagement

Send follow-up messages over several days to contacts who have not recently responded or taken action.

Start with one simple outcome

A basic campaign is easier to test and manage when every event supports one clear purpose.

Step 1: Create the Campaign

Open Campaigns

Open Campaigns from the legacy Automation area.

Select Create Campaign

Click Create Campaign in the upper-right area.

Enter the Campaign Name

Use a name that explains the audience and intended outcome.

Examples:

  • New Lead – 7 Day Nurture
  • Customer Onboarding – Week 1

Save the Campaign

Click Save to create the campaign shell.

Step 2: Configure the Campaign Settings

Open Campaign Configuration and define how the campaign should behave.

Delivery Windows
Purpose: Controls when campaign messages and actions are allowed to run.
Example: Monday through Friday, 8:00 AM to 5:00 PM.
Users and Assignees
Purpose: Assigns team members for contact ownership or Manual Actions.
Next Campaign
Purpose: Determines where contacts should move after completing the current campaign when another campaign should follow.
Allow Multiple
Purpose: Controls whether the same contact may enter the campaign again.
Stop On Response
Purpose: Stops future campaign events after the contact replies.
Recommended for: Sales and conversational follow-up sequences.

Step 3: Add Campaign Events

Events are the individual messages or actions that make up the campaign sequence.

Select Add Event

Click + Add Event.

Choose the Event Type

Select the type of event you want to add.

Available options may include:

  • Email
  • SMS
  • Voicemail
  • Manual Action
  • Other available campaign events

Create the Message or Action

Add the email content, SMS message, voicemail details, Manual Action instructions, or other required event information.

Configure the Timing

Set how long BizStackPro should wait after the previous event before running this event.

Review Delivery Rules

Confirm that the event follows the intended delivery window and any other campaign restrictions.

Save the Event

Save the event and confirm that it appears in the correct position.

Repeat for the Remaining Events

Add each message or action in the order contacts should receive it.

Understand Relative Event Timing

Campaign event timing is relative to the event before it.

Example

If Event 2 has a wait time of 30 minutes, it runs 30 minutes after Event 1 completes.

This means each delay affects every later event in the sequence.

For example:

  1. Event 1 runs when the contact enters.
  2. Event 2 runs one day after Event 1.
  3. Event 3 runs two days after Event 2.

Event 3 therefore occurs approximately three days after Event 1, subject to delivery windows and other campaign settings.

Delivery windows can affect the final send time

When an event becomes due outside the permitted campaign window, its delivery may be delayed until the campaign is allowed to run.

Step 4: Test the Campaign

Test the campaign before changing its status to Published.

Keep the Campaign in Draft

Do not publish the campaign until the structure and event settings have been reviewed.

Use a Test Contact

Use contact information you control and can easily identify.

Shorten Timing for the Test

When practical, use shorter temporary delays so the sequence can be reviewed without waiting several days.

Review Every Event

Confirm the message content, links, custom values, sender information, timing, and delivery order.

Test Stop On Response

Reply as the test contact and confirm that later events stop when that setting is enabled.

Test Manual Actions

Confirm that Manual Actions appear for the correct assigned user.

Restore the Production Timing

Return temporary testing delays to the intended live schedule before publishing.

Step 5: Publish the Campaign

A Draft campaign does not run as a live campaign.

Review the Campaign Configuration

Confirm the delivery window, users, Allow Multiple setting, Stop On Response behavior, and next-campaign selection.

Review the Event Order

Confirm that the messages and actions appear in the intended sequence.

Review Event Timing

Confirm that each relative delay produces the intended overall campaign timeline.

Change Draft to Published

Change the campaign status from Draft to Published.

Confirm the Live Status

Verify that the campaign now shows as active or Published.

Publishing makes the campaign available to run

Complete the testing and final review before changing the campaign from Draft to Published.

Simple Campaign Examples

Lead Nurture

Welcome SMS → wait one day → value email → wait two days → reminder SMS → wait two days → offer email.

Customer Onboarding

Welcome email → wait one day → getting-started guide → wait three days → check-in message.

Use Stop On Response for conversational sales campaigns

When a lead reply should move the process from automation to a real conversation, enable Stop On Response so later sales messages do not continue unnecessarily.

Use Workflows for New Automation

Workflows are the current BizStackPro automation system and should be used for new automation builds.

The same planning principles still apply:

  • Define the entry trigger.
  • Choose one clear outcome.
  • Add actions in a logical order.
  • Set appropriate delays and sending windows.
  • Assign users when human follow-up is required.
  • Stop or branch the workflow when a contact responds.
  • Test the full path before publishing.

Preserve working legacy campaigns

Do not replace a functioning legacy Campaign without first documenting its events, timing, settings, assignments, and contact-entry behavior.

Basic Campaign Best Practices

Use an Outcome-Based Name
Reason: A descriptive name makes the campaign easier to understand and manage.
Action: Include the audience, outcome, or timeframe in the name.
Keep the First Campaign Simple
Reason: Too many events and settings make testing harder.
Action: Begin with a short sequence and expand only after it works.
Review Relative Timing Carefully
Reason: Each delay affects every event after it.
Action: Calculate the complete timeline from the contact’s entry.
Use Delivery Windows Purposefully
Reason: Delivery restrictions can delay an event beyond its nominal wait time.
Action: Test events that become due near the beginning or end of the allowed window.
Stop Sales Follow-Up After a Reply
Reason: Automated sales messages can become repetitive after the lead engages.
Action: Enable Stop On Response when a human conversation should take over.
Test Before Publishing
Reason: Draft review alone may not reveal timing, assignment, or delivery problems.
Action: Run a controlled test and restore all live settings before publishing.

Frequently Asked Questions

How do I create a campaign in the automation tool?
Click Create Campaign, enter a campaign name, then click Save. After that, configure settings, add events, and publish the campaign.
What settings can I configure for my campaign?
You can configure delivery windows, assign users, set what happens next after the campaign, and enable options like Stop on Response or Allow Multiple depending on your setup.
How do I add events to my campaign?
Click +Add Event, choose the event type such as email, SMS, voicemail, or another available action, then set timing and delivery rules. Events run in order and are timed relative to the previous event.
What should I consider when setting event timings?
Event timing is relative. A wait time of 30 minutes means the next event runs 30 minutes after the prior event completes.
How do I make my campaign active?
Change the campaign status from Draft to Published once you finish setup so it can run live.

Continue Learning

Continue learning how to configure campaign behavior, add human follow-up, and manage message timing.

Recommended Next Step

Build and Test One Short Campaign

Create a Draft campaign with two or three events, short temporary delays, and a test contact. Confirm the event order, message content, delivery window, user assignments, Stop On Response behavior, and total timeline before restoring the production delays and changing the campaign to Published.

Build Connected Follow-Up Systems with BizStackPro

BizStackPro connects workflows, email, SMS, conversations, tasks, contact records, pipelines, scheduling, and automated follow-up in one business platform.

Disclaimer: This site is NOT endorsed by Google, Facebook or YouTube in ANY WAY. All trademarks & Logo / branding are the property of their respective owners. Please Note: This site was created in BizStackPro by Ken George II (An Affiliate of BizStackPro) and may contain affiliate links.

All About BizStackpro


Copyrights 2024 | AllAboutBizStackPro.Com | Pricing | About | Features | All Rights Reserved.