Alert your fans when you go live.*
Give people who actually want to hear from you a simple way to know when you are live, so fewer regular listeners discover the stream after it has finished.
Permission, not pestering
Live Sharing is designed around affirmative choice. Creating an invitation does not quietly enrol somebody. The recipient must opt in before a supported alert route can treat them as eligible. That choice is only for Live Sharing alerts; it does not sign the recipient up for marketing, newsletters or promotions. After STOP, alerts stay off until the recipient makes a fresh opt-in choice.
Why it matters
You can spend hours preparing a stream and still have regular listeners say “I wish I’d known”. A useful live alert is about helping the people who already want to be there find the room at the right time.
Availability depends on the messaging service and its current rules. Live messaging stays off until the consent, permission, account and delivery journeys have passed the required real-service checks.
Real Live Sharing interface
This is a genuine test-screen capture. The current source still contains the consent-first Live Sharing workflow.
Top tips
- Enter the recipient phone number in full international format beginning with + and the country code. If RigWave cannot safely understand it, correct the number rather than guessing.
- Check the exact recipient, account and link before sending.
- Your RigWave acknowledgement is not the recipient’s consent.
- Respect STOP, unsubscribe, blocking and objections.
LIVE SHARE · MUST READ
Lawful, responsible sharing is a condition of use
Before Live Share or connected-chat controls unlock, RigWave presents separate required tick boxes for: account and destination authority; copyright and other content rights; privacy and recipient permission; no bullying, harassment or harmful misuse; third-party app rules; checking before sending; and end-user responsibility. The accepted wording version and time are stored on that PC so the same checklist is not repeated on every launch. A material change to the requirements triggers a fresh acknowledgement.
The acknowledgement is not another person’s consent, does not grant access to an account or destination, and does not prove delivery. The operator must already have any permission, consent or lawful basis required for each recipient, purpose and channel; must check the actual message, link, account, audience and recipient; and must honour STOP, blocking, objections and withdrawal.
Never use RigWave for bullying, harassment, stalking, threats, discrimination, doxxing, impersonation, deception, spam, fraud, unlawful surveillance or exploitation. Misuse can harm people and damage the RigWave brand. Police.uk online harassment and threatening-message help ↗ · Report Harmful Content ↗.
If WhatsApp, Messenger, Facebook or another third-party desktop/web app is used, install or open its official app, sign in and authorise there, approve only the permissions needed, protect credentials, and comply with its current terms, policies, recipient controls, templates, moderation, rate limits and charges. RigWave does not control or guarantee the service. WhatsApp official app-link guidance ↗. If a message is direct marketing, review the ICO electronic-mail marketing guidance ↗ before use.
Clear next steps without the guesswork.
Explore plans and guided setup. Downloads and checkout are not open yet.