The setup itself is not hard. Salesforce ships a native Enhanced WhatsApp Channel, and the click path takes an afternoon. What catches teams out is everything around it. There is a setup step that, done in the wrong order, means starting over from scratch. There is a 24-hour rule that quietly stops your agents from replying. There is a template approval process that adds days to a launch nobody budgeted for. But from July 2025 onward, Meta charges according to the number of messages you send rather than the number of conversations, thus altering the cost structure of this channel.

The guide starts by taking you through the four setup steps in the proper sequence, followed by three key issues not covered by any other guide: how the 24-hour customer service window determines what your agents can send, what the messages cost you, and whether you should use the native channel or create your own. Don’t start Step 2 until you’ve read Step 1. That’s the one that’s costly to get wrong.

What You Are Actually Connecting

Three things must line up, and the names matter because the setup screens use them.

WhatsApp Business Account (WABA). This is your business identity inside Meta’s system. It owns your phone numbers and your message templates.

A phone number. Dedicated to WhatsApp Business. It cannot be a number already registered to the consumer’s WhatsApp app, and you will need to verify it.

The Enhanced WhatsApp Channel in Salesforce. This is the native connector inside Service Cloud. It creates a Messaging Session for each conversation, which behaves any other record — routable, reportable, attachable to a Case.

The important idea is that WhatsApp becomes a channel, not a separate inbox. An agent handling WhatsApp works in the same console they use for email and chat. Managers’ report on it the same way.

That only holds if the setup order is right, which brings us to the step most teams get backwards.

Read: AWS Consulting Partner: How to Reduce Cloud Costs

Step 1: Create the WABA Inside Salesforce, not in Meta

This is the step to read twice.

The approach seems sensible since you are connecting with WhatsApp, and therefore, you navigate to the Meta Business Manager, create a WhatsApp Business account, input your phone number, and finally connect Salesforce to it.

This will not help. Salesforce’s own documentation is explicit: if you create your WABA in Meta Business Manager outside the channel setup flow in Salesforce, you cannot use it with a Salesforce channel.

So do it in this order:

Enable Messaging in Salesforce first. Setup, then Messaging Settings. Nothing else works until this is on.

Start the Enhanced WhatsApp Channel setup in Salesforce. Begin from the Salesforce side, not the Meta side.

Create the WABA from inside that flow. Salesforce hands you off to Meta at the right moment and links the two accounts as it goes. You will log into your Meta Business account during this step, which is expected.

Verify the phone number when prompted. Have access to it, because a code arrives.

If you already created a WABA in Meta and hit this wall, you are not stuck forever — but you will be creating a new one through the correct flow. Better to spend three minutes reading this than a morning unpicking it.

Step 2: Configure the Enhanced WhatsApp Channel

With the WABA created through the right path, the channel configuration is straightforward.

Name the channel for humans. “WhatsApp — Support US” beats “WhatsApp Channel 1.” Someone will be picking it from a list in six months.

Set the business hours. This drives what happens to messages arriving overnight, which matters more than teams expect.

Choose the routing type. Omni-Channel routing sends conversations to queues based on skills or availability. Decide this before launching rather than after.

Set the welcome and offline messages. An incoming message from a client at 11 p.m. needs a response, not a silence.

Perform all of the above in the sandbox first. Test with a real phone number, not just a test record. WhatsApp behaves differently from web chat, and you want to feel that difference before customers do.

One practical note. Test the phone you can hold. Reading a transcript in the console tells you nothing about whether the customer experience feels right.

Setup walkthroughs with current screenshots are useful alongside this – Salesforce Geek keeps reasonably current tutorials on Service Cloud channel configuration.

Step 3: Route Conversations to a Queue That Answers

Every guide says, “set up routing.” Almost none says what happens when nobody is there.

WhatsApp raises the stakes because customers treat it instantly. An email left for four hours is normal. A WhatsApp message left for four hours feels ignored.

Four decisions to make explicitly:

