Signal alerts by email

Every VIP signal and every booking confirmation can land in your inbox as well as on the site and in Telegram. Add your address below, and if you run your own domain you can tell us which one alerts should be routed to.

Send alerts to my inbox

Useful if your mail server filters unknown senders — we allow-list the alert stream for that domain.

How the sender domain is verified

Alerts send from a domain SignalFlow owns and controls. This is the exact sequence — SPF and DKIM included — and it is the only thing standing between the current in-app confirmations and real inbox delivery.

1. Point a domain at SignalFlow

Use a domain you own (bought anywhere, or through Project Settings → Domains). Email alerts always send from your own brand — never a shared address — because that is what keeps inbox placement high.

2. Delegate a sending subdomain

Sending runs on a subdomain such as notify.yourdomain.com. You add the nameserver records shown in the email setup screen at your registrar; that subdomain is then managed for you.

3. SPF, DKIM and DMARC are created for you

Once the delegation resolves, SPF (which servers may send), DKIM (the cryptographic signature on every message) and the MX record are generated automatically inside that subdomain. No manual TXT records to copy.

4. Verification

DNS can take anywhere from a few minutes to 72 hours to propagate. When it verifies, the sender flips to active and every VIP signal alert and booking confirmation starts sending.

What gets sent once it's live

  • · New VIP signal — pair, direction, entry, stop, TP1 and TP2
  • · Booking confirmation — your reference and current status
  • · Status changes when a request is scheduled, published or declined