Frequently asked questions

Staamina is an agentic operations orchestration platform designed for multi-site networks.

It centralises incidents, operations, interventions, equipment, workflows and service providers, then orchestrates their handling end to end.

Thanks to its workflow engine, business rules and AI agents, Staamina automates qualification, dispatch, coordination, follow-up and escalation tasks while keeping human oversight on critical decisions.

An operations orchestration platform doesn't just record requests: it moves operations forward.

Staamina connects establishments, head-office teams, area managers and service providers around a single workflow.

When an incident is reported, Staamina can identify its context, qualify it, determine the next actions, engage the right stakeholders, track their execution and escalate when the defined rules require it.

An agentic platform uses AI agents able to execute sequences of actions within a framework defined by rules, data and permissions.

In Staamina, agents can in particular:

• understand and structure a request
• gather the necessary context
• determine the next steps
• trigger workflows
• engage an establishment or a service provider
• perform follow-ups
• track deadlines
• detect exceptions
• escalate to a human when needed

The goal is not simply to generate responses, but to automate operational execution.

No.

The chatbot is only one possible point of interaction with the platform.

The core of Staamina is its operations orchestration engine, which combines data, business rules, workflows, integrations and AI agents to move operations forward until they are resolved.

A ticketing tool mainly records a request and lets you track its status.

Staamina orchestrates the process behind that request.

From the initial capture through to resolution, the platform can qualify, assign, coordinate, follow up, validate, escalate and log every step.

The ticket thus becomes the starting point of an operational workflow, not its end.

CMMS solutions are mainly focused on managing maintenance, equipment and interventions.

Staamina adds an operations orchestration layer that connects establishments, head-office teams, area managers and service providers.

The platform can also work with existing maintenance tools to orchestrate operations without necessarily requiring their replacement.

CAFM and Facility Management platforms mainly structure activities related to buildings, equipment and maintenance.

Staamina focuses on the execution and coordination of operations between the different stakeholders in the network.

The platform can therefore sit on top of or alongside existing systems to automate the operational workflows that connect sites, teams and service providers.

Staamina is designed for organisations that run multi-site networks, with several establishments, internal teams, area managers or service providers.

The main users are:

• Operations departments
• Network management
• Regional or area managers
• Maintenance and facility management teams
• Establishment managers
• Support teams
• Service providers and technicians

Staamina primarily targets multi-site networks whose activity depends on the availability and proper functioning of their establishments.

The main verticals are:

• Retail
• Restaurants
• Hospitality & reception
• Fitness & leisure
• Agencies and services
• Health and local services

Yes.

Staamina is particularly well suited to franchise organisations where head office needs to keep operational visibility while allowing establishments to remain autonomous.

The platform makes it possible to manage different levels of responsibility between franchisor, franchisees, area managers and service providers.

Staamina addresses the friction that arises between detecting a problem and resolving it:

• incomplete information
• poorly qualified requests
• scattered tools
• lack of visibility
• manual coordination
• repetitive follow-ups
• unclear responsibilities
• intervention times that are hard to control
• lack of standardisation between establishments
• limited visibility on service provider performance

Staamina primarily aims to improve:

• operational responsiveness
• resolution times
• SLA compliance
• team productivity
• the quality of operational data
• coordination with service providers
• head office visibility over the network
• process standardisation

Staamina is the intelligent platform that orchestrates operations and maintenance across multi-site networks, from incident to resolution.

Staamina's agentic architecture can call on several specialised agents depending on the steps of a workflow.

For example:

Capture agent : understands and structures requests coming from textual or unstructured information.

Qualification agent : analyses the context, identifies the category, criticality and information needed for handling.

Dispatch agent : determines the right stakeholder or service provider based on business rules, site, availability, skills and SLAs.

Coordination agent : tracks the progress of an operation, engages the relevant stakeholders and triggers the planned actions.

Follow-up agent : identifies pending actions and performs the follow-ups planned by the workflow.

Escalation agent : detects situations requiring human intervention and applies the escalation rules.

Yes, within the scope defined by workflows, permissions and business rules.

An agent can execute several successive steps without requiring human intervention at each action.

Sensitive operations or those requiring a decision can remain subject to human validation.

Agents operate in an environment governed by:

