Most organisations do not lack communication channels. There is the intranet, the newsletter, the employee app, a few chat groups, the notice board and, for retirees, a printed magazine. Each new channel promised to finally reach everyone. Each one ended up competing for the same few minutes of attention, and the usage statistics tell the story: a spike at launch, then a slow decline to the people who would have read the news anyway.
The problem is rarely the channel. It is the reason to open it. This post argues that a community portal earns its place through the things people actually use, benefits, vouchers and services, and that news works best as the wrapper around them rather than the main course.
People come back for value
Think about which apps you open without being reminded. Your bank, your train tickets, your loyalty card. They have one thing in common: opening them gets you something. An employee app that mainly carries announcements asks for attention and gives little back.
A benefits portal reverses that. When the place where employees find their discounts, book the company holiday homes or ask for help is the same place that carries the news, people arrive with a purpose and see the news on the way. That is what appsolut ONE is built for: its strategic focus is tangible member and employee benefits, not another communication channel.
What "benefits" means in practice
Take Pannoniqa AG, the fictional manufacturer we use for examples. Its "Pannoniqa Portal" is a Community Portal, the frontend component of appsolut ONE, connected to the Studio, where Pannoniqa decides who its members are. Here is what its people find there.
Partner offers and voucher codes
Pannoniqa has negotiated discounts with local businesses: a fitness studio, an optician, a regional theatre, a bike shop. Each one is a benefit in the Portal, with a clear line saying what it is worth, for example "20% off" or a €30 voucher.
When a member chooses "Redeem", the Portal checks that they are entitled, hands them their voucher code and records the redemption. The partner sees a code, not a membership list. Pannoniqa sees which offers are actually used and can renegotiate the ones nobody wants.
Travel and holiday homes at member prices
Pannoniqa owns holiday apartments by a lake and works with a travel partner for group trips. Members browse the offers by season and catalogue, see what each costs, and send a booking request through a short step-by-step form: the trip, the dates, the room type and who travels along. The request reaches the team that handles bookings, and the member gets a confirmation by email.
Services and help
Not everything is a discount. Members can ask a question, make a membership enquiry when the Portal cannot confirm them, or find the forms they need. Every one of these is a reason to return that has nothing to do with reading the latest announcement.
The right offer for the right person
A portal for everyone does not mean that everything in it is for everyone. The news about the new canteen can be public, while the discounts Pannoniqa negotiated for its people should not be.
In the Portal, content and offers are published for everyone, for signed-in visitors only, or for members alone. Who counts as a member is decided in the Studio: each frontend has one community, and the Pannoniqa Portal is served by "All staff", so active employees and retirees both qualify. Where a narrower group needs a place of its own, it gets its own frontend: the mobile Pannoniqa App serves the community "Active employees".
This also solves a quiet problem of many benefit programmes: proving eligibility. Nobody prints membership cards or checks a spreadsheet at the counter. From release 26.1.2, the Portal signs people in with Login with appsolut, so a person's membership is checked against Pannoniqa's registers when they sign up and again at each sign-in, and a members-only voucher code only reaches someone who is entitled to it.
Communication as the wrapper
None of this makes news unimportant. It changes its position. On the Pannoniqa Portal, the article about the new canteen sits next to the summer holiday offers. The newsletter links to a new partner discount rather than repeating the CEO's letter. Posts, pages and layout blocks are maintained by Portal editors in the Portal's own admin, with drafts, scheduled publishing and translations, so communications teams keep full control over how things look and when they appear.
The effect on reach is noticeable. People who came to book a holiday apartment read the article on the way, including many who would never have opened the newsletter.
Measuring what matters
When the portal is a place where things happen, success becomes measurable in terms that management understands:
- Redemptions per benefit, instead of newsletter open rates.
- Booking requests for holiday homes and trips, instead of page views.
These numbers make the case for a benefits budget, and they show which partners are worth keeping.
Getting started
If you already offer benefits, you have most of what you need: a list of offers, the partners behind them and the people entitled to them. Start with the three or four offers people ask about most, decide whether each is public, for signed-in visitors or for members only, and let the news follow.
The Portal documentation describes the Community Portal, and the Studio documentation shows how members and communities are set up.