Skip to content
GullySales

Facility management companies · WhatsApp marketing

The site group is where your contract is renewed or lost.

WhatsApp in facility management is operational long before it is promotional: the site group where the client posts a complaint, the deployment message at the start of the shift, the escalation acknowledged in minutes. GullySales sets up how those groups run and keeps business development off broadcast.

Scope, fee, reporting and term are agreed in writing after we have read your brief and spoken to you.

Realistic editorial illustration of facility management companies at work in India

What WhatsApp marketing means

WhatsApp marketing is sending updates, offers and reminders to customers on the app most Indian buyers already check daily. GullySales sets up business WhatsApp, writes the message templates and keeps the list consented and current.

Last updated 14 Nov 2026.

For facility management companies

Where it usually goes wrong, and what we would do.

  • “The site group is the evidence produced at renewal”

    A complaint posted at nine and acknowledged three minutes later is the record that defends your price. A group where the client's message sits unread until afternoon is the record that loses it.

  • “Broadcasting an offer to facilities managers gets you blocked”

    This is a tendered purchase made by a committee, and the number came off a business card rather than from a consent tick. One unwanted broadcast ends a relationship that took a year to build.

  • “Housekeeping and security recruitment already runs on WhatsApp”

    Supervisors fill a shift through their own contacts on their own phones. When a supervisor leaves, the recruitment network and the client group history go too.

What we do

What we deliver for facility management companies.

The work available for this need. We agree the deliverables and responsibilities for your engagement in writing.

  1. A site group standard

    Who sits in each client group, who answers, what an acknowledgement says and what has to become a phone call, agreed with the client at mobilisation.

    Result: Every site group runs the same way, whoever the supervisor is.

  2. Groups held on a company number

    Client and rostering groups moved onto a business number your company controls, so the history stays behind when a person leaves.

    Result: A resignation does not take the client group with it.

  3. A deployment message format for each shift

    Attendance, deployment against the agreed headcount and the tasks completed, written in a form the admin head can forward to their own management.

    Result: Your client has something to show upstairs without asking you for it.

  4. Escalation wording

    What to send the moment a complaint arrives, what not to promise in a chat, and the point at which a message has to become a call.

    Result: A complaint closes in the group instead of climbing to procurement.

  5. Completion photographs for periodic work

    Before and after records for deep cleans, facade cleaning and pest control, posted in the group and filed for the renewal case.

    Result: Work nobody watches being done is evidenced anyway.

  6. A written rule against marketing broadcasts

    What business development may send on WhatsApp and what belongs in an email or a meeting, so no target account is broadcast to by accident.

    Result: Nobody burns an account with an unwanted forward.

How the result is measured

  • Messages delivered
  • Reply rate
  • Enquiries from WhatsApp

Recorded as a baseline before work starts, so every later report has an honest comparison.

What must be in place first

Settle these before a client site group is created.

Who owns the group
Create each site group from the company's account or a registered admin, with two named admins from your side. A group owned by a supervisor disappears when the supervisor leaves.
The client's written agreement on members
Get the client to confirm who joins: your supervisor, site manager and escalation contact, and their own facilities head. Staff names and photographs need the same care.
Staff documents stay out of the chat
Do not post guards' or housekeepers' ID proofs or attendance sheets in a group. Share only what the contract and the client's security team ask for, through the agreed route.
An escalation matrix in writing
Write who answers a complaint, who is next, and what the first reply says. Copy complaints and replies into the contract file when they close, since the chat may not survive to renewal.
What a group can and cannot carry
Groups and the Business API work differently, so check WhatsApp's current business policy before building a shift message system on either. Keep a written fallback for a missed message.

Who it is for

This is written for these facility management companies.

  • Corporate office and IT campus FM providers
  • Mall and retail FM providers
  • Hospital and healthcare facility contractors
  • Residential welfare association service providers
  • Industrial and warehouse FM contractors
  • Integrated single-vendor FM companies

Before you decide

When this may not be the right fit.

  • Clients have not agreed to site groups, and the business uses personal phones for every site message.
  • The plan is to broadcast offers to facilities managers, who would block the number.
  • Site supervisors do not record incidents and closures in the group, so there is no evidence to produce at renewal.

Before you decide

Agree the work. Know how to judge it.

WhatsApp marketing for facility management companies: use these checks to prepare, choose the scope, and review what changes.

Bring the right evidence

Describe how the contact list was collected, what people asked to receive, and which messages are currently sent. Include opt-outs and replies when reviewing campaign performance.

Make the scope clear

Agree the audience, message purpose, sending system, and response owner. Separate promotional communication from order or service updates, and check current platform requirements before launch.

Check the work in use

Test the message with a small appropriate audience before wider use. Check links, reply handling, opt-outs, and whether the response leads to a relevant conversation or order.

Know when to change course

Do not use an unexplained contact list as a shortcut to demand. If recipients do not expect the message, resolve the permission and relevance questions before sending.

These are discussion points, not a fixed package. GullySales confirms the deliverables, responsibilities, fee, and term in writing after reading your brief and speaking with you.

Before we start

What to have ready before the work starts.

The records, access and decisions this work needs from facility management companies. Anything missing is noted in the written scope, with who will supply it.

