Your industry · Your work OS
Your brand’s application, with a clear scope for each location.
Present the offers and contact instructions authorised for your network. The journey defines who receives each enquiry; internal knowledge and local records retain separate access rules.
What customers can do with your application.
What customers browse: The services approved for the brand or relevant location.
What you receive: The offer and location when configured, plus the question and contact details.
Your benefit: Present authorised offers without exposing data from every location.
What services does this location offer?
I have a question about this offer.
How can I request a callback from this business?
Illustrative examples of the journey to configure. A submitted enquiry is not an accepted service order or a confirmed appointment.
Multi-site operation, routing between locations and brand usage rights must be scoped. The base application does not promise an unlimited network rollout.
Your initial scope and extensions.
The Customer AI Application includes your company identity, an authorised offer catalogue, conversational search, contextual enquiries, an administration dashboard and WebApp, plus initial configuration and launch testing.
Additional team workflows: Network procedures, head office decisions, local questions, shared knowledge and location-level access.
Booking journeys, business integrations, private documents and the internal workspace are defined separately, according to available features and the quote. They are not automatically added to the customer application.
Workflow example
A concrete workflow, from the signal to the next step
Several authorized branches report the same operational question.
Head office reviews the available reports and validates a shared response.
Each site finds the rule and the action relevant to its scope.
A new branch accesses approved network knowledge without receiving every site’s private records.
Fictional illustration. Available capabilities, sources and access depend on your environment; conditions are explained below.
Networks and franchises: carry decisions through to each site
On this page
Share what the network needs
A central procedure may be common while local customer files remain private. Groups, roles and scopes determine what head office, regional coordinators and sites can consult.
From a central decision to local work
A decision must keep the reason for the change, affected sites and next action. A mission can show what awaits clarification or an owner without asserting that every site has executed it.
Repeated questions and recurring signals
A group of approved knowledge helps avoid answering the same question twenty times. Local feedback may reveal a shared issue to examine, without turning a few exchanges into an official network indicator.
Campaigns and new sites
Objections encountered locally can contribute to a campaign review within the authorized scope. A new site finds the procedures, decisions and dependencies useful for opening instead of reconstructing the entire history.
Connections, languages and local dependencies
Provider configuration must be checked for the relevant site. Translation can facilitate exchanges between regions; important instructions still need validation. Head office does not automatically receive full access to local environments.
Professional scope and responsibilities
AlefOS does not manage till transactions, inventory, royalties, accounts, franchise agreements, HR schedules or training certification. It does not calculate site profitability. Operators retain their activity and head office its decisions within configured permissions.
Your team’s tools
Explore features, connections and access rules in the AlefOS documentation.
Explore the documentation ↗Continue exploring
This workflow uses capabilities configured in your company’s environment, under your brand. Your team can use a compatible assistant to consult authorized context through its configured MCP connection. Understand your AI connection ↗