Sales CRM for Telecommunications functional architecture

  • Release version: Australia
  • Updated June 16, 2026
  • 3 minutes to read
  • Summarize
    Summarized using AI
    This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete.

    Summary of Sales CRM for Telecommunications functional architecture

    Sales CRM for Telecommunications is a specialized order management solution tailored for telecommunications service providers. It functions as a central orchestration layer within the telecom ecosystem, integrating various customer-facing channels, supporting systems, and fulfillment platforms to manage the entire customer journey from prospecting to service activation. This solution adheres to TeleManagement Forum (TMF) standards to streamline order management across selling and fulfillment phases.

    Show full answer Show less

    Core Components

    The solution’s foundation relies on key data entities that support all stages of order management:

    • Account: Customer account and organizational hierarchy information.
    • Contact: Customer contact details and relationships.
    • Location/Site: Service delivery sites.
    • Product Model: Product definitions based on the Product-Service-Resource (PSR) framework.
    • Sold Product: Customer’s purchased products and entitlements.
    • Install Base Item: Configuration of customer products.
    • Entitlements: Rights associated with sold products.
    • Contracts: Customer contracts including assets covered.

    Functional Phases

    Selling Phase

    This phase manages customer acquisition and order capture, including:

    • Lead and opportunity management
    • Product catalog and configuration
    • Sales agreements and contract management
    • Shopping cart, quoting (CPQ), and final order submission

    During selling, the CRM integrates with digital channels, self-care portals, product catalogs, and service feasibility systems to provide a seamless customer experience.

    Fulfillment Phase

    After order capture, the fulfillment process includes:

    • Order decomposition into service and work orders
    • Service order lifecycle tracking
    • Activation handoff to external provisioning systems

    The solution coordinates with field service management, inventory systems, and network activation platforms but does not perform network activation itself.

    API Integrations

    The architecture leverages TMF Open APIs to ensure standardized and flexible integration with third-party systems:

    • Product Catalog Management API: Manage product catalogs externally.
    • Product Inventory API: Support order submissions from CRM or CPQ systems.
    • Service Catalog API: Synchronize technical specifications with network provisioning catalogs.
    • Service Order API: Manage service orders in collaboration with other applications or marketplaces.
    • Technical Service Qualification API: Verify resource and service availability before fulfillment.
    • Quote Management API: Handle quoting based on TMF 648 standards.

    Additional non-TMF APIs support entitlement management, lead management, order processing, and sales agreements, facilitating comprehensive CRM functionality.

    Sales CRM for Telecommunications is a comprehensive order management solution designed specifically for telecommunications service providers. Sales CRM for Telecommunications serves as a critical orchestration layer within the larger telecommunications ecosystem, integrating with key systems to manage the complete journey from prospect identification to service activation.

    Sales CRM for Telecommunications in the Telecommunications ecosystem

    Sales CRM for Telecommunications is a critical application in the telecommunications industry, serving as the central orchestration layer for order management. It acts as a central hub connecting various systems across the telecom operator's landscape:

    • Customer-facing channels: Mobile apps, web portals, and sales representatives.
    • Supporting systems: Product catalogs, inventory systems, and service qualification platforms.
    • Fulfillment systems: Field service management and network activation platforms.

    Sales CRM for Telecommunications leverages TeleManagement Forum (TMF) industry standards to manage telecommunications orders across both selling and fulfillment phases while integrating with multiple upstream and downstream systems.

    Foundation components

    Sales CRM for Telecommunications is built on the following core data entities that underpin the entire order management process:

    • Account: Customer account information and organizational hierarchy.
    • Contact: Customer contact details and relationships.
    • Location/Site: Service delivery locations and site information.
    • Product Model: Product specifications and definitions created using the Product-Service-Resource (PSR) framework.
    • Sold Product: Customer's purchased products and entitlements
    • Install base item: Customer's product configuration.
    • Entitlements: Entitlements associated with the sold products.
    • Contracts: Customer contract including account details and specific assets covered.

    These foundational elements provide the essential data structures that support all operations, from lead management through service activation. The Sales CRM for Telecommunications functional architecture operates across two distinct phases: the Selling Phase and the Fulfillment Phase.

    Selling phase

    This phase covers the customer acquisition and order capture process:
    • Lead Management: Initial prospect identification
    • Opportunity Management: Sales opportunity qualification
    • Product Catalog: Product offerings and configurations
    • Sales Agreement: Pre-sales contractual arrangements
    • Shopping Cart: Customer selection management
    • Quote: Pricing and proposal generation (CPQ)
    • Contract: Post-sales contractual obligations
    • Order Capture: Final order submission

    During this phase, Sales CRM for Telecommunications integrates with digital apps, self-care portals, account managers, product catalogs, and service feasibility systems.

    Sales CRM for Telecommunications: Selling phase

    Fulfillment phase

    After order submission, the next phase is the fulfillment process:

    • Order Distribution: Decomposition into service orders and work orders.
    • Service Order Management: Tracking through activation lifecycle.
    • Activation Handoff: Submission to provisioning systems.

    During this phase, Sales CRM for Telecommunications coordinates with Field Service Management for Telecommunication, external inventory systems, and network activation platforms.

    Sales CRM for Telecommunications: Fulfillment phase

    Note:
    Sales CRM for Telecommunications orchestrates the order management process and submits service orders to downstream activation systems but does not perform network activation or provisioning.

    TeleManagement Forum (TMF) Open APIs

    The Sales CRM for Telecommunications leverages TeleManagement Forum (TMF) Open APIs throughout its architecture, ensuring standards-based integration with third-party systems. Key API integrations include:

    • Product catalog management API: Manage product catalog information from external systems. See Product Catalog Open API.
    • Product inventory API: For ServiceNow applications or external CRM / CPQ submitting orders. See Product Inventory Open API.
    • Service catalog API: For synching technical specifications with other network domain specific provisioning catalogs. See Service Catalog Open API.
    • Service order API: Use when a customer order is handled by another application and Sales CRM for Telecommunications acts as a service order manager. Also use when the marketplace owner handles decomposition and orchestration and sends the order to Sales CRM for Telecommunications for fulfillment. See Service Order Open API.
    • Technical service qualification API: Checks availability of resources and services before an order is submitted for fufillment. See Technical Service Qualification Open API.
    • Quote management API: Based on the TMF 648 API. See Quote Management API.

    Non-TMF APIs