Draft where the work already happens
Menus, events, news and hours are drafted inside the ERP by the people who own that content, not emailed to someone else to publish.
Menus, events, news and service hours, drafted by your team, approved before they go out, and live on the client portal and the branded app within seconds.
Built on the Konetic One ERP, this module shares one record across the whole org. No duplicate data entry, no third-party tools to stitch together, and no version-control surprises at audit time.
Community services providers publish a constant stream of small, time-sensitive content.
This week's meal menu, an upcoming social outing, a change to service hours over a public holiday, a news update about a program change. Handled by email and noticeboard, that content is stale by the time it reaches a client or family member.
Konetic One's live feeds module gives your team a structured place to draft that content, route it through an approval step, and publish it straight to the client portal and your branded mobile app. A feed is a channel with a content type, menu, event, news or hours, and every item drafted against it carries its own publish and expiry window.
Nothing goes live without someone approving it, and every submission, approval and rejection is written to a permanent audit trail, so the person who asks why a menu changed gets an answer instead of a guess.
Outcome-first design. Every interaction is in service of a measurable result.
Menus, events, news and hours are drafted inside the ERP by the people who own that content, not emailed to someone else to publish.
Every item moves through a submit and approve step before it reaches a client, so a typo or an unconfirmed change never reaches a family member first.
An approved item pushes to the client portal and the branded mobile app together, so there is never a version mismatch between the two.
A typical end-to-end flow inside the module.
Name, slug and content type set once.
Title, details, publish and expiry window.
Item enters the shared approvals queue.
Approve to publish, or reject with a reason.
Pushed to the portal and the branded app.
Who drafted, approved and when.
Each capability is included. Open any one for the deep dive.
What a week of publishing looks like from draft to the client portal and the app.
Every item passes through the same four stages, regardless of content type.
The same publish action reaches every destination, and the trail behind it is permanent.
No item is visible to a client or family member until a second person has approved it.
Every draft, submission, approval and rejection is retained with who and when.
The client portal and your branded app always show the same approved version.
A menu, an outing or a change in service hours looks like low-stakes content, until a family member acts on the wrong version and a provider has to explain the gap. Live feeds treats publishing as a controlled workflow rather than a casual update.
Every item is drafted, submitted, and either approved or rejected with a reason, and none of those states can be skipped from the client-facing side. That is the same discipline providers already apply to clinical documentation, applied to the content that clients and families actually read day to day.
When a regulator or a quality committee asks how a menu change was communicated, the answer is a timestamped record, not a recollection of who sent what email.
Providers that maintain a website, a portal and a mobile app separately inevitably end up with content drifting between them, an outing listed on the app but missing from the portal, or a menu updated in one place and not the other. Konetic One's live feeds publish to the client portal and the branded mobile app from the one approved item, so there is exactly one version of the truth at any moment.
Publish and expiry windows are set on the item itself, so time-sensitive content, this week's menu, a one-off event, a temporary change in hours, retires itself without anyone having to remember to take it down. The feed becomes the single channel your organisation uses to talk to clients and families, with governance built into how it gets there rather than bolted on afterwards.
Three real-world examples drawn from Konetic One customer setups.
The kitchen coordinator drafts the week's menu against the meals feed. A clinical manager reviews it for dietary flags before approving, and the approved menu appears in the client portal and the branded app at the same moment, replacing last week's version everywhere at once.
A program coordinator drafts an upcoming social outing as an event item with a start time and RSVP note. Once approved, it appears in the app for subscribed families and on the client portal, without a second copy being typed into a newsletter or noticeboard.
A single hours feed is updated ahead of a public holiday and approved by an operations lead. Every site's clients see the same change in the portal and the app, removing the risk of one site publishing an update that another site forgets.
Native to Konetic One, open to everything else.
Menus, events, news and service hours, each with fields suited to that content, service date and dietary notes for menus, start and end time for events, and so on.