Lead & Opp service (SA)

Use Cases

1. Create Lead / Opportunity in CRM

API
POST /integration-service/int/api/crm/v1/combo-create-lead-opportunity

Purpose

To create a new Lead with "New Lead" status for NTB customers, or a new Opportunity with "New Opportunity" status for ETB customers, after validating existing records with different ownerId.

Scenario

A customer starts a product journey (onboarding, lending, card, etc.) from a digital channel and needs to be registered in CRM for tracking and processing.

System Action

• The channel system triggers the
  /combo-create-lead-opportunity API via integration service to CRM.
• For NTB:
  • The service checks existing Opportunity records.
    • If a record with the status other than "Close won" or "Close lost" exists with the same RM (ownerId), the backend returns the existing opp id and the process ends.
    • If a record with the status other than "Close won" or "Close lost" exists with a different RM (ownerId),  the current record will be updated "Close lost" and a new record is created with "New Opportunity" status.
    • If a record exists with the "Close won" or "Close lost" status, a new record is created with "New Opportunity" status.
    • If a record does not exist or exists with the status "Close won" or "Close lost", continue to check the existing of Lead.
  • The service checks existing Lead records.
    • If a record with the status other than "Close lost" exists with the same RM (ownerId),  the backend returns the existing lead id and the process ends.
    • If a record with the status other than "Close lost" exists with a different RM (ownerId), the current record will be updated "Close lost" and a new record is created with "New Lead" status.
    • If a record does not exist or exists with the "Close lost" status, create a new lead with "New Lead" status.
• For ETB:
  • The service checks existing Opportunity records.
    • If a record with the status other than "Close won" or "Close lost" exists with the same RM (ownerId), the backend returns the existing opp id and the process ends.
    • If a record with the status other than "Close won" or "Close lost" exists with a different RM (ownerId),  the current record will be updated "Close lost" and a new record is created with "New Opportunity" status.
    • If a record does not exist or exists with the status "Close won" or "Close lost", create a new opp with status "New Opportunity".

Outcome

A Lead or Opportunity is successfully created in CRM and ready for further processing.

Benefit

• Registers customer requests at the beginning of the journey.
• Ensures correct NTB/ETB classification.
• Standardizes CRM initialization across channels.

2. Update Lead / Opportunity to Close Won

API
POST /integration-service/int/api/crm/v1/combo-update-lead-opportunity

Purpose

To update the status of a Lead (New Lead) or Opportunity (New Opportunity) to the final status Close Won, including converting a Lead into an Opportunity.

Scenario

A customer successfully completes onboarding or product approval on the channel.

System Action

• The channel system invokes the
  /combo-update-lead-opportunity API to CRM.
• The service:
  • Updates Lead or Opportunity status to Close Won.
  • Converts Lead into Opportunity if required.

Outcome

The Lead/Opportunity is closed successfully as Close Won in CRM.

Benefit

• Reflects successful business completion.
• Keeps CRM synchronized with channel processing.
• Supports sales and performance reporting.

3. Update Opportunity Status to Close Lost

API:
POST /integration-service/api/crm/v1/update-opportunity-status

Purpose

To update an Opportunity status to Close Lost when the customer is rejected by NCB.

Scenario

An ETB customer’s request is reviewed and rejected after checking anti-laundering money.

System Action

• The channel system invokes the
  /update-opportunity-status API to CRM.
• The service updates the Opportunity status to Close Lost.

Outcome

The Opportunity is marked as Close Lost in CRM.

Benefit

• Accurately reflects rejected cases.
• Improves CRM data quality.
• Supports rejection analytics and reporting.

4. Update Lead Status to Close Lost

API:
POST /integration-service/api/crm/v1/update-lead-status

Purpose

To update a Lead status to Close Lost when an NTB customer is rejected by NCB.

Scenario

An NTB customer fails onboarding after checking anti-laundering money.

System Action

• The channel system calls the
  /update-lead-status API to CRM.
• The service updates the Lead status to Close Lost.

Outcome

The Lead is marked as Close Lost in CRM.

Benefit

• Completes the Lead lifecycle properly.
• Ensures accurate CRM reporting.
• Eliminates stale open leads.