# Which IRCM platforms integrate best with legacy billing and customer care systems?

<p class="elv-tracking-normal elv-text-default elv-font-figtree elv-text-base elv-leading-base elv-font-normal" elv="true">I’m gathering real-world perspectives on IRCM integration because most telecom operators are modernizing around legacy BSS, OSS, mediation, and customer-care systems rather than starting fresh.</p><ol>
<li>
<a class="a a--md" elv="true" href="https://www.g2.com/products/agentforce-communications-formerly-salesforce-communications-cloud/reviews"><strong>Agentforce Communications</strong></a><strong>:</strong> Offers broad APIs and strong Salesforce integration. How much custom work did deeper telco integrations require?</li>
<li>
<a class="a a--md" elv="true" href="https://www.g2.com/products/oracle-communications-billing-and-revenue-management-brm/reviews"><strong>Oracle Communications BRM</strong></a><strong>:</strong> Integrates natively with Oracle ordering, CRM, inventory, mediation, and middleware. How well does it connect outside Oracle?</li>
<li>
<a class="a a--md" elv="true" href="https://www.g2.com/products/csg-ascendon/reviews"><strong>CSG Ascendon</strong></a><strong>:</strong> Provides 1000+ APIs and can run alongside existing BSS as an adjunct platform.</li>
<li>
<a class="a a--md" elv="true" href="https://www.g2.com/products/amdocs-ces/reviews"><strong>Amdocs CES</strong></a><strong>:</strong> Offers broad carrier functionality, though the overall suite can be expensive.</li>
<li>
<a class="a a--md" elv="true" href="https://www.g2.com/products/ericcson-charging-and-billing-in-one-cbio/reviews"><strong>Ericsson CBiO</strong></a><strong>:</strong> Connects deeply with Ericsson infrastructure but may require costly customization in mixed environments.</li>
</ol><p class="elv-tracking-normal elv-text-default elv-font-figtree elv-text-base elv-leading-base elv-font-normal" elv="true">Which legacy integration caused the most difficulty for your team?</p>

##### Post Metadata
- Posted at: 2 months ago
- Author title: Marketer
- Net upvotes: 1


## Comments
### Comment 1

For teams that have actually connected an IRCM platform to a legacy mediation system, how much of the usage-record formatting mismatch got handled by the platform itself versus custom middleware your team had to build separately?

##### Comment Metadata
- Posted at: 7 days ago
- Author title: Marketing Executive



### Comment 2

Customer care was harder for us than billing, because it&#39;s the system carrying a decade of undocumented local behaviour that nobody wrote down. CSG Ascendon running alongside existing BSS as an adjunct is the pattern that made it survivable, since you&#39;re not forced to cut over care and charging in the same window.

##### Comment Metadata
- Posted at: 8 days ago
- Author title: SEO Content Specialist



### Comment 3

Agreeing on mediation, and worth adding what happens after the integration works: the legacy platform usually remains the system of record for a large part of the in-flight base for years, which means running two billing engines and reconciling them every cycle. That reconciliation, rather than the initial interface, is where the sustained cost sits, and it is what makes the adjunct model worth understanding properly. CSG Ascendon being able to run alongside existing BSS is that pattern named explicitly. Worth asking how subscriber ownership is tracked across the two, since an account existing in both is the one that double bills.

##### Comment Metadata
- Posted at: 17 days ago
- Author title: Tech Consultant



### Comment 4

&lt;p&gt;The legacy integration that tends to cause the most trouble isn&#39;t the CRM or ordering system, it&#39;s mediation, since it sits between the network and the charging engine and every mediation vendor formats usage records slightly differently. I&#39;ve noticed a version of this friction in reviews too: a systems engineer at an enterprise telecom company reviewing Agentforce Communications liked how quickly CPQ and order management could be configured, but specifically flagged that deploying components and resolving bugs took real time, which tracks with how deeper telco-specific integrations tend to need more custom work than the API surface suggests.&lt;/p&gt;

##### Comment Metadata
- Posted at: 2 months ago
- Author title: SEO Content Writer





## Related discussions
- [How well does Trello scale into a larger team?](https://www.g2.com/discussions/1-how-well-does-trello-scale-into-a-larger-team)
  - Posted at: over 13 years ago
  - Comments: 6
- [Can we please add a new section](https://www.g2.com/discussions/2-can-we-please-add-a-new-section)
  - Posted at: over 13 years ago
  - Comments: 0
- [Quantifiable benefits from implementing your CRM](https://www.g2.com/discussions/quantifiable-benefits-from-implementing-your-crm)
  - Posted at: over 13 years ago
  - Comments: 4