seankearney
commented
3 years ago I've had a similar response from Intercom regarding their .NET SDK in January 2021.
Our Product Team with responsibility for our Developer Platform has recently finalised their Roadmap for the next two quarters. Given the sheer number of items that jockey for position, some pretty tough trade off calls have been made. One such trade-off was the decision, at this time not to further develop our .NET SDK. While this is the decision for the immediate roadmap, it is not necessarily a long term decision and may be reviewed again in future.
I wrote a letter to Intercom support in September 2020 and received an answer right after:
My question: "Hey, why do you have such a poor support for intercom dotnet library ? Last change was 2 years ago. Do you have some other library you are supporting and I cannot find? Or do people rarely integrate with your application through API ?"
Answer: "Hey Julius 👋 Thanks for getting in touch. The primary reason that the DotNet SDK is not updated is due to a lack of manpower and resources that we have available. We do not have any DotNet specialists in Intercom, so updates are provided ad hoc. There are a number of dependencies that need to be updated before we can release a newer version of the API on this platform. I'll make sure to flag this with our Product team to bring this to their attention, but to set expectations, this isn't a priority for them at the moment. The ruby and php libraries would be the two SDKs updated most frequently, but here's the full list of available SDKs for reference. Hope that helps."
Seems like still no fixes/commits since then, so I assume this is a dead project