Start with a reusable workflow
Connect calls and forms to a branded lead flow that can be adapted across accounts.
Agency use case01 02 03 04 01 02 03 01 02 03 01 02 03
Launch a repeatable lead-response service across client accounts.
Spacebrain gives agencies one place to configure branded intake, qualification, follow-up, booking, and lead management—without rebuilding the delivery process from scratch for each client.
The problem
A new client should not require a new operating system.
When intake, qualification, follow-up, booking, and billing depend on separate tools and one-off fixes, each account adds delivery drag. A reusable Spacebrain workflow keeps the service consistent while preserving client-specific rules and lead context.
Apply client rules
Set qualification questions, routing, ownership, and booking logic for each client.
Keep delivery visible
Give the client team and agency a shared view of lead history, status, and next action in the built-in CRM.
White-label and rebill
Package the workflow under your brand and manage the recurring client service from Spacebrain.
What this use case connects
- White-label
- Rebilling
- Calls
- Forms
- Follow-up
- Booking
- Routing
Make lead response easier to deliver, explain, and repeat.
Start with one repeatable service pattern, then adapt the branding, questions, routing, and booking path for each client account.
Start for free →AGENCY DELIVERY
Use it when every client needs the same standard—not the same setup.
This workflow fits agencies turning lead response into a repeatable service while keeping each client’s brand, questions, routing, calendars, and lead records separate.
You sell lead response as a service
The offer includes capture, qualification, follow-up, booking, or a combination of those steps.
Clients need their own operating rules
Each account may use different services, qualification questions, owners, hours, and calendars.
Delivery has to be repeatable
Your team needs one onboarding pattern instead of rebuilding the operating model from scratch for every client.
WORKFLOW
Turn the service into a launch sequence.
Standardize the parts your agency owns, then adapt the client-specific decisions without losing visibility or account separation.
- 01
Define the service template
Choose the channels, qualification stages, follow-up boundaries, booking path, and deliverables included in the offer.
- 02
Collect client decisions
Capture the brand voice, request types, questions, escalation rules, owners, calendars, and business hours.
- 03
Configure the account
Apply the repeatable workflow while keeping client-specific records, branding, routing, and access separate.
- 04
Launch one lead path
Test a call, form, or campaign source from capture through handoff before expanding the scope.
- 05
Review and refine
Use conversation and lead status in Spacebrain’s built-in CRM to adjust questions, routing, and ownership.
- 06
Manage the commercial model
Use white-label and rebilling capabilities to package the workflow inside the agency’s client service.
BEFORE YOU LAUNCH
Separate the template from the client decisions.
The agency should own a repeatable delivery method. The client should provide the rules that make the method correct for their business.
Agency template
- Included lead sources and channels
- Qualification and follow-up stages
- Onboarding checklist and approval points
- Launch test and handoff QA
- Reporting and review cadence
- Service boundaries and escalation process
Client-specific decisions
Brand and conversation style
Define the approved name, tone, greetings, and language for the account.
Fit and qualification
Document what the client accepts, rejects, prioritizes, or sends for review.
Routing and booking
Connect the correct owners, locations, calendars, and after-hours paths.
Ownership and access
Decide who can view, manage, and act on each client’s lead records.
THE HANDOFF
Make the service easier to launch, explain, and repeat.
A repeatable operating model helps the agency know what is standard, what changes by client, and what must be approved before launch.
A clearer onboarding path
The same decisions are collected in the same order for every client account.
A consistent delivery standard
Each workflow follows the agency’s service model while preserving the client’s own rules.
A connected client record
Conversations, status, ownership, and bookings stay visible inside the client’s built-in CRM workflow.
Start small. Start with one service package and one client profile. Prove the onboarding and handoff checklist before adding optional variations.
AGENCY FIELD GUIDE
A repeatable lead-response service is an operating model, not a bundle of tools.
The agency value is not that every client gets the same configuration. It is that every client receives a clear, accountable process for capturing demand, applying their rules, continuing the conversation, and handing the lead to the right next step under the agency’s standard of delivery.
Productize the decisions, not just the channels.
Calls, forms, messages, calendars, and a built-in CRM are delivery surfaces. The agency’s service is the set of decisions that connects them: what counts as a lead, what information matters, who owns each path, when a customer can book, and when a human must review. If those decisions change from account to account without a framework, the service will remain custom work even when the technology is shared.
Keep client truth separate from agency method.
The agency should own a repeatable launch sequence, quality check, reporting rhythm, and definition of a complete handoff. The client should own the facts that make the workflow correct for their business: services, offers, locations, hours, language, escalation choices, calendar availability, and approval boundaries. This separation keeps the implementation disciplined without flattening the client’s operation.
Make the handoff part of what you deliver.
Many accounts can generate a reply. Fewer can show a client how a request moved from source to context, qualification, owner, next action, and outcome. A visible handoff is the artifact that makes the service easier to explain, review, and improve. It also gives the agency and client team a shared language when something needs to be corrected.
DELIVERY SEQUENCE
Use the same launch sequence for every account—even when the rules differ.
A reusable sequence makes onboarding more reliable because the agency asks for the same categories of decisions in the same order. The account-specific answers can vary; the implementation discipline should not.
- 01
Define the service boundary before configuration begins.
State what the agency is responsible for in this version of the service. Is the scope capture and routing, qualification and follow-up, booking, white-label account setup, or a defined combination? Name the included sources, channels, review points, and handoff states. A boundary is not a limitation in disguise; it is what allows the client to understand what the service will and will not operate.
- 02
Collect the client’s operating rules once, in a usable format.
Gather the decisions that cannot be guessed: approved business name and tone, services and exclusions, qualification signals, service areas, team ownership, business hours, calendar paths, escalation instructions, and the language that requires review. Do not scatter these across sales notes, messages, and a kickoff call. Put them into a client configuration brief that the implementer and reviewer can use.
- 03
Configure one representative lead path first.
Choose a common, high-value scenario rather than attempting every source and exception at launch. For example, a new inquiry from one form or one call type can reveal whether the questions, routing, lead record, and owner assignment make sense. The purpose is to prove the operating model, not to create the broadest possible workflow on day one.
- 04
Run a realistic test with the client’s actual decisions.
Test complete, incomplete, out-of-scope, and exception examples. Follow the record from source through the reply, routing, built-in CRM status, handoff, and closing state. A test is not just a technical check. It is a chance for the client team to notice a missing question, an unclear message, an unstaffed queue, or a decision that was never documented.
- 05
Document the review cadence and the change path.
Decide how the agency and client will review real lead records, request changes, approve new rules, and correct exceptions. Without a change path, every adjustment becomes an informal request and the delivery standard slowly erodes. With one, the service can adapt while preserving a record of what changed and why.
TEMPLATE VS. CONFIGURATION
Standardize the agency method. Configure the client reality.
This distinction keeps teams from overbuilding templates that are too rigid to use or accounts that are too bespoke to maintain. The template gives the agency a consistent delivery structure; the configuration makes that structure correct for a particular client.
What belongs in the agency template
- The intake and onboarding sequence, including approval points and the definition of a launch-ready account.
- The recurring lead states, review checklist, handoff expectations, and standard quality checks.
- The required record fields for source, context, owner, status, next action, and outcome.
- The test scenarios used before a new path is expanded or an important rule is changed.
- The process for client requests, escalation, documentation, and scheduled operational review.
What belongs in each client configuration
Customer-facing language and claims
Use the client’s approved name, tone, service language, policies, and customer commitments. The agency should not create promises the client has not authorized.
Fit, qualification, and exclusions
Document the requests the client accepts, declines, prioritizes, or sends to review. Clear exclusions are as important as preferred leads.
Routing, availability, and booking
Connect the correct people, teams, locations, business hours, calendars, and fallback paths for the account.
Access and commercial ownership
Set who can view, manage, and act on client lead records, and how the white-label or rebilling arrangement is represented inside the client service.
QUALITY ASSURANCE
Quality is visible when the service survives a real handoff.
A launch can look complete in a checklist and still fail in use. The practical test is whether the account’s users can see what happened, understand why it happened, and take the next action without translating the work back into their own system.
Test the happy path and the awkward path.
Run an example that should move smoothly from source to booking or owner. Then test the situations that expose ambiguity: incomplete information, an out-of-area request, a specialist need, an existing customer, an after-hours inquiry, or a request that must be reviewed. A delivery standard is credible when it explains what happens outside the ideal case.
Read the record as the client would.
Open the lead without relying on implementation notes. Can a client team member identify the source, reason for contact, answers collected, messages sent, current owner, and next action? If the agency must explain the record every time, the account is not yet delivering a connected handoff.
Make changes traceable rather than conversational.
When a client asks to update a question, routing rule, team owner, or follow-up boundary, capture the request, the decision, and the test that verifies it. This protects both sides from changes disappearing into a chat thread and makes future reviews more productive.
Practical starting point. Start with one client profile and one lead source that the agency understands well. Launching a narrow, observable workflow gives the team a reference point for later variations. Expand only after the client and agency can agree on what is standard, what is client-specific, and where the next owner sees the complete context.
SERVICE REVIEW
Review the account as an operator would, not as a dashboard would.
Operational review is a chance to inspect the path from inquiry to next action. It should focus on whether the process is understandable and owned—not on creating a performance claim that the account cannot substantiate.
Questions for a practical account review
- Did the intended lead sources enter the correct workflow with their context preserved?
- Can the client identify the person or queue responsible for each open request?
- Can the next owner see why the route was chosen and what has already been communicated?
- Are exceptions appearing in a reviewable state rather than being forced into a normal path?
- Do completed records show the agreed state: booking, review, handoff, resolution, or closure?
Use findings to protect the delivery standard
Refine the template only after a pattern appears.
One unusual client request is not necessarily a new standard. Update the agency method when the team can explain the repeated situation and the approved way to handle it.
Keep client changes client-specific when they should be.
A unique service rule, calendar constraint, or brand decision can remain within one account without making the shared delivery model more complex.
Document ownership changes immediately.
When people, teams, or hours change, update the configuration and test the handoff. Ownership is one of the details most likely to break quietly.
Review the language beside the actual client offer.
Customer-facing replies and booking steps should remain aligned with the promises the client makes on its website, campaigns, and sales process.
COMMON QUESTIONS
Questions agencies should answer before they add another client account.
How much of the workflow should be standardized?
Standardize the delivery method: intake, testing, lead states, handoff expectations, review, and change management. Configure the client facts that make the method correct: brand, services, offers, qualification, ownership, schedules, and policies. This gives the agency consistency without treating clients as interchangeable.
What should the agency show a client after launch?
Show the operating path, not just a software screen. The client should understand which sources are connected, what information the workflow collects, who receives each request, how the lead record stays connected, how exceptions are handled, and where they can request a change.
When is the service ready to expand?
Expand when the existing account can be launched, tested, reviewed, and changed without relying on an individual’s memory. If the agency can explain the standard, retrieve the client decisions, follow the handoff, and correct an exception, it has a foundation for the next variation.
DELIVERY DISCIPLINE
The agency delivers a clearer path from inquiry to accountable next action.
White-label delivery becomes easier to sustain when the agency can separate its repeatable method from the decisions each client owns. Spacebrain provides the connected workflow and built-in CRM context; the delivery discipline is what turns that capability into a service clients can understand and use.
Capture the client truth.
Gather and approve the rules that define how the account should respond, route, book, and escalate before the service goes live.
Apply a reusable operating method.
Use the same onboarding, test, record, handoff, review, and change process across accounts while preserving the differences that matter.
Keep the service inspectable.
Make the source, context, ownership, conversation, and next action visible so the agency and client can review work together and improve it deliberately.
CLIENT APPROVAL
Treat approval as part of the service, not a box to tick.
The client should be able to approve the important decisions in a form they can understand: what the workflow can say, what it should collect, who receives each kind of request, which path is used after hours, and where a human must review. That conversation prevents scope drift before it appears in a live lead.
Show the decision map.
Give the client a readable view of the lead paths, questions, owners, and exceptions. A visual or written decision map is more useful than asking a client to approve a list of technical settings they cannot evaluate.
Record the approved language.
Keep the approved business name, tone, service descriptions, offers, and customer commitments in the account configuration. When wording changes, treat it as an account update that deserves a review and test.
Make the next change easy to request.
Clients will learn from real inquiries. Give them a clear route to request a new rule, a wording update, an owner change, or a revised handoff without asking them to reverse-engineer the system.
SEE THE PLANS
Choose the plan behind your first workflow.
Compare plan options, included capabilities, and usage before you build.
See pricingONE CONNECTED WORKFLOW
- Capture
- Qualify
- Follow up
- Book
- Built-in CRM
Start with calls, forms, or a client workflow. Keep the next step connected.
