Template sync and approval state
Templates are pulled from your Meta Business account with category, language and approval status. A rejected or paused template cannot be scheduled by mistake.
Marketing & lead follow-up
In Bangladesh a property enquiry lives on WhatsApp, not in email. PropERP ships the WhatsApp Business Cloud API natively: Meta-approved templates with merged variables, delivery and read state per recipient, inbound replies attached to the lead, and campaign results measured down to booked units — not clicks.

Most CRMs claim WhatsApp support. In practice it is a bridge: a third-party service sends the message, and the CRM stores a note saying a message was sent. The reply comes back to somebody's personal WhatsApp on their own phone. When that person leaves, the conversation history leaves with them.
That arrangement breaks in three specific ways. Template rejections are invisible until a campaign silently fails. Delivery and read state never reach the buyer record, so nobody knows whether the demand letter reminder was actually seen. And the reply — the only part that matters — is not on the deal.
PropERP connects to the WhatsApp Business Cloud API directly. Templates are synced from Meta with their approval status, sends are recorded per recipient, and the reply arrives on the same timeline as the site visit and the booking.
The approved template with its variables, delivery and read state across the audience, and the funnel from replies through site visits to booked units with the booked value attached.
Marketing / Broadcast — Green Valley launch
Assalamu alaikum {{1}},
{{2}} has 6 units left at {{3}}/sft. Booking money {{4}}. Reply BOOK for a site visit.
Sent
2,140
Delivered
2,061
96.3%
Read
1,488
72.2%
Replied
214
10.4%
| Stage | Count | Conversion |
|---|---|---|
| Replies | 214 | 100% |
| Site visits booked | 63 | 29% |
| Quotations issued | 31 | 14% |
| Units booked | 7 | 3% |
Booked value from this campaign: ৳ 8.9 Cr against ৳ 62,400 of message cost — measured on the booking record, not on click estimates.
Templates are pulled from your Meta Business account with category, language and approval status. A rejected or paused template cannot be scheduled by mistake.
Buyer name, unit number, project, amount and due date merge into Bangla templates correctly, including numerals — which is where most generic tools produce unreadable messages.
Segment on lead source, project interest, budget band, pipeline stage, overdue amount or ageing bucket — because the audience lives in the same database as the campaign.
Local SMS gateways for buyers who are not on WhatsApp, or for the collection reminder that must arrive regardless of app installs, with per-message delivery status.
A reply lands on the lead record and notifies the assigned salesperson. Conversation history belongs to the company, not to a personal handset.
Each campaign reports replies, site visits, quotations and bookings with the booked value — so message spend is judged against contract value, not open rate.
Warm leads on this project, in this budget band, not already booked — built from live CRM data.
An approved Bangla template with unit count, rate and booking money as variables.
Delivery and read state per recipient, with failures listed rather than buried.
Replies route to the assigned salesperson on the lead, and site visits are booked from the same screen.
Marketing broadcast and collection reminder are separate categories in Meta's rules, and mixing them is how a number gets throttled.
| Use | Meta category | Typical trigger | Measured by |
|---|---|---|---|
| Project launch broadcast | Marketing | Manual send to a segment | Replies, visits, booked units |
| Site visit reminder | Utility | 24 hours before the visit | Visit attendance rate |
| Kisti due reminder | Utility | Due date minus 3 days | On-time collection rate |
| Overdue follow-up | Utility | Day 7 and day 14 overdue | Recovery within 30 days |
| Receipt confirmation | Utility | On receipt issue | Support call deflection |
Utility templates carry the payment and service messages; marketing templates carry promotion. Keeping them separate is what keeps the sender quality rating healthy.
Yes — the WhatsApp Business Cloud API through your own Meta Business account and verified sender. Templates, their categories and their approval status are synced from Meta, so what you can send in PropERP is exactly what Meta has approved.
Yes, including variable merge into Bangla templates with correct numerals. This is worth testing on a demo, because generic marketing tools frequently mangle merged Bangla content.
Yes. Inbound messages attach to the lead or buyer record and notify the assigned salesperson. The conversation history stays with the company rather than on an individual's personal phone.
Delivered, read and replied at the message level, then site visits, quotations and bookings attributed to the campaign, with the booked value. The comparison that matters is message spend against contract value.
Yes. Local SMS gateways are supported alongside WhatsApp, which matters for collection reminders that must arrive regardless of whether the buyer uses WhatsApp.
Meta rates sender quality on how recipients respond. Keeping utility and marketing templates in their correct categories, honouring opt-outs, and sending to segmented lists rather than everyone are the practical controls — all of which the module enforces by design.
Next step
Pick a project and a warm-lead list. We will set up a template, send to a small segment and show the delivery, reply and attribution path end to end.
40 minutes · walked through on your project structure · no card required