Which queue receives new conversations. One queue to start with. Add skills-based routing later, once you know the volume.

What happens outside business hours. An automated response that sets an expectation – “we reply by 9 a.m.” — beats nothing at all.

How does escalation work? If a conversation needs a specialist, can the agent transfer it without losing history? Test this before launch.

When a conversation closes. Sessions that stay open forever clog your agent capacity reports. Set a rule.

Then measure one number in week one: median time to first agent reply. It will be worse than you expected, and it is the number customers judge you on. Practitioner discussion of Omni-Channel setup patterns is worth scanning in the Trailblazer Community before you finalize the design.

Step 4: Get Templates Approved Before You Need Them

Here is the constraint that surprises teams, and no competing guide explains it.

You cannot send a customer a WhatsApp message whenever you like. Outside of an active conversation, you can only send pre-approved message templates. Meta reviews each one.

Templates fall into categories, and the category determines both what you may send and what it costs:

Marketing. Promotions, offers, and announcements. Always billable.

Utility. Order updates, appointment reminders, shipping notifications. Tied to a specific transaction.

Authentication. One-time passcodes and verification codes.

Service. Replies inside an open conversation. These are now free for all businesses.

Three things make approval go smoothly. Write the template for the category you selected — a promotional message submitted as Utility gets rejected. Use variables for the changing parts and make the surrounding text read naturally. And submit early, because review takes time you have not scheduled.

Build your template library during the build phase, not the week before launch. A project that is otherwise ready can sit waiting for approval.

The 24-Hour Window That Changes How Agents Work

It is the rule which transforms your agents’ workflow and does not feature in any of the major manuals. 

Upon receiving a message from a customer, a 24-hour customer service timeframe becomes active. Within its timeframe, your agents may respond with a free-form message. Once it closes, they cannot. They can only send an approved template.

Picture what that means on a Monday. A customer messages Friday afternoon with a question. Nobody replies over the weekend. Monday morning your agent types a helpful answer and it will not send, because the window shuts on Saturday.

What You Can Send, and When

Two consequences worth designing around.

Reply inside 24 hours or lose the free-form option. That makes response time a technical constraint, not just a service goal.

Keep a small set of Utility templates ready for reopening conversations that have gone quiet. Without them, an agent has no way to restart the thread.

There is also a useful exception. If a customer reaches you through a Click-to-WhatsApp ad, replying within 24 hours opens a Free Entry Point window lasting 72 hours, during which any message type is free. Worth knowing if you run those ads.

What WhatsApp Actually Costs in 2026

Nobody writing about this integration mentions the money. Six leading guides, no cost figures, no pricing model explained. So here is the shape of it, from Meta’s own documentation.

Meta moved to per-message pricing on July 1, 2025. Before that, it was charged for 24-hour conversation. If your budget was built on the old model, it is wrong.

Service messages became free for all businesses on November 1, 2024. Replying to a customer inside an open window costs nothing.

Marketing templates are always billable. Every send, every recipient.

Utility and Authentication templates are free inside an open customer service window and billable outside it. So, a shipping notification sent while a conversation is live costs nothing; the same notification sent cold is charged.

Rates vary by country and Meta updates the rate card periodically — there were changes on October 1, 2025, and new currency rates from January 1, 2026. Check the current rate card for the countries you message rather than trusting a figure in any article, including this one.

The practical takeaway is a design decision. Answering fast is cheaper than answering late. Free-form service replies inside the window to cost nothing, while reaching someone after the window closes requires a billable template. Response time is a line item, not just a metric.

Native Channel or Custom Build?

Salesforce’s Enhanced WhatsApp Channel is not the only route. You can build directly against Meta’s Graph API with Apex callouts and webhooks. Both are acceptable. It all depends on what you need.

Enhanced WhatsApp Channel vs. Custom Graph API Build

Pick the native channel unless you have a concrete requirement it cannot meet. It is faster, cheaper to own, and maintained for you.

Pick a custom build when you need something the channel genuinely does not do — an unusual approval flow, a non-Service-Cloud destination, or a messaging experience embedded in a custom app.

