The client stack stays in the client workspace.
Catalogue, booking, and routing attach to the client. They do not replace the store, calendar, or tools the client already runs.
Website, then knowledge, then action.
Then the systems they already run.
- Website
Connect the client site. That is the first approved source.
- Knowledge
Pages, files, and policies stay in the knowledge lane on that client.
- Action
Website Chat, WhatsApp, Instagram, and AI Forms turn questions into a next step.
- Systems
Contact Requests, scheduling, exports, and webhooks keep the existing stack involved.
Keep source material next to the conversation.
Two lanes, one client.
The agency approves website and policy content for the knowledge lane. Live store products stay in dedicated catalogue tools, attached to the same client workspace.
Catalogue, scheduling, routing.
Each connection has its own page.
