WhatsApp Business or the API? Meta's app and platform for a student residence (2026)

The short answer

The app is for one person to answer from a phone; the platform is for software to answer on the residence's behalf. If someone at reception reads everything and only a few messages come in, the app is usually enough. If there are several areas, night shifts and notices that have to reach a specific person, the platform is needed, almost always through a provider.

What follows has been checked against Meta for Developers documentation as of 19 October 2026. Meta changes these rules often, so it is worth looking at them again before signing anything.

Two products with the same name

The WhatsApp Business app is WhatsApp with a business profile: it is installed on a phone, registered with the residence's number and answered by a person. The WhatsApp Business Platform is something else: Meta's route for software to work with WhatsApp. Its main piece is the Cloud API, which sends and receives messages programmatically. What shows up in searches as "WhatsApp Business API" is this.

The documentation for the platform is written for developers, and it asks for four pieces: a business portfolio, a WhatsApp account holding the numbers, a messaging account holding the templates and billing, and an app linked to the portfolio. A residence does not have to build any of that itself: usually a provider does. The term in more detail: WhatsApp Business Platform.

How many people can answer, and how the work is split

The app can be opened on other devices linked to the same number, so several people can read it. But they all read the same inbox: there is no way for the fault to go to maintenance and the meal cancellation to the kitchen, and if two people reply, the resident gets two answers. It works when one person answers per shift.

On the platform, the software does the routing. A message comes in on the residence's number and the program decides where it goes: to the role that covers that area, to whoever is on shift or to management if it is serious. Each member of staff can receive only what is theirs, on their own phone, and the resident still talks to a single number. For a residence with porters, maintenance, kitchen, cleaning and management, this is the difference that shows most.

What can be automated in each

The app comes with tools to help whoever is answering: a greeting message, an away message out of hours, saved quick replies, labels to sort chats and broadcast lists. They save typing the same thing twice, but they understand nothing: the away message goes out the same for a question about gym hours as for a water leak.

The platform has no built-in automation: it has an API on which the software does whatever it is built to do. That can be a menu of buttons, or an AI assistant that reads the message, answers from the residence's house rules, turns a fault into a fault report and passes it to a person when a decision is needed. How well it works depends on the software, not on Meta.

The 24-hour window and templates: who can write first

On the platform, when someone writes to the residence a 24-hour window opens, and it starts again with each of their messages. While it is open, any kind of message can be sent: text, photos, buttons. Once it closes, according to Meta's guide to sending messages, only message templates approved in advance can be sent.

A template is registered with its text and its category (utility, marketing or authentication), and Meta reviews it. According to its templates overview, the review can take up to 24 hours, and a template that keeps getting negative feedback can be paused or disabled. Meta also requires prior consent (opt-in): you only write to people who have agreed to receive messages from that business, with the business's name stated clearly. Meta accepts it being collected in person or on paper, which in a residence fits arrival day.

In the app, the window does not apply: Meta states that what is sent from the app is not subject to it. For a residence, the practical consequence lies in the notices that are not replies: the parcel at the porters' lodge, the fault that has been fixed, the announcement to the whole house. From the platform, each one needs its approved template; from the app, someone has to type them by hand.

What is needed to get started on the platform

There are two routes. One is for the residence to build its own integration with the Cloud API, which Meta provides for anyone building an app that other businesses will not use; in practice, that means having someone to build and maintain it. The other, the usual one, is to come in through a provider, and Meta distinguishes two roles in its Solution Providers overview:

• Solution Partner: provides the full service, can extend a credit line to its clients and invoice them itself for the platform.
• Tech Provider: offers similar services without a credit line. The client adds its own payment method, Meta charges the client for API usage and the provider invoices its own service separately. To become one, the provider verifies its business with Meta and passes the review of its app.

The residence is usually onboarded through Embedded Signup, Meta's flow in which the residence itself connects its account and its number.

Business verification and messaging limits

According to Meta's page on messaging limits, a new business portfolio can message 250 different numbers outside the window in a moving 24-hour period, and the limit is set for the whole portfolio, not for each number. Verifying the business is one of the ways to raise it to 2,000, after which Meta raises it in steps. For a residence with more than 250 places, an announcement to the whole house depends on this.

Keeping the app's number

A residence that already uses the app with its number does not have to lose it. Meta allows a WhatsApp Business app account to be connected to the Cloud API through a Solution Partner or a Tech Provider, while still sending one-to-one messages from the app as the software handles the volume; messages are mirrored on both sides. There are conditions: the app's broadcast lists are disabled and group chats are not synchronised. It is in Meta's guide to onboarding business app users.

What changes for a residence

The question is not which one looks more modern, but how many people and how many areas have to handle that number. Some signs to decide by:

• The app is enough if one person answers per shift, few messages come in and almost all of them are answered on the spot.
• The platform is needed if messages have to be split between porters, maintenance, kitchen and management, if at night whoever is on duty should receive only what is urgent, or if the whole house has to be notified without typing by hand.
• The record matters too: in the app, the history is the chats on one phone; on the platform, the software can keep each request with its time, its owner and its closure.
• And so does data protection: with the platform, a third party processes residents' messages on the residence's behalf, and that is formalised as controller and processor.

The bill changes as well: through the app, Meta does not charge per message, and through the platform it does, for each delivered message according to its category and the number's country. How much that weighs for a residence depends mainly on how many notices go out while the window is closed.

Where Bedel fits

Bedel works on the WhatsApp Business Platform, through the Cloud API. The resident writes to a single number and each matter reaches whoever it belongs to: the technician handles the ticket with buttons from their own WhatsApp and closes it with a photo, and staff have commands such as /paquete (parcel), /averia (fault) or /difundir (broadcast), the last one showing the real number of recipients and asking for "SÍ" (yes) before sending. Notices that have to arrive while the window is closed (the parcel, the status of the fault, announcements) go out as templates.

What it does not do: without an approved template, a message such as the morning "¿Llegas hoy?" ("Are you back today?") does not reach someone whose window is closed, and it does not translate what staff write in the direct chat. More under escalation to people and features.