You have a few thousand users holding a token you are about to stop supporting, a withdrawal deadline three weeks out, and a support inbox that will fill the moment the first notice goes out. Or trading is paused and you have no restart date to give anyone. Or a researcher posted something about wallet security and users are asking whether to move funds tonight. Email reaches a fraction of them. The text is what gets read, and text is the channel most crypto operators lost at the aggregator.
This is the playbook for the deadline-driven notices a crypto business sends: what each says, when it goes, who answers the replies, and what you do with silence.
Three notices every crypto operator ends up sending
The delisting with a deadline. On 8 October 2026 the European Securities and Markets Authority published an opinion telling national regulators that MiCA-authorised providers should stop offering services for non-compliant stablecoins, with legacy exposures remediated "no later than three (3) months following the date of publication." Within days, Coinbase told customers in the European Economic Area to withdraw USDT and PYUSD by 30 October, with remaining balances converted automatically, according to Cointelegraph.
The halt with no end date. Trading on bitcoin.de has been largely suspended since 12 June 2026. On 6 October 2026 its parent, Bitcoin Group SE, announced that BaFin had refused its subsidiary's MiCA authorisation and that details would follow "in due course via the bitcoin.de website." More than a million registered users are waiting on a website.
The security advisory. On 8 October Ethereum researcher Justin Drake urged a "controlled mass migration of assets to fresh addresses," while warning that "a rushed migration would do more harm than good." Every support line got the same question that week: should I move my funds?
Those examples are European or protocol-level, but a US list gets the same three shapes: a token delisted after a regulatory letter, a chain upgrade that pauses deposits, a vulnerability disclosure.
The delisting ladder: four texts over thirty days
Bitbuy's delisting policy notifies holders 21 days before trading stops, reminds them at 14 days, 7 days and 24 hours, then opens a 30-day withdrawal window with reminders at 15 days, 5 days and 24 hours. Seven emails is fine. Seven texts is not. By text you send four, each only to people who still hold the asset.
That rule is the whole playbook. Pull the holder list from your own ledger before every send, so anyone who already withdrew drops off. A reminder to someone who moved their balance last week reads as a mistake.
Text 1: the announcement. Trigger: the public notice is live on your site. Goes to every current holder, in their daytime.
[Exchange]: We're ending support for [TOKEN]. Trading stops [3 Nov]. Withdrawals stay open until [3 Dec, 08:00 UTC]. Full notice is in the app under Alerts. Reply HELP for a person, STOP to end texts.
That is two segments, and it has to be: date, UTC deadline, where the notice lives, reply path. Then nothing for seven days. No reply is normal.
Text 2: seven days before withdrawals close. Trigger: re-pulled holder list, seven days out.
[Exchange]: Reminder: you still hold [TOKEN]. Withdrawals close [3 Dec, 08:00 UTC], 7 days from now. To withdraw: Wallet > [TOKEN] > Send. Reply HELP if the send fails.
The most common reply is a variant of "it won't let me withdraw," usually minimum amounts, network fees or the wrong chain. Have those answers ready before this text goes out.
Text 3: 24 hours before. Trigger: re-pulled list, one day out.
[Exchange]: Last call. [TOKEN] withdrawals close tomorrow, [3 Dec, 08:00 UTC]. After that, any remaining balance is converted to [USDC] automatically. Reply HELP now if you're stuck.
Say what your policy actually does after the deadline. Coinbase's EEA approach converts what is left; other exchanges decommission the asset and the balance is gone. That sentence decides how many angry tickets you get in week five.
Text 4: after the deadline. Trigger: the conversion or decommissioning is complete. Goes to anyone who still held at close.
[Exchange]: [TOKEN] withdrawals have closed. Your remaining [TOKEN] was converted to [USDC] on [3 Dec] and is in your wallet now. Reply HELP with any questions.
This is the text that prevents the "where did my money go" ticket.
Send between 10:00 and 18:00 in the holder's local time, state the deadline in UTC because that is what your systems enforce, and never stack a delisting text with a promotional one on the same day.
The halt and the maintenance window: two texts, then only news
Planned maintenance is a two-message pattern. The second message matters more, because silence after a maintenance window reads as "still broken."
Text 5: the day before.
[Exchange]: Scheduled maintenance [Sun 9 Nov, 02:00-06:00 UTC]. Trading and withdrawals pause in that window; balances aren't affected. No action needed. Reply HELP for questions.
Text 6: the all-clear. Trigger: your ops lead confirms systems are up. The actual end, not the scheduled one.
[Exchange]: Maintenance finished at [05:40 UTC]. Trading and withdrawals are back on. If something looks wrong in your account, reply HELP and a person will look.
An unplanned halt with no end date, the bitcoin.de shape, is harder, because people want a date and you do not have one. Send the first text the day the halt starts, then send again only when something changes.
Text 7: the open-ended halt.
[Exchange]: Trading is paused while we move to a new custody partner. Your assets are held and your claims are unchanged. We'll text when trading resumes; there's no date yet. Reply HELP for a person.
A weekly "no update" text teaches the list to ignore you. If nothing has changed in thirty days, one message saying so is the ceiling.
The security advisory: tell them what you are not asking
A security scare produces two kinds of text: yours, and the phishing texts that start the same afternoon pretending to be you with a "migrate now" link. Yours has two jobs: say what happened in a sentence, and say what you are not asking the user to do.
Text 8: the advisory. Trigger: your security lead has a position on the disclosure and it is posted in the app.
[Exchange] security note: you may have seen reports about future risks to wallet signatures. No action is needed today. We will never text you a link to move funds or ask for a recovery phrase. Updates are in the app under Security. Reply HELP for a person.
No link. Once your real advisories carry links, a fake one with a link is indistinguishable from them. Point to a path inside the app instead, and if you later recommend a migration, the guide in the app carries the detail.
What the inbox looks like the week after
Replies to a delisting ladder cluster into five types: how do I withdraw, the withdrawal failed, is this real, what if I miss it, and STOP. Build a quick reply for each before text 1 goes out. In the Android Texter dashboard those are slash-shortcuts in the composer: /withdraw expands to the steps, /deadline to the date in UTC and the main US time zones, /real to how the user can verify the notice inside the app, and /missed to your post-deadline policy.
Ownership is one named person per rung. Texts 1 and 2 can be a single support lead alongside normal tickets. The 24-hour rung needs two people, because that is the day the failed-withdrawal replies land, and a reply that waits four hours on last-call day is a balance converted against the user's wishes.
If your team lives in Telegram, forward inbound replies into the channel they already watch. The setup is in our Telegram forwarding guide, and the runbook for crypto support off a handset is in Crypto SMS Support: The Week After You Get Dropped.
Scheduling: queue texts 2 and 3 the morning they are due, after the holder list is re-pulled, with the scheduled-send picker set for 10:00 in the recipient's zone, not three weeks ahead against a list that will be stale. Volume: a few thousand holders is more than one handset should push in a morning, so spread the send across paired phones and keep each line at a human day's worth of messages. The per-line numbers are in SMS Sending Limits Per Phone Number.
How you know it worked
The metric is the holder count on your own ledger at each rung, not open rate. If 4,000 people held at text 1 and 900 hold at text 2, the announcement worked. If 900 hold at text 2 and 850 at text 3, the reminder did not, and the usual fix is that the withdrawal path in the message does not match the app. Per rung, also count failed-withdrawal replies, "is this real" replies and STOPs. A jump in "is this real" means a fake notice is circulating and your next text should say so.
Consent, STOP and the aggregator gate
These are account-service notices to people who hold a balance with you, but that relationship does not substitute for consent to text. Prior express consent to receive texts at that number is yours to collect, normally at signup, and yours to keep a record of. A user who has texted STOP gets the delisting notice by email and in the app, not by SMS. Our TCPA opt-out guide covers what counts as a STOP and what has to happen next.
The gate that took this channel away is at the aggregator. Twilio's reference for error 30947 says carrier policies prohibit A2P campaigns that "promote, advertise, or facilitate cryptocurrency trading," lists price alerts and token launches among the triggers, and says a rejected campaign "cannot be resubmitted." A withdrawal deadline is not a promotion, but the campaign that would carry it was registered by a crypto business, and that classification is what gets refused. The wider picture is in Which Industries Are Blocked From SMS Marketing in 2026?
Android Texter routes each message through an Android handset you own, as person-to-person SMS from a real ten-digit number. There is no campaign to classify and no registration a policy review can withdraw, which is what makes it usable for a notice with a date on it. The TCPA applies in full, consent and opt-out are your responsibility, and nothing about the channel changes your securities, money-transmission or consumer-protection obligations.
Frequently Asked Questions
How many texts should a token delisting get?
Four, each sent only to people who still hold the asset at that moment: an announcement when the notice goes public, a reminder seven days before withdrawals close, a last call 24 hours out, and a confirmation after the deadline that says what happened to remaining balances.
Can I text a delisting notice to someone who opted out?
No. A STOP covers service notices as much as promotions. Reach an opted-out holder by email and the in-app notice, and make sure the notice on your site is complete enough that a user who never gets a text can still act in time.
Should the security advisory include a link?
No. Phishing texts that mimic your advisory will carry a link, and the only way a user can tell yours apart is that it never does. Tell them where in the app the update lives and state that you will never ask for a recovery phrase.
Run the next deadline from a line you own
Pair an Android handset to Android Texter, load the four quick replies, and send the ladder from a number that does not depend on a campaign review. The channel is yours. The consent records and the sentence about what happens after the deadline are still your job.