The Request Cycle workflow template in Chatavise automates follow-up communication when a request is created in Jobber. Whether the request comes from your website form or is created manually in Jobber, this workflow sends a series of text messages over several days to keep leads engaged — and automatically stops when the request is deleted or converted to a job.

This guide walks you through how to install the Request Cycle workflow, customize the messages and timing, assign tags to contacts, add team reminders, and understand how reaction triggers work to stop the workflow when needed.

What the Request Cycle Workflow Does

When a request is created in Jobber — either from a website request form or manually by your team — this workflow automatically begins a follow-up sequence designed to keep the lead engaged without manual effort.

By default, this workflow:

  • Listens for the Request Created event from Jobber
  • Sends an initial text message immediately after the request is created
  • Assigns tags to the contact for future filtering
  • Waits two days, then sends a follow-up message
  • Waits two more days, then sends a final follow-up
  • Creates a reminder for your team when automation has reached its limit
  • Stops automatically if the request is deleted or a job is created

How to Install the Workflow

  1. Navigate to your Jobber integration page in Chatavise.
  2. Locate the Request Cycle workflow template.
  3. Click Install.

The workflow is now installed but not yet active. This gives you a chance to review and customize it before turning it on.

Reviewing the Workflow Design

  1. Click on the newly installed workflow to open it.
  2. Select the Design tab to view the workflow structure.

You'll see the Request Created event as the trigger, followed by text message actions, tag assignments, delay steps, and a team reminder. If you want to learn more about how workflows function, click the Learn How To button inside the workflow editor.

Customizing the Initial Text Message

The first text message is sent immediately when a request is created. Since every business uses request forms differently, we recommend editing this message to reflect exactly what your business offers and why customers are filling out the form.

To edit the message:

  1. Click the Edit button on the first text message action.
  2. Modify the message text as needed.

The default message includes several message variables that pull data directly from Jobber:

  • Business name — your company name
  • First name — the customer's first name

You can add, remove, or rearrange these variables to match your preferred messaging style.

Assigning Tags to Contacts

The workflow includes a tag assignment action that helps you categorize contacts for future campaigns and filtering.

To configure tags:

  1. Click the Edit button on the tag assignment action.
  2. Add your desired tags — for example, "Web Lead" to indicate the contact originated from a request form.
  3. Click Save.

Every contact that enters this workflow will automatically receive the tags you configure, making it easy to segment leads later.

Adjusting the Delay Timing

By default, the workflow waits two days between each follow-up message. To change this:

  1. Click the delay action between messages.
  2. Adjust the timing — for example, one day, three days, or a specific number of hours.
  3. Click Save when you're done.

Customizing Follow-Up Messages

The workflow includes two follow-up text messages. We recommend editing these as well to match your business tone and the specific purpose of your request form.

If you don't want follow-up messages, you can remove them by clicking the Remove button on each action. However, follow-ups are a proven way to increase response rates from leads.

Adding a Team Reminder

At the end of the automated sequence, the workflow creates a reminder for your team. This ensures that if the lead hasn't responded after all automated messages, a team member is notified to follow up personally.

To configure the reminder:

  1. Click the Edit button on the reminder action.
  2. Enter a reminder title — for example, "Stale request — follow up needed."
  3. Assign the reminder to one or more team members.
  4. Click Save.

This handoff from automation to human follow-up helps ensure no lead falls through the cracks.

Understanding Reaction Triggers

The Request Cycle workflow includes reaction triggers that automatically stop the workflow when certain events occur in Jobber. This prevents customers from receiving follow-up messages after they've already taken action.

Request Deleted

When a request is deleted:

  • The workflow sends a message letting the customer know their request has been removed
  • The workflow stops — no further follow-ups are sent

Job Created

When a job is created from the request:

  • The workflow stops immediately — no further follow-ups are sent

These reaction triggers act as a circuit breaker, ensuring the automated sequence doesn't continue after the request has been resolved.

Tip: We recommend keeping these reaction triggers in place to avoid sending irrelevant messages to customers who have already responded or been converted to a job.

Activating the Workflow

Once you're satisfied with the message content, timing, tags, and reminders:

  1. Toggle the workflow On using the switch at the top of the workflow editor.
  2. The workflow is now live and will trigger automatically whenever a new request is created in Jobber.

Related Resources

Need Help?

If you have questions about configuring this workflow or need assistance with customization:

  • Click the Help button inside Chatavise
  • Contact the support team directly

The Chatavise team is happy to help you get your Jobber workflows running smoothly.