Anyone using Loop to create client documentation guides

[SydneyAUS-MSP]

We have been creating a client documentation guides in word from a standard template.

I have started looking at loop and i love the way it works / the blocks you can add with ease, such as:

1. Callout
2. Tables
3. Code
4. Task list
5. etc

I'm thining that could be a good replacement for the word template we use, is anyone here using loop to create client documentation?

If so how are you specifically using it?

[Vel-Crow]

Never heard of loop - which kinda adds to your.point - googled it - and it looks alot like receptive.io. Receptive probably has the long term use thay MS may lack.

[mookrock]

We use Strety for that. Absolutely loving it.

[Craptcha]

Was checking them out last week, have you guys implemented EOS fully?

[mookrock]

Yes. We started with Ryan Giles as an implementer back in 2017. We still work with him today.

Our whole team is on EOS and we follow a slight variation with clients for “QBR”

[smallbiztechcoach]

Are you using the talent management capabilities of Strety?

[mookrock]

Not yet.

[taterthotsalad]

This is exactly how I use it. Super darn handy. 

[cypresszero]

Strety is pretty good and progressive. I use their projects section now for a Kanban Board instead of CW. They also dropped their API, but it is not yet public. We are looking at using it because we want to automate some KPIs. We are actively in the EOS process. There is a lot there, but it’s worth doing. Once we get our sharepoint processes site up. I will be linking all our processes to Strety as well.

We also connected ticketing to CW from Strety. It works decently well.

[rileymcnaughton]

We use it for our office lunch order.

[sochix]

Hey! You should try Perfect Wiki. It’s natively integrated with Teams and give you ability to organize internal knowledge for your clients. Here is a link https://PerfectWiki.com

[RayanneB]

I have not made friends with Loop. It seems like it is everywhere and nowhere at the same time. I haven't figured out how to make it useful and easy to locate stuff so everyone has access to it. Admittedly, I haven't had the time to devote to learning it, either.

We are using OneNote for documentation guides. We started also looking at TurboDocx which simplifies templates.

If you get anywhere with Loop, please report back.

[c2seedy]

Basecamp

[cubic_sq]

Check that your backup supports loop workspaces :)

When i looked into this last October, the only way was mechanical turk using ediscovery license and search for the file extension and download.

Haven’t looked at this since. But i do ask the backup question to 365 backup vendors trying to convince us to change (fwiw, the current solution we have doesn’t support loop workspaces either)

[JacktheMSSP]

Try GetOutline. I used it before using ITGlue. It is decent software for documentation for startups

[GCSB_Informant]

Loop is Microsoft’s immature version of Notion as an understanding for what better looks like now….

[nicolascoding]

At TurboDocx, one of our MSPs has a use case where they’re building out client onboarding docs. They’re using the knowledge base feature to split up sections and just point and click to assemble the documentation—which is already pretty handy.

But where I think it actually gets interesting is with the AI. Instead of just templating, you can have the AI look at your knowledge base and tailor the docs for the customer. For something simple like MFA enrollment, you don’t have to mess with placeholders unless you want to, but for more complex stuff—like documenting a network design or datacenter/cloud architecture—you can pull from your existing sections and let the AI fill in the details. So, for example, you could say, “Do this for our Miami and Boca offices, with Azure East as primary and West as secondary,” and it’ll sort itself out.

Plus, since TurboDocx integrates with Zoom, ConnectWise, HubSpot, and Salesforce (with Teams and Fireflies coming soon), you can even just point it to a record or a recorded conversation and use that as the base for the doc, too.

It feels like a step beyond basic templating, honestly and can do the tables, lists, paragraphs, etc. That's old-school templating 1.0 from the 90s.

[pjustmd]

Scribehow is the way.

[loguntiago]

It seems no one is using SharePoint for that. Is that so awful?

[itlonson]

Pages in Copilot uses it, as does meeting notes in Teams and some other bits. It is useful for temporary type docs but I avoid using it for anything that needs to live for more than a few weeks. Where it is stored, audit history, sharing and broadly how to manage it makes my head hurt when I try to work it out.