العربيةExplore the platform

ARMADA application

Product roadmap

Customer Relationships

Customer Relationships covers a structured record for customer context, opportunities, follow-up, and the hand-off of qualified work to Sales.

Customer relationship scope

Contract-based preview — not connected to live data

Customer relationship scope
  • Opportunity capture
  • Structured qualification
  • Clear sales hand-off

Outcomes

What changes in your operation?

A unified communication record

Clear ownership for each follow-up

A defined hand-off from opportunity to order

Operating journey

From start to outcome

  1. 1

    Capture

    Keep the source and need in a clear context.

  2. 2

    Qualify

    Understand scale, priority, and next step.

  3. 3

    Hand off

    Move a qualified opportunity to the sales journey.

Application scope

Core capabilities

A practical scope that explains what this application covers and where its current boundary sits.

Opportunity capture

The operating scope captures source, need, and customer context in a structured record.

  • Clear source and need
  • Organised customer context

Structured qualification

The operating scope captures priority, scale, next step, and accountable owner.

  • Follow-up owner
  • Reviewable next step

Clear sales hand-off

The operating scope hands an approved opportunity to sales through a defined contract.

  • Opportunity kept distinct from order
  • Controlled hand-off

Control and governance

How does the work stay controlled?

Operating controls that preserve context, permission, and a reviewable trail.

Explicit scope contract

The contract defines entities, transitions, ownership, and permissions.

Source and contact consent

The contract must define source, consent, and handling of contact data.

One owner per transition

The boundary contract defines write ownership and the hand-off to sales.

One shared core

How does it connect to other applications?

Intended connections to the shared ARMADA core. Only the integrations covered by the approved scope are enabled.

Customer RelationshipsCustomer relationship scope

Sales

The connection hands an approved opportunity to sales through the boundary contract.

Reports

Views use an approved definition and source for every measure.

Access Control

Access is scoped by role, organisation, and approved contracts.

Implementation approach

From operating study to acceptance

A practical sequence that starts with the real operation and ends with clear acceptance of the agreed scope.

  1. 1

    Approve product scope

    Fix entities, states, ownership, permissions, and events first.

    One shared source of truth
  2. 2

    Design the follow-up journey

    Test capture, qualification, and hand-off against realistic scenarios.

    A journey the teams understand
  3. 3

    Configure and connect the scope

    Configure the journey and connect it through approved contracts and ownership.

    Controlled operation without shared writes

Designed for

Fits different teams and operating models

SalesCustomer serviceAccount management

Related applications

Applications that extend the same operating journey without separating its business context.

Sales

Organise quotations, orders, invoices, and collections in one traceable flow.

Contract-based preview

Reports

Turn connected operations into management views that retain their source.

Contract-based preview

Before you decide

Common questions about this application

What does Customer Relationships cover?

It covers opportunity capture, qualification, follow-up, and the hand-off of approved work to Sales.

Will it replace the Sales application?

It organises opportunity and follow-up, then hands approved work to Sales through a defined boundary.

Does this page collect contact data now?

No. Actual collection requires an approved interface, consent, and retention contract.