A list of every site group and its admins
Compile the groups, their members by role and the phone each runs on. Ask supervisors. Without this list we cannot tell which groups are at risk, and the standard would be written for groups we have not seen.
Client agreement to your reading the group
Ask each client contact whether their group may be reviewed for improvement, and keep the reply. Groups hold remarks and sometimes personal details. Where permission is refused, we work from your supervisors' own descriptions and examples with names removed. Keep the reply, as it protects your supervisors if a client later questions why the group was read.
Company numbers and a person who owns them
Provide company SIM cards or business accounts for site groups, and name one person who holds the login. Supervisors leave. If groups remain on personal phones, the history that proves your service disappears with them.
Your rule on photographs and personal data
Decide what staff may photograph and post, including the faces of guards and housekeepers and any client documents. Only the owner can set it. Without a rule, a photograph meant to show completion can expose a client's confidential area.

How it works

How the whatsapp marketing work runs

The work itself, in order. How an engagement starts, from your brief to a written scope, is set out on our method page.

  1. 1

    Read the site groups as they run today

    We start by reading a sample of your site groups with the client's permission and the supervisor's: who posts, how fast complaints are answered, what photographs are sent. You decide which groups we see. What exists afterwards is a plain account of what each group does well and badly, taken from the messages themselves. We also note which messages the client replied to and which went unanswered, since those show what the contact values.

  2. 2

    Sort which numbers belong to the company

    We list every phone that holds a site group and every admin. You tell us which are company numbers and which are personal phones of supervisors. Groups on personal phones leave with the supervisor. What exists afterwards is a list showing which groups must move to a company number before anything else is built.

  3. 3

    Write the standard for a site group

    With your operations head we write a short standard: who is added, who answers, what a deployment message contains, how a complaint is acknowledged and when it moves to a call. You approve it. Supervisors receive it in plain language, and the client's contact sees it when you introduce the group.

  4. 4

    Set the shift message and the escalation wording

    We draft the message format sent at the start of each shift, with names, posts and any absences, and the wording used when a complaint is raised. Your supervisors test them on live sites. You change anything that sounds unlike your people. The aim is a message a client reads once and trusts.

  5. 5

    Agree the rule that keeps sales out

    We write a clear rule that business development does not broadcast offers into client groups or to facility heads, and that any outreach uses another channel. You sign it with your sales lead. Where the client permits a business message, it is a reply to a request, never a broadcast.

Where this fits

Three pieces of sales work, in this order.

This work sits inside sales process design, at stage 0, foundation. The audit comes before it, and sales management keeps it running.

  1. Step 1

    Sales audit

    Find where deals are being lost and what to fix first.

    Start here if you cannot say where orders are lost.

  2. Step 2 · you are here

    Sales process design

    One written way to sell, from first enquiry to repeat order.

    Start here if every salesperson sells differently.

  3. Step 3

    Sales management

    A target, a review routine and someone who owns the number.

    Start here if the team has targets and no routine.

Tell us what you need Your brief is read before we call. Scope, fee and term in writing.

FAQ

Questions owners ask before they call.

Not here? More answers, or ask on WhatsApp.

Should our sales team use WhatsApp to reach facilities managers?
For a conversation already under way, yes. For a first approach to a stranger, no. This buyer expects an email with a company profile attached, and a cold WhatsApp message reads as a small operator.
The client wants our supervisor in their own group. Is that a risk?
It is useful, as long as your operations manager sits in the same group and the supervisor knows what they may commit to. We write that down so nobody agrees to extra scope in a chat.
What if the client's manager posts a complaint at night and nobody replies?
Name a night contact and put hours and an escalation number in the group description. If there is none, say so in the contract. A complaint with no reply is the first thing quoted when renewal is discussed.
Can we share the group's history with the client's auditor?
Only if the contract allows it, and check with the client first. The history may hold staff details and other people's remarks. Export only the dates the audit asks about and remove unrelated messages.
Should we use the WhatsApp Business app or an API service?
For site groups, the ordinary business app on a company phone is enough, because groups are conversations, not broadcasts. An API service suits automated notices to long contact lists and has its own rules. Read the platform's current rules before you choose. We recommend starting with the app and moving only if a clear need appears.
How do we handle a client who posts a complaint at night?
Agree a duty supervisor who sees the group at night and acknowledges with a short message, even if the fix waits until morning. Write the acknowledgement wording in advance. A quick acknowledgement is noticed at renewal. If nobody can cover the night, say so to the client in the standard, so expectations are honest.
How much does it cost?
There is no price list, because the work differs by business. The fee is scoped after we have read your brief and spoken to you, and put in writing before anything starts, split into our time, your media spend and production.
How long is the contract?
The term is agreed in writing after we have spoken, along with the fee and the reporting. It is never a default twelve months, and renewal is decided on the numbers against the baseline recorded at the start.
How soon will we see results?
It depends on the trade, the channel and what is already in place. After we have read your brief and spoken to you, we say what we would expect to move first and how it will be measured against the baseline. Nothing here is guaranteed.
Who will actually do the work?
The person you speak to before anything starts. We work from one office in Nagarbhavi, Bengaluru, with no account managers in between.

Your next practical step

Tell us what you are trying to grow, and we will read it before we call.

Eight short steps, mostly taps. Skip anything you would rather answer on the call.