# A contact is marked Not on WhatsApp > In SkedX Flow, a contact is marked Not on WhatsApp when WhatsApp answered a message to their number with #131026 (message undeliverable: the number is not on WhatsApp, cannot receive it, has not accepted WhatsApp’s latest terms or uses a very old app). The mark is kept per company, from WhatsApp’s own answer; no one — SkedX, Gupshup or Meta — can check a number before the first send, and that first send is refunded. A contact who wrote to the business on WhatsApp shows On WhatsApp in green. Where it shows: Contacts — the On WhatsApp tile says “· N not on WhatsApp”, the filter “Not on WhatsApp (N)” lists them, and each row’s Reachable on shows “Not on WhatsApp · date” instead of the WhatsApp logo (an Indian number with the wrong number of digits says “number looks a digit short”); the contact pop-up fades the WhatsApp logo and its Reachability line reads “WhatsApp — Not on WhatsApp · since date” with Check again; the inbox shows “Not on WhatsApp” under the bubble, a note “ isn’t on WhatsApp”, and a line above the composer with Send an SMS instead (or Set up SMS) and Check again. Audiences stop counting them as reachable on WhatsApp. Every WhatsApp send leaves them out — campaigns (taken off the cost), automations (skipped, not failed) and template sends — not charged. Check again lifts the mark: the next WhatsApp send tries them once; refused again, the mark comes back. The mark ends by itself when the person writes to the business on WhatsApp, and Flow tries once more after 30 days. Developers: GET /api/contacts/ rows carry whatsappReach {status: on | not_on, at}; ?whatsapp=not_on filters. Product: SkedX Flow · Topic: Contacts · Draft — steps not yet re-verified in the live product When WhatsApp says a number can’t receive messages, Flow marks that person once — and every screen and every send follows the mark, so you stop paying to find out again. This page shows where you see it and how to check the number again. ## Step 1: Find them in Contacts Open **Contacts**. The **On WhatsApp** tile says how many are not. Pick **Not on WhatsApp** in the channel filter to list only them. In each row, **Reachable on** shows **Not on WhatsApp · date** instead of the WhatsApp logo — the date WhatsApp said so. A person who wrote to you on WhatsApp shows **On WhatsApp** in green. An Indian number with a digit missing or extra says **number looks a digit short**: fix the number first. Open it directly: https://flow.skode.ai/contacts ## Step 2: On the contact Open the person. The WhatsApp logo is faded — hover it to see since when. Under **Reachability** the line reads **WhatsApp — Not on WhatsApp · since** the date. **Check again…** is how you lift the mark — see [Check again](#check-again). ## Step 3: In a chat In the inbox the message says **Not on WhatsApp** under the bubble, in grey — not “Not delivered” in red — and the note under it says the person isn’t on WhatsApp, not charged, with **What this means**. Above the composer, Flow says a WhatsApp message would not be delivered and offers **Send an SMS instead** — or **Set up SMS** when SMS is not set up for your account — and **Check again**. ## Step 4: What Flow does with the mark Every WhatsApp send leaves them out, so you are not charged for a message WhatsApp will refuse again: campaigns take them off the cost before you send, automations skip them with “Not on WhatsApp” in the run (not counted as a failed run), and template sends skip them. Audiences stop counting them as reachable on WhatsApp. Email and SMS are not affected. ## Step 5: Check again Think the number is on WhatsApp now? On the contact press **Check again…**, or **Check again** above the composer in the chat. The mark is lifted and the next WhatsApp send tries them once. If WhatsApp refuses again, the mark comes back, and that send is not charged either. You do not always need to: the mark ends by itself when the person writes to you on WhatsApp, and Flow tries once more after 30 days. ## Common questions ### Can Flow check a number before I send to it? No. WhatsApp offers no way for any business platform to check a number before sending — not SkedX, not Gupshup, not Meta’s own API. Tools that claim to do it log a real phone into WhatsApp Web, which breaks WhatsApp’s rules and can get numbers banned. Flow learns from the first send, refunds it, and remembers. ### Am I charged for the message that found out? No. A message WhatsApp refused is refunded to your wallet. ### Does another company in SkedX see my mark? No. The mark comes from your own sends and stays in your company. ### Why is someone who wrote to me marked? They are not: a person who wrote to you on WhatsApp shows On WhatsApp, and writing to you ends a Not on WhatsApp mark at once. ## Useful links - Contacts in SkedX Flow — filter Not on WhatsApp: https://flow.skode.ai/contacts Videos and screenshots © 2026 SkedX, with sample data only. Share and link to them freely; copying the SkedX product or its design is not allowed. Terms: https://skode.ai/terms/ ## Related guides - Why WhatsApp held back some of your messages: https://skode.ai/help/flow/templates/why-whatsapp-held-back-some-messages/ - Send a WhatsApp campaign to many contacts: https://skode.ai/help/flow/templates/send-a-whatsapp-campaign-to-many-contacts/ - What you see in a Flow conversation: every message as your customer saw it: https://skode.ai/help/flow/inbox/what-you-see-in-a-flow-conversation/ - A contact’s Activity in SkedX Flow: everything that happened, in one list: https://skode.ai/help/flow/contacts/a-contacts-activity-in-skode-flow/ - Import contacts into SkedX Flow from a spreadsheet: https://skode.ai/help/flow/contacts/import-contacts-into-skode-flow/ - Add the country code to numbers saved without one: https://skode.ai/help/flow/contacts/add-a-country-code-to-saved-numbers/ - Build an audience in SkedX Flow: https://skode.ai/help/flow/contacts/build-an-audience-in-skode-flow/ Source: https://skode.ai/help/flow/contacts/a-contact-is-marked-not-on-whatsapp/