Recent content by rajagency

I worked with a solo real estate broker who hated email. We switched to WhatsApp follow-ups with cold leads. After some testing, these 5 opening scripts converted best: “Hey [Name], I’ve got a new property that matches what you described in our last chat—want a quick peek?” “2 BHK with garden...

Most people think you must have a full online presence to get started with WhatsApp API. I helped a local mechanic business onboard in 7 days — here’s how. What I used: Google My Business (instead of website) Basic Gmail for domain (no custom email) WhatsApp Cloud API via my agency’s BM A...

I’ve seen more template delays lately. What worked for me: Rewriting content to avoid emojis and shortened URLs Using only one variable field per line Once I followed this, my approvals dropped to 1–2 hours consistently. -also you cannot add urls in utility messages it will most likely get...

Used a lead magnet to collect WhatsApp opt-ins: 37 chats in 48 hours Hit Tier 2 Spent $0 on ads Added a welcome bot + upsell CTA. Funnels don’t need websites if your chat journey is solid.

I tested this—changed my display name in WABA three times during setup. After the 4th change, messaging stopped with no explanation. Support confirmed: frequent name changes trigger auto-review. Now I pick one and leave it. Has anyone else triggered this ?How many times did you manage before...

Exactly but, for full utilization of the resource, also verified BM has increased messaging limit by default for WABA

In case if you are creating multiple new facebook accounts enabling 2fa significantly decrease the chances of your account getting suspended.

No worries, if you ever face any difficulty regarding BM and WhatsApp Business API I am open to discuss

Ghost BM = unverified, sometimes works short-termVerified BM = long-term stable WABA quality score seems based more on user replies and spam reports. But verified BMs get faster support + easier template approvals. Use ghost BMs for testing, verified for scaling.

Exporting settings is manual. Chats are lost. Templates need to be re-approved. Make sure: Number is released from agency BM Client’s BM is verified All access tokens regenerated post migration It’s messy – do it only if client insists.

Tested this with a BM flagged for ads but not WABA. It allowed me to create a new WABA and submit display name. But template approval was super slow. Technically possible, but not ideal. Always use clean BM for WABA launch

Display name was approved, but WABA dashboard said ‘Pending Assets’ for 2 days. Fix: Go to BM > Refresh Assets Disconnect and reconnect WABA integration Wait 10 mins, refresh again Finally synced and started messaging.

Sharing logins = red flag. Meta detects it. We now Create FB profiles for every team member Add each to BM as Employee (not Admin) Use password manager for asset roles Result: no more gray account flags or ad account lockouts.

I struggled with verification for 2 weeks until I used this message: “Hi Meta team, we’re pending verification and it’s impacting our business API integration timeline. Kindly escalate to internal support for review.” Got reply in 2h. Verified in 1 day.

2FA on BM = helps stop random access but not critical.2FA on WhatsApp Number = critical. Without it, anyone can hijack your number. Always enable 2FA inside WhatsApp settings for WABA numbers. That’s what protects from number theft.