Article summary
Design a temporary WhatsApp Activity queue for Seychelles tourism, separating +248 phones, foreign guests and expired contact purposes.
The central question in a Seychelles tourism list is not the share of +248 phones; it is which guest needs contact inside which service window. Visitors commonly retain foreign phones. Activity observations can help an authorised service queue, but they cannot turn one trip into a permanent marketing relationship.
Build queues around the guest journey
| Stage | Defensible action | Expiry condition |
|---|---|---|
| Pre-arrival | Confirm transfer or check-in details | Service completed |
| In-stay | Resolve a requested service issue | Checkout |
| Post-stay | Follow up within permission | Purpose completed or opt-out |
| No current relationship | Do not revive from activity data | Keep suppression |
+248 and Seychelles customers are not the same set
number_plan records phone formatting, while service_market records where the order was served. A +248 phone may not be local today, and a foreign phone may belong to a real guest. Neither field should overwrite the other.
Activity helps only time-sensitive actions
When a transfer or service case must be arranged within hours, activity time may assist ordering. If the action does not depend on recency, do not collect active days, avatar or mapping merely to make the output look complete.
Minimise the AIPUSH field view
WhatsApp Activity may return phone, activity time, active days, business-account observation, avatar and mapped phone. A service desk usually needs only phone and time fields. Give other columns narrower access or keep them outside the daily view.
Booking and passport data stay out of TXT
The upload contains one phone per line. Name, booking, hotel, dates, documents and permission remain inside the business system and reconnect through batch_row, reducing unnecessary data in the execution chain.
A new season cannot inherit an old snapshot
Store checked_at, valid_until and season_batch for each result. A new peak period needs a current business basis. Copying last season’s workbook does not create a present “active list.”
Use country evidence for visitor phones
Preserve phone_raw and normalize from a user-provided country or reliable order evidence. Never force a foreign phone into +248, and never select language automatically from the phone country.
Opt-out follows confirmed phone relationships
When a mapped relationship is manually confirmed, suppression should cover the related phones. Do not merge conflicts automatically. No new observation can erase an existing opt-out.
What a peak-season report should measure
Measure queue response and service completion, not a claim that active users are more likely to buy. Record submitted, returned, unknown, expired and deleted counts by provenance and journey stage to evaluate the process.
The Seychelles operating principle
Activity checking should make temporary service more timely, not make temporary guests permanent. Use observations inside a defined window and expire them when that window closes.
