Customer Interaction & Integration Layer

Every interaction. One connected ecosystem.

A unified customer interaction and integration layer connecting conversations, contacts, channels and business applications.

Developed and operated by AAL Team

Platform

A transversal layer between your customers and your applications

AAL-Nexus sits between the channels your customers use and the business applications your teams rely on. It is built as shared infrastructure: one place to manage interactions, with every organization, user and permission kept clearly separated.

Communication channels
  • Email
  • SMS
  • Messaging
  • Web
AAL-Nexus
  • Interactions
  • Contacts
  • Identity & access
  • Automation
Business applications
  • RoofUp
  • RoofBuild
  • RoofAdmin
  • Other systems
Conceptual architecture. Channels and integrations are added progressively.
  • Customer Interaction Layer In development

    A shared model for conversations and contacts, so every interaction is recorded once and understood in context.

  • Business application integration In development

    Connects with business applications through APIs, so each application keeps its own data while sharing the interactions that matter.

  • Multi-company environments Available

    Each organization works in its own workspace, and a user can belong to several organizations without their information being mixed.

  • Independent identities and permissions Available

    Users, memberships, roles and permissions are managed per organization, so access is granted exactly where it is needed.

  • Omnichannel readiness In development

    The interaction model is designed for channels such as email, SMS and messaging apps, which will be enabled progressively.

Available operational in the current platformIn development being built, not yet commercially available

Capabilities

What AAL-Nexus is being built to do

The platform foundation — organizations, identities, permissions and secure access — is in place. The capabilities below are being built on top of it and will be released progressively.

  • In development

    Unified Inbox

    One shared workspace for customer conversations, with status, ownership and history in a single view.

  • In development

    Contact360

    A complete profile for each contact, bringing together identities, conversations and activity across channels.

  • In development

    Multichannel Communication

    Conversations from multiple channels handled from one place, under the same rules and permissions.

  • In development

    Workflow Automation

    Rules and templates to route, assign and follow up on interactions without repetitive manual steps.

  • In development

    Business Integrations

    API connectors linking AAL-Nexus with AAL applications and other business systems.

  • In development

    Operational Analytics

    Indicators on volume, response and workload, scoped to each organization and to each user’s permissions.

AAL ecosystem

One layer for many applications

AAL-Nexus is not a CRM tied to a single product. It is a transversal layer designed to serve several applications at once — starting with the AAL Team portfolio and open to other business systems.

  • Integration through APIs, never through direct access to another application’s database.
  • Each application keeps ownership of its own data.
  • Shared conventions for organizations, identities and permissions across products.
  • RoofUpAAL Team applicationPlanned
  • RoofBuildAAL Team applicationPlanned
  • RoofAdminAAL Team applicationPlanned
  • Other applicationsCRM, ERP and operational systemsPlanned
AAL-Nexus
Integrations shown here are planned. None is presented as live until it has been released.

Security & trust

Access built around organizations and explicit permissions

Security in AAL-Nexus starts with how people sign in and what each of them is allowed to see.

  • One-time code authentication

    Users sign in with single-use verification codes delivered by email.

  • Organization-level access control

    Every request is evaluated within the organization it belongs to, and authorization is enforced on the server.

  • Contextual permissions

    What a user can see and do depends on their role and permissions in each organization.

  • Logical tenant separation

    Each organization’s information is kept logically separate from that of every other organization.

  • Transactional communications

    Service messages, such as sign-in codes, are sent from the dedicated nexus.aal-cloud.com domain.

Corporate identity

Developed and operated by AAL Team

AAL-Nexus is designed, developed and operated by AAL Team, a software company that builds business applications and the platforms that connect them.

AAL Team uses a small set of domains, each with a clear purpose:

aal-team.com (opens in a new tab)
Corporate website of AAL Team.
aal-cloud.com (opens in a new tab)
Corporate technology domain of AAL Team, home of its platforms and services.
nexus.aal-cloud.com (opens in a new tab)
Product site of AAL-Nexus and the domain used for its transactional communications.

Visit aal-team.com (opens in a new tab)

Contact

Talk to AAL Team

For information about AAL-Nexus, its availability or integration with your business applications, contact AAL Team through its corporate website.

Automated messages sent from no-reply addresses are not monitored. Please do not reply to them; use the contact channel above instead.