# Templates to help troubleshooting and support

**URL:** <https://community.interop.io/t/templates-to-help-troubleshooting-and-support/592>\
**Category:** io.Connect Desktop\
**Tags:** Discussion\
**Created:** [June 2, 2026, 1:35pm UTC](https://community.interop.io/t/templates-to-help-troubleshooting-and-support/592 "2026-06-02T13:35:21Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![toni.petrov](https://yyz2.discourse-cdn.com/flex028/user_avatar/community.interop.io/toni.petrov/32/17_2.png) [@toni.petrov](https://community.interop.io/u/toni.petrov)\
**Post date:** [June 2, 2026, 1:35pm UTC](https://community.interop.io/t/templates-to-help-troubleshooting-and-support/592/1 "2026-06-02T13:35:22Z")

</div>

Often when support tries to repro an issue they need the code, but customers understandably can’t share. We were thinking about creating some minimal templates, like small, self-contained sample apps for common integration patterns (Channels, Interop methods, Intents, Workspaces) where you can swap in methods and see if the problem reproduces, to isolate whether an issue is in your code or in the platform/config.  
Would that be helpful?  
What should we start with?

---

<div class="post-metadata">

**Author:** ![sara.courson](https://yyz2.discourse-cdn.com/flex028/user_avatar/community.interop.io/sara.courson/32/43_2.png) [@sara.courson](https://community.interop.io/u/sara.courson)\
**Post date:** [June 8, 2026, 3:46pm UTC](https://community.interop.io/t/templates-to-help-troubleshooting-and-support/592/2 "2026-06-08T15:46:17Z")

</div>

I’m very interested in our clients’ perspectives on this. From a support perspective, I think Workspaces could be a good place to start.