ABEE

    Technology

    A five-layer architecture

    ABEE is neither an AI model nor a simple connector. It is an orchestration layer that turns a human interaction into an action executed in enterprise systems, under explicit rules.

    Explore ABEE Core Security & GDPR
    In shortThe ABEE platform is organised in five layers: interaction, intelligence, workflows, integrations and security. Each layer is independent, so an interface, a workflow or an integration can be added without rebuilding the rest. The security layer is cross-cutting and governs every access to data.
    01

    Interaction layer

    The point of contact with a human, on any medium.

    Voice (phone, intercom)Text (web, Teams, mobile)Touch (tablet, kiosk)Physical interfaces (lobby screen, hologram)
    02

    ABEE Intelligence layer

    Understanding and conducting the conversation.

    Intent recognitionEnterprise knowledgeConversation handlingContext managementAgent orchestration
    03

    Workflow layer

    What happens once the request is understood.

    Visitor journeysCall handlingWorkplace requestsNotificationsActions in the tools
    04

    Integration layer

    Controlled connection to the information system.

    TelephonyMicrosoft Teams and messagingAPIs and workplace toolsVisitor management systems
    05

    Security layer

    The cross-cutting governance layer.

    Access controlEncryption in transitLoggingData governance

    This description is deliberately functional. Implementation details, network topology and configuration are not published and are shared under NDA during client security reviews.

    Interfaces are access points, not products

    A phone line, a lobby screen, a kiosk, a Teams conversation or a holographic agent all reach the same engine. Knowledge, workflows, permissions and analytics are defined once in ABEE Core, then exposed at every front door. Adding an interface never means rebuilding the intelligence behind it.

    ABEE Labs Resources

    Questions fréquentes

    Does ABEE build its own AI models?

    ABEE builds the orchestration layer, the domain knowledge and the front-of-house workflows. Language models are selected according to client requirements, in particular localisation and confidentiality.

    What exactly belongs to ABEE?

    The software asset is ABEE Core: the modelling of the front-of-house domain, the workflows, multi-channel orchestration, access governance and the associated analytics.

    Is the architecture reversible?

    Reversibility terms — export of knowledge and interaction history — are defined contractually before any deployment.

    An architecture review with your IT teams?

    We walk through integration details, access scopes and audit procedures.

    Demander une démonstration Security & GDPR