Nabu
Growth

Growth Overview

What Growth is, why it exists, and how the pieces fit together.

What Growth is

Growth is Nabu's follow-up system. It watches the activity already flowing through your booking system (completed visits, quotes given during consultations, cancellations, open appointment slots) and turns the ones worth a phone call, text, or email into a task for your team to work.

It lives at Growth in the left sidebar.

Before Growth, a spa's revenue depended on someone remembering to follow up: the front desk noticing a client hadn't rebooked, a provider remembering who was quoted last month, a manager combing through cancellations at the end of the week. That work doesn't scale past a handful of clients, and it's the first thing that gets skipped on a busy day. Growth exists to catch those moments automatically so nothing falls through because nobody had time to check.

Key concepts

An opportunity is the underlying reason a client is worth contacting: a completed visit that's due for a follow-up, an unconverted quote, a cancellation with no rebooking, and so on. A task is the specific piece of work your team does about that opportunity. Most of the time there's one task per opportunity, but the two are tracked separately on purpose: recording an outcome on the task ("client booked," "client declined") is what actually closes the opportunity, not just marking the task as done. See Task Status and Lifecycle for exactly how that works.

Workflows are the five kinds of opportunity Growth looks for: post-visit follow-up, quote follow-up, no future booking, cancelled and not rebooked, and open-slot outreach. Each one has its own trigger, timing, default owner, and channel, all covered in The Five Workflows.

Execution mode describes how much of the work Nabu does versus a person. A task can be a manual task a staff member handles start to finish, a review-required task where Nabu drafts something and a person checks it before it goes out, or an automated task Nabu sends on its own. Automated is never shown as a role. If you see "Generated by Nabu" on a task, that's the automation label; a real role (Front Desk, Provider, Manager) is still attached underneath in case it ever needs to be handed to a person.

Claiming lets one team member take ownership of a role-assigned task before working it, so two people don't both call the same client. Nabu prevents two people from claiming the same task at once.

Do-not-contact is enforced everywhere in Growth. If a client has an active do-not-contact flag, no task will suggest calling, texting, or emailing them, no matter what workflow generated it.

Where to go next

On this page