JS8Call, created by Jordan Sherer, KN4CRD, takes the FT8 weak-signal modem (technically a modified, slower variant tuned for message integrity) and builds an actual messaging layer on top of it: free-text chat instead of fixed-format exchanges, store-and-forward, and relay through intermediate stations.
Why this matters for served agencies
Voice nets and even CW have a floor — past a certain point of weak signal or high noise, the operator on the other end simply can’t copy you. JS8Call’s underlying modem inherits FT8’s resistance to noise, so it keeps working in conditions where voice traffic has already broken down. On top of that:
- Relay — a station that can’t hear net control directly can route a message through another station that can, without anyone manually retyping anything
- Store-and-forward — JS8Call can queue a message for a station that’s temporarily off frequency and deliver it once that station reappears
- Heartbeat / APRS-style network view — JS8Call maintains a live picture of which stations are on frequency and reachable, which gives net control situational awareness without a full voice roll call
- Group messaging — messages can be addressed to a group callsign so multiple served-agency stations pick them up at once
Tradeoffs
Throughput is slow — JS8Call’s “normal” speed mode moves on the order of tens of words per minute equivalent, and the more robust modes are slower still. It’s built for getting a short, accurate message through reliably, not for high-volume traffic. Think formal message forms and status reports, not large file transfer (that’s a job for Winlink).