• business rules
• workflows
• permissions
• user roles
• approval thresholds
• criticality levels
• escalation rules

An agent's autonomy is therefore defined and governed by the organisation.

Staamina can request additional information, pause a step or escalate to an operator.

The goal is to prevent uncertainty from being automatically turned into an operational decision.

Workflows make it possible to define which actions require human validation.

Sensitive topics, business exceptions, significant spending or critical operations can thus be submitted for approval before execution.

Agents rely on the available operational context, the organisation's data, business rules and configured workflows.

When the available information is insufficient, Staamina can request clarification or hand the decision over to a human.

Staamina leverages the context, data and operational rules defined in the platform to adapt workflow execution to how each organisation operates.

Business rules remain controllable and explicit for the teams.

Staamina can automate various steps of an operational process:

• qualification
• assignment
• dispatch
• notifications
• follow-ups
• information gathering
• confirmation requests
• escalations
• validations
• SLA tracking
• closing operations

Yes.

A workflow can start with a request raised from an establishment and continue automatically across several stakeholders until resolution.

For example: Incident → qualification → dispatch → service provider → intervention → confirmation → validation → closure → reporting.

Yes.

The workflow engine makes it possible to define the steps, conditions, responsibilities, deadlines, automatic actions and escalation rules specific to each process.

Yes.

Workflows can be adapted based on:

• establishment
• region
• brand
• category
• equipment type
• service provider
• contract
• criticality level
• business rules

Yes.

SLAs can be associated with workflows and used to trigger alerts, follow-ups and automatic escalations.

Teams can track response, intervention and resolution times according to the defined rules.

Yes.

Escalation rules can depend on time, criticality level, site, service provider, incident type or any other business criterion.

Yes.

Approval workflows make it possible to control actions requiring validation, based in particular on:

• cost threshold
• criticality level
• intervention type
• category
• establishment
• manager
• region

Yes.

Staamina supports recurring workflows and scheduled operations, notably for preventive maintenance processes, inspections, audits or other periodic operations.

Yes.

Staamina orchestrates the full cycle of a corrective operation: reporting, qualification, dispatch, intervention, follow-up, validation and resolution.

Yes.

Preventive operations can be scheduled based on calendars, frequencies, equipment, establishments or business rules.

Workflows then make it possible to track their execution and manage any exceptions.

Yes.

Equipment can be associated with establishments, interventions, incidents and history to keep the necessary operational context.

Yes.

The history can bring together the incidents, interventions and operations associated with a piece of equipment to make diagnosis, tracking and maintenance easier.

Yes.

Audit workflows can be standardised, scheduled and tracked across the network.

The results and associated actions can then be centralised to ensure follow-up.

The dispatch engine takes into account the rules defined by the organisation and can notably rely on:

• establishment
• category
• criticality
• skill
• availability
• service provider
• contract
• SLA
• geographic area

The goal is to route each request to the right stakeholder with as little manual intervention as possible.

Yes.

The platform is designed to orchestrate operations between internal teams, establishments and external service providers.

Yes.

Workflows can allow service providers to receive the requests assigned to them, provide progress updates and confirm the steps needed for closure.

Yes.

Workflow rules can automatically trigger follow-ups when an expected action has not been carried out within the planned time.

Yes.

Staamina centralises the operational data needed to track in particular:

• intervention volumes
• response times
• resolution times
• SLA compliance
• incident recurrence
• performance per service provider

Yes.

The platform is natively designed for multi-site environments.

Establishments, regions, teams, service providers and business rules can be organised within a single operational architecture.

Yes.

Workflows, permissions, SLAs, business rules and escalation levels can be configured according to the different geographic or organisational scopes.

Yes.

Staamina makes it possible to combine centralised rules at head-office level with processes specific to each establishment, region or entity.

Yes.

The multi-entity architecture makes it possible to structure operations according to the defined organisations, brands, regions or scopes.

Yes.

Staamina is designed for environments requiring:

• centralised governance
• fine-grained permission management
• complex workflows
• traceability
• integrations
• SLAs
• automation
• human oversight
• multi-site and multi-region operation

Yes.

Staamina is designed to integrate with the existing operational ecosystem to avoid creating a new, isolated environment.

Staamina can integrate in particular with:

