Onboarding Blueprints let you build your ideal client setup once, then reuse it for every new customer. Instead of manually creating the same forms, campaigns, widgets, responders, and prompts over and over, you turn them into a package the platform can apply for you.
Think of it like a repeatable client playbook. You decide what a new location should look like, and the platform builds that setup out when the customer is ready.
What onboarding blueprints are
Onboarding Blueprints are package-based setup templates for new customer locations. You create the setup once, then let the platform repeat it for future locations automatically or apply it manually to existing customers.
When a customer connects a review source such as Google or Facebook, the package can kick in and create the matching resources for that location in the background.
Where to find it
Go to `Settings`, then click `Onboarding Blueprint` in the left sidebar. This is the main area where all your packages live.
Understand packages and blueprints
A package is the collection that gets applied together. A blueprint is one individual template inside that package.
For example, you might create a package called `Standard Setup` that includes one feedback form blueprint, one campaign blueprint, and one widget blueprint. When that package runs, all of those items are created together.
- A package can include one type or several types together
- Campaigns depend on feedback forms, so the package needs a feedback form if it includes a campaign
| Type | What it creates |
|---|---|
| Feedback Form | A review collection form with your custom fields, branding, and settings |
| Campaign | An email and SMS review request sequence with your timing and message templates |
| Widget | A review display widget with your chosen style, filters, and layout |
| Auto Responder | An automatic review reply rule with your filters, delay settings, and response template |
| AI Prompt | Custom AI instructions that tell the AI how to write review replies for this customer |
If a package includes a campaign, it must also include a feedback form. Campaigns need somewhere to send customers.
Create your first package
Click `Create Package` and follow the setup wizard. The wizard is the easiest way to build a full onboarding package because it handles the order and dependencies for you.
- Step 1: package details
- Step 2: choose what to include
- Step 3: pick your templates
- Step 4: review and create
Step 1: package details
Give the package a name and, if useful, a description. This is mostly for your team so you can tell different package setups apart later.
If you use custom plans, you can assign the package to a specific plan. If you leave it on all plans, it can apply to any customer regardless of plan.
Step 2: choose what to include
Turn on the blueprint types you want inside the package. You do not need to use all five every time.
If you enable `Campaign`, the system also enables `Feedback Form` because campaigns depend on forms.
- Feedback Form: collect reviews and private feedback
- Campaign: automate email and SMS review requests
- Widget: display reviews on the customer website
- Auto Responder: automatically reply to new reviews
- AI Prompt: define how AI should write review replies
Step 3: pick your templates
For each enabled type, choose one existing resource to use as the template. The dropdown uses a `Resource Name - Organization Name` format so you can tell similar items apart.
The platform copies the resource settings at that moment. Later edits to the original source do not automatically update the blueprint copy.
- Feedback Form copies form settings, fields, and configuration
- Campaign copies steps, timing, and message templates
- Widget copies style, filters, and display settings
- Auto Responder copies filters, timing, approvals, and response logic
- AI Prompt copies the prompt name and instructions
Make sure the original source is exactly how you want it before you use it as a template. Later changes to the original do not flow back in automatically.
Step 4: review and create
The review step shows the full package summary and whether each blueprint is ready or missing something.
- `Auto-apply to new locations` makes the package run automatically when a new review source is connected
- `Bypass plan restrictions` lets the package create resources even if the customer plan would normally block that feature
Leave auto-apply on if the package is meant to act as your standard onboarding flow. Turn it off if you want to test or use it manually first.
How automatic application works
When a package is set to auto-apply, the platform watches for a customer connecting a review source on a location. It then finds the matching default packages for that customer and processes the blueprints in order for that location.
The feedback form is created first, then the campaign that depends on it, then the widget, then the auto responder, then the AI prompt.
This happens in the background and usually completes within a few moments, so the location reaches a usable setup without the agency needing to build each item manually.
- The trigger is a review source being connected on a location
- Plan matching is checked before creation
- The package runs in blueprint order
- Existing matching resources are skipped to avoid duplicates
Apply packages to existing customers
If customers already exist, you can still apply a package manually. Click `Apply to Customer` on the package and pick the customer locations you want.
You can do this for one customer, many customers, one location, or many locations in the same run.
- Search for the customer by name or email
- Expand the customer to see all locations across their organizations
- Select one or more locations
- Add them to the selection area
- Repeat for more customers if needed
- Click `Apply` when the selection is ready
Location status indicators
The apply flow shows status labels so you can tell what will happen before you run anything.
- `No source` means the location does not have a review source connected yet, so source-dependent parts of the package may be skipped
- `Applied` means this package already ran successfully on that location, but you can still re-apply it if you want to refresh the setup
- `In Progress` means another run is already working on it
Watch the progress
After you click apply, the platform opens a live progress view. This shows the overall status, progress bar, and a location-by-location breakdown.
- You can expand `Location Details` to see each blueprint result per location
- Skipped locations usually tell you why, such as `Already applied to this location` or `Feature not available on this customer plan`
- If you close the progress window, the jobs keep running in the background
- An active-run banner lets you reopen the progress view later
| Status | What it means |
|---|---|
| Running | The package is still being applied |
| Completed | Everything finished successfully |
| Completed with Issues | The run finished but some items failed or were skipped |
| Failed | The run timed out or hit blocking errors |
Managing your packages
Click `Edit` on a package to change package details, assign it to a custom plan, control auto-apply, use bypass mode, or pause the package.
You can also add more blueprints from the package edit screen without recreating the whole package from scratch.
- Edit package name and description
- Change plan assignment
- Turn auto-apply on or off
- Turn bypass plan restrictions on or off
- Pause or unpause the whole package
Pausing and deleting
A paused package does not auto-apply to new locations, but you can still apply it manually.
You can also pause individual blueprints if you want one part of the package skipped while keeping the rest active.
- Paused packages show a red `Paused` badge
- Paused blueprints stay in the package but are skipped during application
- You cannot delete a package while it is actively running
- If a blueprint has dependencies, such as a campaign needing a feedback form, the system prevents destructive removals in the wrong order
Real-world scenarios
Most agencies end up using blueprints in one of a handful of practical ways.
- Standard setup package for the most common client onboarding flow
- Different packages by custom plan tier
- Bulk application of new capabilities to existing customers
- Test packages before turning auto-apply on
- Separate packages for separate brands or service lines
- VIP or trial use with bypass plan restrictions enabled
- Seasonal packages for temporary campaigns
- Re-applying after a broken setup is removed manually
Tips and best practices
- Start with one strong standard package before building lots of variations
- Always pair campaign blueprints with a feedback form
- Use descriptive package names so the manual apply flow stays easy to manage
- Check the source template carefully before selecting it
- Use manual apply for existing customers
- Do not worry about duplicates because matching resources are skipped
- Watch the first few runs closely so you can confirm the package behaves the way you expect
- Keep packages focused rather than turning every package into a giant everything-bundle