Use clear, structured documentation to learn modules, answer common questions, and keep your team aligned on the way Flossly works.
Overview
Docs should reduce uncertainty, not create it. We keep them organized, plain-spoken, and easy to navigate.
The goal is simple: make it easier for teams to understand the platform and confidently use it every day.
Use direct instructions and plain language to reduce confusion.
Help new users understand the platform faster with practical guidance.
Keep topics grouped so users can find the right guide without hunting.
Make sure everyone follows the same process across the practice.
At a glance
Good documentation saves time for the team and makes the product feel more approachable from day one.
A structured reference library covering the things teams use most often.
A guided intro for first-time users and team leads.
Begin with confidence.
How to create, assign, and track work clearly.
Keep ownership visible.
Reference content for CRM processes and follow-up flows.
Make the pipeline easier to use.
Documentation for staff-related workflows and records.
Organize team information.
Guides for working with diaries, appointments, and planning.
Support daily coordination.
How to locate and use files, templates, and references.
Everything in one place.
Start with the basics, then move into the modules and workflows your team uses most often.
Begin with the overview and core concepts.
Use the relevant docs when you need a deeper explanation.
Keep internal workflow consistent by following the same reference material.
Documentation should stay useful as your needs evolve.
A few quick answers for teams using Flossly docs.
Yes. The docs are intended to give teams a clear first step into the platform.
They are designed to help users navigate the major modules and workflows.
Absolutely. They are a practical companion for onboarding and internal learning.
Yes. Documentation should grow as the platform and team needs evolve.
