Keep client work isolated
Workspaces separate client data and workflow access. Workspace roles distinguish owners, editors, agents, and viewers.
For WhatsApp agencies and implementation partners
Ship client WhatsApp systems without rebuilding the backend.
Create an isolated workspace for each client, reuse approved workflow structures, test every branch, and deploy to the Meta account and number the client owns.
The problem
Client delivery repeats the same infrastructure work
Client requirements change. Meta setup takes time. Custom backends repeat the same infrastructure work. A basic chatbot tool becomes a dead end as soon as the workflow needs real logic.
Outcomes
Delivery outcomes to inspect
- A separate workspace and access boundary for each client.
- A reusable, validated workflow structure instead of a fresh backend for every brief.
- A tested branch map before the client’s WhatsApp number is connected.
- A deliberate publication record for the workflow that is live.
Capabilities
The tools behind the work
Reuse a working starting point
Export and import validated Fluenta v2 flow JSON when a proven structure should become the starting point for a new client.
Test before connecting a number
Use the simulator to inspect customer inputs, variables, and branch behavior before a workflow is published.
Inspect a live operation
Review workflow and conversation activity in the workspace rather than treating a published flow as a black box.
How a flow looks
A delivery system, not another basic chatbot tool
Isolate client work, reuse versioned structures, simulate the journey, extend it with APIs or code, and publish intentionally.
01 · Scope
Map the client journey
Turn the client brief into explicit questions, conditions, handoffs, and operational endpoints.
02 · Build
Start from an approved structure
Use a known flow shape, then adapt the client’s copy, variables, and integrations.
03 · Test
Simulate every branch
Exercise normal, unavailable, and human-handoff paths before publishing.
04 · Publish
Deploy deliberately
Publish the validated workflow to the WhatsApp setup the client owns.
Example workflow
Dental clinic booking and deposit
- 01Qualification — ask the patient’s reason for visit and route unsuitable requests to staff.
- 02Service selection — capture the appointment type and required details.
- 03Availability — offer slots configured for the clinic’s own booking rules.
- 04Deposit — request a configured amount through the payment node when the clinic requires one.
- 05Confirmation — retain the booking reference and send the next-step message.
- 06Reminder — add a deliberate follow-up message where the clinic’s policy requires it.
- 07Human escalation — route exceptions to a person with the captured context.
- 08CRM sync — planned extension; it is not included in this demonstration workflow.
Demonstration workflow using a first-party Fluenta template.
Product truth
Agency controls: shipped and planned
- Shipped: client workspaces
- Workspaces isolate client work and access.
- Shipped: roles
- Owners, editors, agents, and viewers have different access levels.
- Shipped: template reuse
- Validated flow JSON can be exported and imported as a starting structure.
- Planned: central deployment health
- A cross-client health view is not available today.
- Planned: white-label
- White-label delivery is not available today.
- Planned: client billing
- Client billing is not available today.
- Planned: workspace transfer and per-client usage
- Workspace transfer and a per-client usage view are not available today.
Metrics
Agency operation metrics
- Client workspace
- Published workflow version
- Workflow executions
- Conversation activity
- Human handoffs
- Changes published
Questions
Before you build
Who owns the WhatsApp account and number?
The client retains the WhatsApp Business account, phone number, and Meta billing relationship.
Can we white-label Fluenta or bill each client from the platform?
No. White-label and client billing are planned capabilities, not available product features.
Can a workflow use an API or code?
Yes. HTTP and code nodes can extend a visual flow where an operational step needs them.
Build your first client workflow free
Start with the client journey, test the operational branches, and publish only the workflow you intend to run.