• CMMS
• CAFM
• ERP
• CRM
• ticketing tools
• communication tools
• establishment management systems
• business tools
• platforms offering APIs or data feeds

Integrations can rely on APIs, webhooks and structured data feeds to synchronise the information needed by the workflows.

Not necessarily.

Staamina can act as an orchestration layer on top of existing systems.

The goal is to connect tools rather than multiply operational silos.

Requests can be captured from the interfaces and channels connected to Staamina.

The platform then turns the available information into structured data usable by the workflows.

Yes.

Staamina is designed to let field teams capture, view and track operations from their mobile devices.

The goal is precisely to limit that friction.

Staamina can integrate with the channels and tools teams already use to make operational automation possible without systematically imposing new, complex processes.

Permissions and automation rules can be configured based on roles, teams, sites, workflows, categories and risk levels.

Yes.

Actions, workflow steps and interactions can be logged to ensure operational traceability and make audits easier.

Yes.

Human oversight can be built directly into the workflows when certain actions require validation or a decision.

Yes.

Permissions and workflows make it possible to precisely define which actions an agent can perform automatically and which require human intervention.

Staamina centralises the data needed for operations to function, notably information relating to establishments, incidents, equipment, interventions, workflows, users and service providers according to the configured scope.

Yes.

Staamina's architecture includes governance mechanisms, role and permission management, access control and operational traceability to meet the requirements of professional and enterprise environments.

Staamina is designed with data protection and security as guiding principles.

Specific requirements around compliance, data retention, access management and governance can be defined according to each organisation's constraints.

Deployment generally follows several steps:

• Scoping : identifying the processes, stakeholders, business rules and systems involved
• Configuration : setting up workflows, roles, SLAs, escalation rules and integrations
• Pilot : deployment over a defined operational scope
• Measurement : analysing the results and adjusting the workflows
• Scaling : gradual extension to other establishments, regions or processes

Yes.

A deployment can start on a limited number of sites to validate the workflows and measure results before a larger-scale rollout.

The duration depends on the number of sites, the complexity of the workflows, the integrations and the level of customisation required.

The preferred approach is a gradual deployment that quickly generates value while progressively building functional coverage.

Yes.

Staamina centralises operations to provide a consolidated view of incidents, interventions, SLAs, equipment and activity across the network.

Indicators can notably cover:

• incident volume
• response time
• resolution time
• SLA compliance
• service provider performance
• incident recurrence
• intervention volume
• operational workload
• performance per establishment
• performance per region

Yes.

Operational data can be consolidated and analysed by establishment, region, brand, incident category or service provider to identify gaps and trends.

Yes.

Centralising incidents, equipment and interventions makes it possible to identify recurrences and surface the operational problems requiring structural action.

ROI depends on the volume of operations, the complexity of the network and the existing processes.

The main value levers are generally:

• reduced administrative time
• automated follow-ups
• shorter resolution times
• improved SLA compliance
• fewer information losses
• better service provider coordination
• process standardisation
• improved operational visibility

Staamina's goal is not to replace teams.

The platform automates repetitive coordination, follow-up and reminder tasks so teams can spend more time on decisions, problem solving and higher-value activities.

Yes.

The business case can be built from the network's real data: incident volumes, handling times, intervention times, coordination costs, SLAs, administrative workload and service provider performance.

The main elements are:

• network structure
• establishments
• teams and responsibilities
• existing processes
• incident categories
• business rules
• service providers
• SLAs
• existing tools
• operational goals

Yes.

This is a particularly good approach to quickly identify potential gains.

A first workflow can then serve as a foundation to progressively extend Staamina to other operations.

Use cases with high volume, strong repetitiveness or complex coordination are generally the most valuable.

For example:

• incidents and maintenance requests
• service provider dispatch
• intervention tracking
• preventive maintenance
• audits and inspections
• SLA escalations
• recurring operations

Staamina identifies the information needed to move the workflow forward and can automatically reach out to the requester or the relevant stakeholder.

If the situation cannot be resolved automatically, it is escalated to the right contact.

The first step is to identify a concrete operational process where Staamina can create value.

From that process, we can define the target workflow, the business rules, the stakeholders involved and the indicators to measure results.

The goal: quickly move from a manual process to an orchestrated, automated and measurable operation.