How to Track Bookings That Come from WhatsApp
Track appointments booked directly through Niwa on WhatsApp. Associate the conversation source with a saved booking and count cancellations separately.
Track WhatsApp bookings by associating the conversation’s channel and available campaign information with the appointment Niwa saves. Customers can complete a reservation directly in WhatsApp, so a website visit is not required to count the outcome. Use the saved booking reference for counting, then report enquiries, reservations and cancellations separately.
The important outcome is a saved appointment with a stable reference. Tracking a message interaction tells you about interest; it does not tell you whether someone reserved a time.
Define what “from WhatsApp” means
Decide whether you want to identify WhatsApp as the entry channel, a particular campaign that sent people there, or the final interaction before booking. These are different questions.
The Niwa WhatsApp agent can carry out the booking in the conversation using your website’s business context and connected availability. Identify WhatsApp as the booking channel, then preserve any campaign or referral information available through your configured channel and reporting workflow. The channel alone does not prove which earlier advert or website visit prompted the customer to contact you.
Forwarded messages add another complication. Someone can share a tagged link with a friend. The recorded link source still describes that link, but it may not describe the new visitor’s whole journey. State the attribution method when reporting results.
Capture the direct conversation’s booking outcome
Use the saved appointment as the booking event. Associate its stable reference with the WhatsApp channel and available conversation or campaign identifier in your configured reporting workflow. Keep that association when the customer changes or cancels the appointment so one reservation does not become several unrelated records.
If you need campaign-level reporting, ask the person configuring the connection to demonstrate where that source is recorded and how it relates to the appointment. Capture only information the integration actually supplies. A customer-reported referral is useful too, but label it separately from a recorded campaign identifier.
Tag website links when customers use that route
Some customers may prefer a website booking page, or follow a link from the conversation to read service details. For that route, use a URL with campaign parameters supported by your analytics setup. For example:
https://example.com/book/?utm_source=whatsapp&utm_medium=messaging&utm_campaign=appointments
This is an illustrative URL, not a live Niwa booking destination. Use your own working booking page and a naming convention your team understands.
Google’s campaign URL guidance explains these parameters. Keep the values consistent so the same channel is not divided among several spellings in your reports.
Do not put customer names, phone numbers, email addresses or sensitive appointment details into campaign URLs. Google’s guidance on personally identifiable information is relevant to an Analytics-based setup.
Preserve the source for each booking route
A tagged website link identifies an incoming visit. A direct conversation booking uses the source information supplied by the messaging connection. Your reporting workflow needs to preserve the relevant source for either route and associate it with the saved appointment reference, subject to your configured consent and data handling.
The Niwa booking agent supplies the saved reservation. For website reservations, the frontend scheduler source identifies that booking route; it should not be mistaken for an earlier campaign source. Keep the booking channel, campaign source and appointment outcome distinct in your report.
Ask for a demonstration that begins with a WhatsApp conversation and ends with a saved appointment associated with the intended source information. Test the optional tagged-link route separately. This establishes which attribution fields your report can use for each customer journey.
Measure the stages separately
Use a small set of definitions that your team can apply consistently:
| Stage | Evidence | What it tells you |
|---|---|---|
| Booking enquiry | Recorded WhatsApp conversation about an appointment | Someone expressed booking interest |
| Website link opened, where used | Recorded visit with the relevant campaign parameters | Someone used the optional website route |
| Reservation completed | Saved appointment with a stable booking reference | A time was reserved |
| Appointment cancelled | Saved cancelled status for that reference | The reservation is no longer active |
| Appointment completed | Recorded attendance or completed status | The service appointment took place |
Avoid counting a confirmation page refresh as another booking. Use the stable appointment reference to identify one reservation, even if several page views or messages refer to it.
Report initial reservations and cancellations separately when useful. If you report active reservations, explain how cancelled appointments are excluded. Attendance requires its own record; a WhatsApp read receipt cannot supply it.
Use a reconciliation process when source capture is limited
For a modest volume, staff can reconcile campaign visits with bookings using an agreed process that records the booking reference and the source information actually available. If the customer voluntarily tells you where they found the business, label that as customer-reported information.
Do not force uncertain matches from similar names or nearby timestamps. Record unknown attribution as unknown. This gives you a more useful report than assigning every appointment to the channel you hope generated it.
Some scheduling products store campaign parameters with appointments. Calendly documents UTM tracking for its own bookings. That is an example of an explicit attribution feature, not proof that every scheduler or Niwa configuration has the same reporting behavior.
Test the handoff before using the report
Complete a reservation directly in a WhatsApp conversation on a phone. Read back its reference and check where the channel and campaign source are recorded. Then test the optional tagged website route, a repeated confirmation view, a cancellation and a booking with unknown campaign origin. Verify that each case produces an understandable result without duplicate reservations.
The WhatsApp booking setup guide covers the underlying customer journey. Use the Niwa help guide to verify scheduler configuration before adding measurement.
Discuss WhatsApp booking attribution with Niwa and specify whether you need channel reporting, campaign reporting or attendance outcomes. That defines the source capture and booking association your setup must demonstrate.
