
A customer who has just placed an order usually wants a useful update: whether payment was received, when the order will arrive and how to get help. WhatsApp can make that exchange easier when your application sends the right message and your team has a clear way to handle the response.
This guide shows Nigerian businesses and organisations how to plan WhatsApp messaging, prepare templates, connect the Yournotify API and measure results. Start with one useful customer journey, prove that it works and then expand.
Table of Contents
Choose the job your message needs to do
Do not begin with a single template for every situation. Separate verification, operational updates and promotions before configuring your sender.
| Message purpose | Practical example | What to prepare |
|---|---|---|
| Authentication | Send a code when a person signs in | An approved authentication template and a verification flow |
| Utility | Confirm an order or appointment | An approved utility template with the relevant order or booking details |
| Marketing | Invite opted-in contacts to a relevant offer | An approved marketing template, an appropriate audience and a clear action |
These categories follow Meta’s WhatsApp template structure. Choose the category that matches the actual content. Adding a sales offer to an order update changes the purpose of the message.
For example, a Lagos homeware shop could start with collection notifications. That creates a clear event to integrate, a small set of variables and a result the team can verify.
What Nigerian businesses can learn from UBA’s Leo
UBA’s Leo provides a visible Nigerian example of service through conversation. UBA describes tasks such as checking balances, transferring funds and paying bills through its assistant, including access on WhatsApp.
The lesson for a business messaging project is to begin with a task the person wants to complete. A useful conversation has context, an understandable next step and a way to get help. A long sequence of generic promotional messages does not create that experience.
For your own business, pair Yournotify’s WhatsApp campaign delivery with a clear response process. The API can send the appropriate approved template, while your application or team handles the specific business action and its outcome.
Industry workflows you can build around WhatsApp
| Industry | First useful message | What should happen next |
|---|---|---|
| Ecommerce | An approved order-status update | Help the buyer resolve a delivery question |
| Automotive | A confirmed service or test-drive appointment | Route changes to the responsible branch |
| Hospitality | Arrival instructions for a confirmed booking | Help the guest clarify timing or location |
| Education | An update about a submitted application | Connect the applicant with the admissions team |
| Professional services | Confirmation of a requested consultation | Answer preparation questions and confirm attendance |
Keep the local context specific: the correct branch, a Nigerian contact number where relevant, clear dates and a recognisable business identity. If your team serves several cities, retain the location with the conversation so the reply reaches someone who can help.
Worked example: an automotive service appointment
A customer books a service appointment in Lagos. After the booking is confirmed, your backend sends the approved utility template with the appointment reference, date, time and branch. The customer replies to ask whether they can arrive later.
The team checks the booking, agrees a new time and updates the booking system. Only after that change is saved should the revised confirmation be sent. Keep a record of which notification relates to which version of the booking.
Measure confirmed appointments, completed visits and unresolved replies. This creates a more useful business picture than message volume alone. Start with one branch and one appointment type before expanding the workflow.
Step 1: prepare your sender and contact data
In Yournotify, open Sender ID → WhatsApp and complete the sender setup requirements. Use the approved sender ID in your API requests. Your sender represents the business customers expect to hear from, so the identity should match the website, purchase journey and support experience.
Store telephone numbers in international format, including Nigeria’s country code where appropriate. Keep the source of each contact and their messaging preferences. A telephone number collected for delivery coordination should not automatically become permission for unrelated promotions.
Before integrating, assemble these items:
- Your approved WhatsApp sender ID.
- A template approved for the intended purpose.
- A server-side Yournotify API key.
- A test recipient you control.
- The event in your application that should trigger the message.
- A person or team responsible for handling replies.
Step 2: write a template that helps the recipient
Open Templates → WhatsApp and prepare a template with a clear purpose and predictable variables. A collection update might read:
Hello {{1}}, your order {{2}} is {{3}}. Reply if you need help with collection.
For this example, the variables could be Amaka, ORD-12345 and ready for collection. Use the exact variable order from the approved template. Keep each value short enough to read naturally within the sentence.
Avoid filling a variable with an entire promotional paragraph. It makes the result harder to review and can change what the template is being used to communicate. Preview the full message with realistic values, including a long name or order reference.
Step 3: send a sandbox request from your server
The example below demonstrates an approved utility template. Replace the sender, template ID and telephone placeholder with your own values. The numeric template ID is illustrative, not a shared template available to every account.
curl -X POST 'https://api.yournotify.com/campaigns/whatsapp' \
-H "Authorization: Bearer $YOURNOTIFY_API_KEY" \
-H 'Content-Type: application/json' \
-H 'X-YN-SANDBOX: 1' \
--data '{
"name": "Order collection update",
"from": "YOUR_APPROVED_WHATSAPP_SENDER",
"template_id": 12345,
"status": "running",
"lists": [{
"telephone": "<TEST_PHONE_E164>",
"attribs": {
"1": "Amaka",
"2": "ORD-12345",
"3": "ready for collection"
}
}]
}'
For this transactional template request, numbered keys inside lists[].attribs supply the approved body variables. Do not substitute unrelated names such as customer_name and expect them to fill positional variables automatically. Authentication templates use a different code field, explained in the Yournotify API documentation.
The sandbox header validates the request without delivering it or charging for a send. After validation, remove that header only for a controlled live test. Keep the bearer key on your server; never embed it in website JavaScript or a public mobile application.
Step 4: connect the right application event
Trigger the collection message when an order actually becomes ready, not whenever someone refreshes the order page. Store the order ID, the notification purpose and the resulting campaign reference in your application.
A practical sequence is:
- A staff member marks the order ready for collection.
- Your server checks whether this order already has a collection notification.
- The server builds the approved template variables and submits the request.
- Your application records the response and checks subsequent campaign results.
- The support team can find the order reference when the customer replies.
If a request times out, investigate whether a campaign was created before repeating it. A timeout does not prove that nothing happened. This small control helps prevent customers receiving several copies of the same update.
Step 5: design the conversation after the message
Sending is only part of the journey. Decide what happens when a person replies with “Can someone else collect it?” or “Please change my delivery address.” Route the conversation to the appropriate team, preserve useful context and make ownership clear.
Yournotify Conversations complements outbound messaging with a place to manage customer conversations. Agree an internal response target and an escalation route for questions the first responder cannot resolve.
Use campaign reporting to review delivery and engagement where available. Then connect those numbers to the business outcome: collections completed, appointments confirmed or enquiries resolved. Do not treat every delivered message as a completed sale.
Troubleshoot with a simple checklist
| Problem | First checks |
|---|---|
| Template request is rejected | Confirm sender approval, template ID, category and required variables |
| Recipient details are invalid | Check country code, formatting and the intended recipient |
| Variables are missing or misplaced | Match numbered attributes to the approved template order |
| Duplicate updates appear | Check repeated application events, retries and stored notification references |
| Replies go unanswered | Review conversation ownership and team availability |
When investigating, keep the campaign reference and error details. Remove personal data and credentials before sharing diagnostic examples.
Frequently asked questions
Can I send any text through a template request? The transactional flow above uses the approved template and its expected variables. Build the message around that template rather than adding an arbitrary body to the request.
Can I send OTPs through WhatsApp? Yes, use an approved authentication template and the authentication payload in the documentation. Your application must still generate, expire and verify the code.
How should I estimate cost? Start with the expected messages, their purpose and destination, then check current Yournotify pricing and your account’s applicable rate.
Build your first useful WhatsApp workflow
Choose one event, prepare one approved template and test it end to end with your own recipient. Once the message, reply handling and reporting work together, extend the same approach to other journeys.
Explore Yournotify WhatsApp or open your dashboard to set up your sender and first template.