The trap is choosing a custom because it feels more capable. Every custom component needs retesting at each Salesforce release, and it narrows the pool of people who can maintain it. Reference implementations of Graph API callouts are well documented by SFDC Panther if you decide to go that way.

The Pre-Launch Checklist

Run this before real customers can message you. It takes an afternoon.

Table 3 — WhatsApp Channel Pre-Launch Checklist

Every row is checkable in under thirty minutes. A failing row is cheap now and awkward once customers are messaging.

Ongoing channel and agent-side administration is well covered by Salesforce Admins if you are building this capability in-house.

Salesforce Integration FAQs

What is the Salesforce integration with WhatsApp?

It allows for WhatsApp integration as a channel within Service Cloud and thus allows customers’ messages to come through as Messaging Sessions tied to Contacts and Cases. The agents then respond to these messages using the same console that they use to respond to emails and chats.

What is included in Salesforce integration services for a WhatsApp rollout?

Typical scope covers WABA and phone number setup, channel configuration, routing and business-hours design, template authoring and submission, agent enablement, and testing. Salesforce integration services vary most in whether template management and post-launch monitoring are included — worth asking, since templates need maintaining.

Do I need a Salesforce integration partner for this, or can my admin do it?

A single-queue native channel is well within a capable admin reach. Bring in a Salesforce integration partner when you need multi-region routing, a large template library, a custom Graph API build, or integration with systems beyond Service Cloud.

How does this fit with the rest of my Salesforce CRM integration work?

WhatsApp is one channel among several. Salesforce CRM integration usually means connecting many systems — ERP, marketing, support — and WhatsApp slots in a customer-facing channel rather than a data pipeline. The design questions are different: response time and message cost, not row volume, and API limits.

What should I ask for a Salesforce integration company before they start?

Three questions. How will you create the WABA — and if the answer starts with Meta Business Manager, that is a warning sign. How will agents reply after the 24-hour window closes. And which message categories will we be paying for. A Salesforce integration company that answers all three has done this before.

Are there Salesforce integration solutions for WhatsApp beyond the native channel?

Yes. AppExchange connectors and Business Solution Providers offer packaged options, and a custom Graph API build is always possible. Most teams find the native Enhanced WhatsApp Channel covers their needs; Salesforce integration solutions beyond it are worth exploring only when you have a requirement it cannot meet.

Can I send marketing messages on WhatsApp?

Yes, using approved Marketing templates, and they are always billable. Consent matters here — send unwanted marketing and users to block you, which damages your quality rating and your reach.

What happens if a customer replies a few days later?

Their reply opens a fresh 24-hour window. So, a customer who comes back after a week gives your agents a new window to work in, which is why keeping the conversation open on your side is worth doing.

Bringing It Together

The setup is an easy part. Four steps, one afternoon, and WhatsApp live in your console. What separates a channel that works from one that frustrates everybody is the three things sitting around the setup: creating the WABA in the right order, having templates approved before you need them, and designing your agent workflow around the 24-hour window rather than discovering it in week one.

Sequence the work accordingly. Start the WABA inside Salesforce, never in Meta Business Manager. Submit your first Utility templates during the build phase, not the week before launching. Test the window behavior deliberately in a sandbox, so your agents meet the constraint in training rather than in front of a customer. Then set one number to watch from day one — median time to first agent reply. On WhatsApp, that metric is not only a service measure. Because free form replies inside an open window cost nothing while reaching someone after it closes needs a billable template, answering fast is also the cheaper option.

Get those pieces right and WhatsApp stops being another inbox someone has to remember to check. It becomes a channel your team works the same way they work email, with the same records, the same routing, and the same reporting. That is what a well-built Salesforce integration with WhatsApp buys you: not a new tool, but one fewer place your customer conversations can go missing.

The post Salesforce Integration with WhatsApp: A Step-by-Step Guide to Seamless Customer Communication appeared first on Tech Gadget Time.