NDIS Social Media Marketing: What to Post (and What Never to Post)
Families and Support Coordinators check your social media before they refer. Here's how NDIS providers can use Facebook, Instagram and LinkedIn to build trust - and the posts that can damage it.
For NDIS providers, social media is less about going viral and more about being visible, warm and trustworthy. A participant's family may have heard your name from a Support Coordinator - then they look you up. An active page full of real people and genuine values reassures them. A page that hasn't posted since last year raises doubts.
Which platforms matter
- Facebook - still where many families, carers and local community groups are. Great for updates, events and community.
- Instagram - visual stories of your team, activities and values. Popular with younger participants and families.
- LinkedIn - where you connect with Support Coordinators, plan managers, allied health and other professionals. Useful for referrals and recruitment.
You don't need to be everywhere. Do one or two platforms well rather than five badly.
What to post
Your people
Introduce your support workers and team - their interests, why they love the work, qualifications. People choose people.
Your values and approach
What person-centred support means to you, how you match workers, how you include participants' choices.
Community and activities
Community access outings, group programs and local events - shared with consent.
Helpful information
Plain-language tips: how to make a referral, what to expect at intake, how plan reviews work. Useful posts get shared.
Vacancies and capacity
"We have availability for in-home support in Springfield" - clear, honest and useful to coordinators.
Behind the scenes
Training days, new vehicles, staff milestones, team celebrations.
For dozens more ideas, see our 30 NDIS social media post ideas.
What never to post
- Photos or stories of participants without informed, documented consent - see our consent guide
- Identifying details - names, addresses, diagnoses or plan information
- "Inspiration" content that treats disability as tragic or heroic
- Before-and-after comparisons that imply outcomes you can't guarantee
- Complaints or disputes - handle these privately, never in comments
- Pressure to switch providers or criticism of other providers
How often to post
Consistency beats volume. Two to three good posts a week on your main platform is plenty for most providers. Plan a monthly calendar so posting doesn't depend on someone remembering.
Respond like you would in person
Reply to comments and messages promptly and kindly. Move anything personal to a private channel. A respectful, quick reply to a public question shows exactly how you treat people.
Measure what matters
Likes are nice, but track what brings enquiries: profile visits, website clicks, messages and calls. Over time you'll see which posts build trust and which lead to referrals.
Related serviceNDIS digital marketing →Frequently asked questions
How often should an NDIS provider post on social media?
Two to three quality posts a week on your main platform is enough for most providers. Consistency matters more than volume.
Can we post photos of participants?
Only with informed, documented consent, ideally using an accessible or Easy Read consent form, and with the right to withdraw consent at any time.
Should we use Facebook ads?
They can help promote vacancies and programs. Keep ads honest and respectful, and note that platforms restrict some targeting around health and disability.
Who should manage our social media?
Someone who understands your values and the NDIS rules - an in-house team member or an agency that knows the NDIS. Have a clear approval process for anything involving participants.
Get a free social media check
We'll review your Facebook, Instagram and LinkedIn and call you with three quick wins.
- Free and no obligation
- Practical advice for your NDIS business
- A call back within one business day
Call 0450 501 772
Email contact@digitalrabbit.com.au
Monday to Friday, 9am - 6pm
Request a call-back
Fields marked * are required.