WhatsApp Business: Handling Status Updates and Buyer Replies on a Schedule

The year before last, a friend in cross-border hardware wholesale complained to me that what he feared most was the phone ringing. A quiet order book came further down the list.

His buyers are mainly in the Middle East and South America, seven or eight hours to eleven hours away from us. While they are at work, he is asleep. By the time he starts, dozens of messages have already piled up.

His replies were arranged like this: more than an hour of catch-up every morning, and another round before bed. For the ten-plus hours in between, the buyers waited. A few orders went to someone else because the reply was slow.

He said this was a limit of sleep, and working harder would not move it.

Operating the phone, and the official API, are two routes

Before talking about WhatsApp Business automation, separate the two routes. People often fold them together.

One is the WhatsApp Business API, the official interface. It needs a business application and a review, and template messages have to be filed in advance. What it can do is fairly regular, which suits a company that already has some scale and standardized processes.

The other is operating the app on the phone, the way you already use it. No qualification is required, the barrier is low, and it can handle more flexible cases. You can look at images, scroll back through the conversation, and see the photo a buyer sent. The API cannot do those, or only with a lot of extra work.

This piece is about the second route. Many teams run both: high-volume standard notices go through the API, and the flexible conversation stays on the phone.

Whether a message can go to the computer depends on whether the answer is fixed.

In cross-border support, a few kinds of questions have fixed answers and can go to the computer:

• Price lists and minimum order quantities
• Dispatch time and parcel status
• Specifications and packaging
• Payment methods and account details
• The returns and exchange policy

In these, the buyer wants a clear fact. A fast answer helps.

When the answer is not fixed, a person has to reply:

• Negotiation
• Complaints and claims
• Unusual orders (short shipment, wrong shipment, damage)
• Any conversation that involves money or who is responsible

One wrong sentence in that list costs several times the time to repair. The minutes a computer saves will not cover the hole.

How a standard reply avoids sounding like a machine, and how to schedule status

This kind of automation usually fails here.

Three suggestions.

Prepare several phrasings for the same kind of question. When a buyer asks when something ships, keep five or six wordings and rotate them. One sentence for a whole year wears thin.

Keep your own speaking habits. If you usually lead with the conclusion or with a greeting, and if you usually write short sentences or long ones, write the replies the same way. Buyers recognize the style. A sudden switch into call-centre language feels odd.

Where a specific number is involved, stop and ask. If a buyer asks how many days a shipment takes to reach Dubai, reply with the range when you have one. When it depends on the case, have the flow stop and hand it to a person. A made-up number is worse than no reply yet.

WhatsApp status is something a lot of people running overseas private-domain work skip. It is a low-cost way to stay with existing buyers: quiet, and still there.

A status update is a simple sequence: open the app, go to status, pick or take a photo, add text, publish. It is fixed enough to turn into a template.

The timing needs care. Buyers sit in different time zones, and posting whenever you think of it only reaches the people who happen to be awake.

My approach is to group by region, work back from each region’s active hours to a time in the home time zone, then stagger the slots. Each market gets covered at least once.

How to work out the time zones is in scheduling overseas accounts, which goes into more detail.

The risk in automated replies is a wrong reply that nobody notices.

For the first two weeks, spend ten minutes a day reading through the conversations the flow answered. Look for three things:

• An answer that missed the question (keyword coverage is incomplete)
• A tone that reads wrong (the wording needs a change)
• A case that should have gone to a person and was answered automatically (the category boundary needs to be tighter)

When you find one, change the keyword or the wording and look again the next day. After two weeks it is mostly stable.

Those ten minutes are easier than handling a complaint afterward. One bad automatic reply uses up some of the buyer’s patience.

Several accounts and several markets

Bind one phone to one account, set the alias to the market it covers, and group by region.

At dispatch time, choosing a device is the same as choosing the account. The alias already names the market. Aliases and grouping are in the Devices documentation.

In cross-border support, this setup carries facts. The buyer asks a clear question, you give a clear answer, and no person has to sit in the middle.

Relationship work stays with a person: how to negotiate, how to settle a dispute, and when to give a little. That is the business itself.

Hand the factual messages over. Use the time you get back on the messages that need a person. Negotiation and disputes decide whether the order closes.

The hardware wholesaler now arranges it like this: standard questions go to the flow and get a reply at any hour, status updates are scheduled separately for three markets, and he handles negotiation and disputes in two focused sessions a day. He says buyers now feel that he replies quickly. What he actually did was hand over the part that did not need him to think.

If you also use WhatsApp Business for overseas private-domain work, connect one phone from the install selection page and start by organizing that table of standard questions. Once the table is clear, the flow comes together quickly.