Duplicate Customer & Subscriber Identity
CRM, billing, channels and service systems may represent the same party or subscription with different identifiers and relationship structures.
Telecom Data & AI Capability
Telecom Master Data Consulting for Trusted Customer, Service & Network Identity
Design a governed master and reference data capability that connects telecom customer and subscriber identity with products, services, network resources, locations, identifiers and partners across BSS, OSS, analytics and AI. DataConsultant helps operators move from conflicting IDs and local reference lists to controlled mastering, stewardship, quality and distribution.
✓Authoritative-source, matching and survivorship design
✓Customer, product, service, resource, location and identifier domains
✓Stewardship, quality controls, hierarchy and reference-data governance
✓Implementation-ready architecture across BSS, OSS and data platforms
Vendor-neutral consulting. Platform selection, licensing, migration execution and managed operations are included only when explicitly scoped.
Party & CustomerIdentity, contact, segment, relationship
Subscriber & AccountSubscription, account, service association
Product & OfferSpecifications, bundles, catalogue hierarchy
ServiceCustomer-facing and resource-facing service
Network ResourceLogical and physical resource identity
Location & SiteAddress, serviceability, site hierarchy
Identifier & NumberNumber, SIM/eSIM, device and cross-system IDs
Partner & ReferencePartner, code lists, statuses, classifications
Source Systems
- CRM / Customer Care
- Catalogue / Order
- Billing / Charging
- OSS / Inventory / GIS
→
Master & Reference Hub
- Standardise & validate
- Match & resolve identity
- Golden record & crosswalk
- Hierarchy, stewardship & change
→
Consumers
- BSS / OSS operations
- APIs / events
- Warehouse / lakehouse
- Analytics / AI
Data QualityMetadata & LineagePrivacy & SecurityAudit & Change Control
Mastering LogicAuthoritative sources, crosswalks, match confidence, survivorship and golden-record rules.
Quality & StewardshipCritical elements, rules, exceptions, owners, hierarchy change and remediation workflows.
BSS / OSS IntegrationCanonical mappings and governed distribution across operational and analytical consumers.
Analytics & AI ReadinessConsistent entity, service, resource and location context for approved analytical and AI use cases.
1
Why Telecom Master Data Breaks Across Connected BSS and OSS Journeys
The same customer, offer, service, location, resource or identifier can be created, transformed and referenced by many systems. When authority, semantics and change control are unclear, operational processes spend effort reconciling identity instead of using it.
Product, Offer & Service Drift
Catalogue definitions, orderable offers, activated services and downstream billing or assurance codes can diverge as products change.
Fragmented Resource & Location Context
Network inventories, GIS, site registers and service inventories can carry inconsistent resource, topology, site and service relationships.
Uncontrolled Identifiers & Reference Lists
Numbers, SIM/eSIM identifiers, status codes, equipment types and local classifications can be managed in disconnected lists.
Point-to-Point Synchronisation Debt
Multiple interfaces apply different mappings and precedence logic, making changes expensive and lineage difficult to explain.
Current state: identity is implicit in systems
- Conflicting customer, subscriber and account IDs
- Unknown or disputed source precedence by attribute
- Local product, service, resource and status code lists
- Manual cross-system reconciliation and correction
- Weak ownership for hierarchy and reference-data change
- Analytics and AI inherit inconsistent entity context
Target state: master data is governed and distributable
- Canonical domains, keys, relationships and business definitions
- Documented authoritative sources and survivorship policy
- Golden records, crosswalks and controlled hierarchies
- Stewardship workflow for exceptions and approved changes
- Quality, lineage, audit and access controls built into the lifecycle
- APIs, events or batch distribution aligned to consumer needs
Find Where Telecom Identity Is Being Reconciled Instead of Governed
Start with the domains, systems and operational decisions where duplicate IDs, conflicting hierarchies, reference-data drift or manual correction create the most risk and effort.
2
Master Data Across the Telecom Customer-to-Service Value Chain
Telecom Master Data carries identity and relationship context through commercial, service and network processes, then supplies consistent dimensions to billing, assurance, analytics and AI.
Prospect & CustomerParty identity and relationship
Onboard & IdentifyIdentifiers and verified attributes
Account & SubscribeAccount, subscription and number
Product & OfferCatalogue and bundle hierarchy
Order & ActivateProduct-to-service relationship
Service & ResourceInventory and network context
Usage & BillingTransactions consume master keys
Assure & SupportService, resource and customer view
Retain & OptimiseAnalytics and AI context
Cross-cutting: canonical identity • product/service/resource relationships • location and number hierarchies • reference codes • stewardship • quality • lineage • access • change control
3
Priority Telecom Master Domains and the Relationships That Must Stay Intact
The design starts with business entities and relationships, not an MDM tool. Domain boundaries are tailored to the operator’s business model and can be aligned with telecom information models where useful.
Party / CustomerPerson, organisation, contact, relationship, segment and role.
Account / Subscriber / SubscriptionCommercial account, subscription, subscriber identity and lifecycle state.
Partner / SupplierPartner identity, roles and controlled external relationships.
Reference DataStatus, reason, geography, equipment, service class and governed code sets.
Telecom Identity & Relationship Spine
Explicit keys and governed relationships connect commercial intent to activated services and network resources.
Customer / Account↔Subscription / Product
Product / Offer↔Service
Service↔Resource / Network
Resource / Service↔Location / Site
Subscriber / Service↔Number / SIM / Device ID
Product / Offer / CatalogueSpecifications, offers, bundles, eligibility, hierarchy and lifecycle.
ServiceCustomer-facing and resource-facing service identity and relationships.
Network ResourceLogical and physical resources, resource classes and inventory crosswalks.
Location / Site / IdentifierAddress, site, geography, numbers, SIM/eSIM, device and external IDs.
4
Telecom Master Data Scope: From Source Authority to Governed Distribution
DataConsultant can assess, design and help implement the rules, architecture and operating practices that keep core telecom entities consistent across their lifecycle.
What DataConsultant Does
Make the rules of identity explicit
We bring business owners, BSS/OSS specialists, data teams and architecture together to define what each master entity means, where it is created, how duplicates are resolved, how changes are approved and how trusted records reach consumers.
- Domain, identifier, key and relationship model
- Source authority and precedence by domain or attribute
- Standardisation, match, merge and identity-resolution rules
- Attribute survivorship, crosswalk and hierarchy management
- Reference-data ownership, versioning and change control
- Stewardship, exception, approval and issue workflows
- Quality, lineage, audit and access requirements
- Integration, publication and consumer contracts
Mastering Lifecycle
From source records to controlled consumption
01ProfileIDs, attributes, duplicates and quality
02StandardiseFormats, codes and canonical values
03MatchCandidate logic, confidence and exceptions
04SurviveGolden attributes and crosswalks
05StewardReview, hierarchy and controlled change
06PublishAPIs, events or batch distribution
07MonitorQuality, lineage and exceptions
Primary Buyer
Chief Data Officer, Head of Data, CIO/CTO, telecom transformation leader, Head of Data Governance or MDM lead accountable for cross-domain consistency and investment decisions.
Critical Stakeholders
Customer operations, product/catalogue, billing, revenue assurance, OSS/network operations, architecture, integration/API, analytics/AI, security, privacy and risk teams.
Not Automatically Included
Full platform procurement, software licences, enterprise-wide data cleansing, migration execution, production support, legal opinions, formal audits and security testing are separate unless commissioned.
5
A Telecom Master Data Architecture That Connects BSS, OSS and Data Platforms
The target pattern separates source ownership, mastering logic and consumer distribution. The precise technology depends on the current estate, but the control points should remain explicit whether mastering is registry, consolidation, coexistence, centralised or hybrid.
Cross-cutting controls: identity & access • privacy • data quality • metadata & lineage • audit evidence • change control • observability
1. Telecom Sources
Systems that create or maintain operational identity and reference values.
CRM, customer care & digital channels
Product catalogue & order management
Billing, charging & mediation
Service / resource inventory & provisioning
Number management, GIS, partner & ERP data
2. Integration & Canonical Mapping
Controlled movement and mapping before records are mastered or distributed.
API management and service contracts
Events, streaming and change-data capture
Canonical payload and identifier mappings
Validation, quarantine and reconciliation
Batch integration where operationally appropriate
3. Master & Reference Data Hub
The governed identity and relationship layer for selected telecom domains.
Domain, relationship and hierarchy model
Standardisation, match and identity resolution
Golden-record survivorship and source crosswalks
Stewardship, approvals and exception workflow
Reference data, quality rules and evidence
4. Operational & Analytical Consumers
Consumers receive governed identity using the pattern that fits their latency and process needs.
CRM, billing, order and service operations
Service assurance and network operations
Warehouse, lakehouse and semantic layers
Revenue assurance and reporting inputs
Analytics, ML and GenAI where approved
Source authorityMatch confidence & exceptionsConsumer reconciliationHierarchy/reference changeQuality & control monitoring
Where Governed Telecom Master Data Creates Operational Value
The objective is not a golden record for its own sake. Mastering should improve decisions and transactions that depend on stable identity, relationships and codes.
Customer & Subscriber 360 Identity
Resolve party, account, subscription and contact identity across channels, care, billing and service systems while preserving source crosswalks.
Product-to-Service Alignment
Keep product specifications, offers, bundles, orderable components and activated services connected as commercial portfolios evolve.
Service & Resource Inventory Alignment
Clarify service-to-resource relationships and canonical resource identity where inventories, provisioning and assurance views disagree.
Site & Serviceability Mastering
Govern address, site, geography and serviceability identifiers used across customer fulfilment, field operations and network planning.
Number, SIM/eSIM & Device Reference Control
Define ownership, status, lifecycle and cross-system mappings for identifiers that connect subscribers, services and devices.
Billing & Revenue Assurance Context
Provide stable product, account, service and reference keys so reconciliation can distinguish business exceptions from identity defects.
Partner & Reference Data
Control shared partner identities, statuses, reason codes, classifications and other values reused across operational workflows.
Trusted Entity Context for Models
Give churn, next-best-action, service assurance and network-optimisation use cases more consistent entities and labels without treating mastering as a substitute for model governance.
Connect the Mastering Rules to the Systems That Must Consume Them
Map where telecom identity is created, reconciled, approved and distributed so architecture decisions are grounded in real BSS, OSS and analytical dependencies.
6
Governance, Data Quality, Privacy and Control for Telecom Master Data
Master-data design becomes sustainable when the ownership, control objective, evidence and remediation route are clear. The control model should reflect the sensitivity and operational importance of each domain rather than applying one rule to every attribute.
| Control Area | Telecom Question | Design Response | Evidence / Monitoring |
|---|---|---|---|
| Ownership & stewardship | Who can decide the definition, hierarchy and acceptable quality of customer, product, service, resource or identifier data? | Domain owner, data steward, decision rights, escalation and forum cadence. | RACI, approvals, issue log and governance decisions. |
| Source authority | Which system is authoritative for each identifier and attribute, and when may another source override it? | Source-of-record matrix, attribute precedence, crosswalk and survivorship policy. | Rule catalogue, match/merge decisions and exception history. |
| Data quality | Which defects can block activation, billing, assurance, care, reporting or analytics? | Critical elements, business rules, severity, reconciliation and remediation workflow. | Scorecards, exception queues, trends and owner sign-off. |
| Hierarchy & reference change | How are product, service, resource, geography, status and code-list changes introduced safely? | Versioning, effective dating, approval, impact assessment and controlled publication. | Change records, versions, approvals and downstream acknowledgement. |
| Privacy & access | Which party, subscriber, contact, location and identifier attributes require restricted handling? | Purpose-aware access, minimisation, segregation, retention and sharing controls as applicable. | Access records, policy mapping, classifications and review evidence. |
| Distribution & reconciliation | How do consumers know they received the correct mastered value and can recover from failed synchronisation? | Consumer contracts, version markers, delivery pattern, retries, reconciliation and observability. | Delivery logs, reconciliation results, exceptions and incident records. |
7
A Telecom Master Data Operating Model With Clear Decision Rights
Technology can automate matching and distribution, but the organisation still needs accountable roles for meaning, source authority, exceptions, hierarchy change, controls and prioritisation.
Domain Owner
Approves domain definition, critical attributes, policy decisions, quality expectations and major exceptions.
Data Steward
Reviews exceptions, hierarchy/reference changes, disputed matches, issue remediation and evidence.
BSS / OSS SMEs
Explain operational semantics, lifecycle events, system behaviour and downstream process consequences.
Architecture & Data Platform
Own integration patterns, canonical models, platform design, observability, deployment and non-functional requirements.
Security, Privacy, Risk & Control
Define applicable access, handling, evidence, change-control and risk requirements with accountable business teams.
AI and Model Dependency
When AI consumes mastered entities or labels, record the data dependency, approved purpose, access boundary, evaluation requirements and model-governance ownership. Better master data can reduce avoidable inconsistency but cannot guarantee model accuracy.
Metadata and Lineage
Document where mastered attributes originate, the rules applied, record crosswalks, hierarchy changes and the consumers that receive each published representation.
Security and Segregation
Separate stewardship permissions, platform administration, business approval and sensitive attribute access so convenience does not override control design.
8
How DataConsultant Delivers a Telecom Master Data Engagement
The method moves from business and system evidence to explicit mastering rules, architecture, implementation decisions and operational ownership. The sequence is tailored to the number of domains and the maturity of the current environment.
Define
Align the business problem, target telecom processes, domains, decisions and scope boundaries.
- Executive and domain objectives
- Priority operational pain points
- Domain and stakeholder scope
- Success and acceptance criteria
Discover & Profile
Build evidence across systems, identifiers, relationships, quality, interfaces and existing controls.
- BSS / OSS source inventory
- Data profiling and duplicate patterns
- Data-flow and interface review
- Policy, issue and control evidence
Model & Decide
Make the domain model and the rules of telecom identity explicit with accountable owners.
- Keys and relationship model
- Source authority and precedence
- Match, merge and survivorship
- Hierarchy and reference-data rules
Design & Prioritise
Design stewardship, controls, target architecture, rollout options and a sequenced backlog.
- Quality and control catalogue
- Stewardship workflow
- Integration and publication design
- Implementation dependencies
Enable & Operate
Support implementation, acceptance, rollout, knowledge transfer and sustainable operations.
- Implementation assurance
- Test and reconciliation design
- Operating cadence and metrics
- Continuous-improvement backlog
9
Tangible Telecom Master Data Deliverables
Outputs are decision artefacts and implementation assets, not presentation-only recommendations. The exact pack is agreed during scoping and only includes artefacts needed for the selected domains.
Current-State Assessment
Evidence-led view of domain, source, duplicate, quality, control and operating-model gaps.
Source & Identifier Map
Systems, authoritative attributes, cross-system keys, flows and reconciliation points.
Domain & Relationship Model
Telecom entities, identifiers, relationships, hierarchies and business definitions.
Mastering Rulebook
Standardisation, matching, precedence, survivorship, crosswalk and exception rules.
Stewardship Workflow
Decision rights, queues, approvals, escalation and hierarchy/reference change workflow.
Quality & Control Catalogue
Critical elements, validation, reconciliation, evidence and remediation ownership.
Target Architecture
Source, integration, MDM/reference hub, publication and consumer-control design.
Target Operating Model
Ownership, stewardship, architecture, security, privacy and governance responsibilities.
Implementation Backlog
Prioritised domain, rule, interface, workflow, quality and migration work items.
Executive Roadmap
Sequenced decisions, dependencies, rollout waves, risks and mobilisation next steps.
Stabilise Identity
Resolve the highest-impact identifier, authority and reference-data gaps that block decisions.
Master Priority Domain
Implement the domain model, match/survivorship policy, stewardship and quality controls.
Connect BSS / OSS
Publish governed identity through controlled APIs, events or batch patterns and reconcile consumers.
Expand Relationships
Add adjacent domains and product-service-resource-location relationships where business value justifies it.
Operate & Improve
Monitor quality, exceptions, change, adoption and the backlog as the telecom estate evolves.
Roadmap phases are illustrative. Timeline is confirmed after scoping and depends on domains, systems, data condition, platform involvement, migration, controls and rollout depth.
Turn Telecom Master Data Decisions Into an Implementation-Ready Backlog
Define the domain model, source authority, matching logic, quality controls, stewardship workflow and integration changes required before platform work accelerates.
10
What We Need From You — and How We Support Implementation and Operations
The most useful evidence is the evidence that explains real telecom decisions and exceptions. Missing inputs are recorded as limitations rather than silently assumed.
Useful Client Inputs
Inputs vary by scope. DataConsultant may request a practical subset of the following.
Business sponsors & domain ownersAccountable decisions and priorities
BSS / OSS subject-matter expertsOperational lifecycle and semantics
System & interface inventoryCRM, billing, catalogue, inventory and integrations
Data inventory & samplesIdentifiers, attributes, duplicates and relationships
Architecture & data flowsCurrent integrations and consumer dependencies
Quality and issue evidenceProfiling, reconciliation, defect and incident history
Policies, standards & controlsOwnership, privacy, security and change requirements
Metadata, lineage & modelsExisting definitions and source-to-consumer traceability
From Design to Sustainable Capability
DataConsultant can stay involved beyond the assessment when implementation or operational continuity is required.
Implementation Support
- Backlog and requirements refinement
- Platform and tool requirements
- Canonical model, API and event design
- Match/survivorship rule configuration support
- Data-quality and reconciliation design
- Migration, testing and acceptance assurance
- Stewardship workflow and rollout
- Knowledge transfer and mobilisation
Ongoing Operational Support
- Stewardship operations and exception triage
- Quality and control monitoring
- Reference-data and hierarchy change
- Metadata and lineage maintenance
- Governance cadence and reporting
- Improvement-backlog management
- Runbook and knowledge maintenance
- Transition or managed-operations support
Service boundaries are explicit. Production support windows, service levels, operational responsibilities and exit/transition arrangements are defined only in an agreed managed-service scope; none are assumed on this page.
11
Custom Scope & Pricing for Telecom Master Data
DataConsultant does not publish a fixed fee for this exact Telecom Master Data service on this page. A reliable quote requires enough discovery to understand the domains, systems, controls and implementation depth involved.
Scope-led enterprise engagement
Pricing is confirmed after the required decisions, evidence, stakeholder coverage, platform involvement and deliverables are understood. Timeline is also confirmed after scoping.
Third-party costs: MDM software licences, cloud consumption, data tooling and external implementation costs are separated from DataConsultant consulting scope unless explicitly included. Vendor pricing can change and is not hard-coded here.
Scope factors that materially affect effort
Number and complexity of master/reference domains
Customer, subscriber and identifier match complexity
BSS, OSS and enterprise source-system count
Product, service and resource hierarchy depth
Geographies, legal entities and business units
Data volumes, duplicates and remediation needs
Current MDM, integration and data-platform environment
Privacy, security, risk and regulatory-control requirements
API, event, batch and consumer-integration scope
Migration, coexistence and rollout requirements
Workshops, governance setup and training
Implementation and ongoing managed-operations depth
12
When Telecom Master Data Is the Right Starting Point — and When It Is Not
A focused master-data engagement is valuable when identity, hierarchy and reference consistency are the core problem. It should not be used as a generic label for every data-platform or governance issue.
Good fit for this service
- Customer or subscriber duplicates cause cross-system reconciliation and service issues.
- Product, offer, service or resource identities disagree across BSS and OSS.
- Source authority, match, merge or survivorship decisions are undocumented or disputed.
- Reference lists and hierarchies are changed locally without governed publication.
- An MDM platform exists but stewardship, rules, quality or adoption are weak.
- A new MDM capability needs business-led requirements and implementation design.
A different or adjacent service may be better
- The main issue is broad enterprise data governance rather than entity mastering.
- The priority is only data-quality monitoring with no cross-system identity requirement.
- The immediate need is metadata catalogue or end-to-end lineage implementation.
- The problem is mainly cloud-platform performance, cost or architecture modernisation.
- The scope is specifically AI model governance rather than source/master-data consistency.
- The requirement is a legal opinion, statutory audit or formal compliance certification.
Scope the Domains, Systems and Decisions Before Choosing the Delivery Model
Whether you need a focused diagnostic, target design, implementation support or ongoing stewardship operations, begin with the telecom master-data boundary and the decisions it must improve.
14
Telecom Master Data Frequently Asked Questions
Questions enterprise data, technology, operations and governance buyers commonly need answered before scoping a Telecom Master Data engagement.
What is Telecom Master Data?
Telecom Master Data is the governed set of relatively stable business entities, identifiers, hierarchies and reference values that must remain consistent across telecom business and operational systems. Depending on the operator, priority domains can include party and customer, account, subscriber or subscription, product and offer, service, network resource, location, identifier or number, partner and controlled reference data.
What does DataConsultant’s Telecom Master Data service include?
The service can include business and source-system discovery, domain and identifier modelling, authoritative-source analysis, matching and identity-resolution design, survivorship rules, hierarchy and reference-data governance, stewardship workflows, data-quality controls, target architecture, distribution patterns, implementation backlog and an operating model. Final scope is agreed around the telecom domains and decisions that matter most.
Which telecom processes are affected by master data?
Master data commonly crosses customer onboarding, subscription and account management, product and offer management, order capture, service activation, service and resource inventory, number or identifier management, billing and revenue assurance, customer care, service assurance, partner operations and analytics. The engagement selects only the processes relevant to the agreed domains.
Which telecom data domains should be mastered first?
There is no universal first domain. Prioritisation should consider business impact, duplication, integration dependency, data quality, regulatory or privacy sensitivity, analytics and AI demand, operational pain and implementation feasibility. A common starting point may be customer or party, product and offer, service, resource, location, identifier or reference data, but evidence should drive the sequence.
Can the service work across both BSS and OSS environments?
Yes. The assessment and design can span relevant BSS, OSS and enterprise systems such as CRM, customer care, catalog, order management, billing and charging, service inventory, resource inventory, provisioning, number management, GIS, ERP, integration, data platforms and analytics. DataConsultant does not assume a particular vendor stack unless platform selection or implementation is explicitly in scope.
How are matching, deduplication and golden-record rules designed?
Rules are designed from the semantics and risk of each domain. The work can define identifiers, standardisation, candidate matching, confidence and exception logic, source precedence, attribute-level survivorship, crosswalks, hierarchy rules, stewardship review and audit evidence. Automated matching should retain controlled exception handling where business review is required.
How is telecom master-data quality handled?
Quality is connected to business purpose. The service can define critical data elements, completeness, validity, consistency, uniqueness, integrity and timeliness rules; cross-system reconciliation; exception severity; accountable owners; remediation workflows; and monitoring. Thresholds are agreed with business owners rather than invented as generic targets.
How are privacy, security and telecom regulatory requirements considered?
Depending on jurisdiction, business model, data handled and applicable obligations, the design can incorporate purpose and access boundaries, minimisation, retention, consent or preference context, identifier handling, audit evidence, segregation of duties, data sharing and change control. In India, relevant considerations may include the Digital Personal Data Protection Act and Rules and applicable TRAI or telecommunications requirements. The engagement supports readiness and control design; it does not replace legal advice or guarantee compliance.
How does Telecom Master Data support analytics and AI?
Master data can provide more consistent entity identity, product and service context, location and network-resource relationships, and controlled reference values for analytics and model features. That can reduce avoidable entity and label inconsistency in use cases such as churn, next-best-action, service assurance, fraud or anomaly analysis and network optimisation. Model evaluation, privacy, access and AI governance remain separate requirements.
What deliverables can we expect?
Typical outputs can include a telecom master-data current-state assessment, source and identifier map, domain and relationship model, authoritative-source matrix, matching and survivorship specifications, hierarchy and reference-data model, stewardship workflow, quality-control catalogue, target architecture, target operating model, implementation backlog and phased roadmap. Exact deliverables depend on scope.
Can DataConsultant help implement the Telecom Master Data design?
Yes. Implementation support can be scoped for backlog refinement, data modelling, platform requirements, integration and API design, data-quality rules, migration and reconciliation, stewardship workflow, test and acceptance design, release governance, rollout assurance and knowledge transfer. Platform licences, cloud consumption and third-party implementation costs are treated separately unless explicitly included.
Can DataConsultant provide ongoing Telecom Master Data operations support?
Ongoing support can be scoped around stewardship operations, quality monitoring, exception triage, hierarchy and reference-data changes, metadata and lineage maintenance, control reporting, improvement backlog management and governance cadence. Service boundaries, responsibilities, support windows and any service levels are defined only in an agreed operating scope.
How long does a Telecom Master Data engagement take and how is pricing determined?
Timeline and pricing are confirmed after scoping. Material factors include the number and complexity of master domains, source systems, geographies, identifiers, match volumes, hierarchy complexity, current MDM capability, data-quality remediation, integration and migration requirements, workshops, controls, platform involvement, deliverables, rollout depth and ongoing support. DataConsultant does not publish a fixed fee for this exact service on this page; request a scoped quote.
Request a Telecom Master Data Scope Discussion
Complete the form and include enough detail for an informed first conversation. Fields marked * are required.