How Rapid Cortex Sends Text Messages
This page covers two distinct SMS workflows: general platform communications, and dispatcher-initiated incident-specific messaging. Published as a public reference for carrier compliance and toll-free verification.
Last reviewed August 1, 2026
General Platform SMS Consent
SMS consent for Rapid Cortex platform users — demo scheduling, onboarding, account access, and support communications.
By providing a mobile number through Rapid Cortex forms or approved agency workflows, you consent to receive SMS messages related to demo scheduling, onboarding, account access, support, or authorized Rapid Cortex communications.
Message and data rates may apply. Message frequency may vary. You may reply STOP to opt out or HELP for assistance where supported.
SMS consent is not required to purchase Rapid Cortex services unless SMS-based communication is part of the approved agency workflow.
Dispatcher-Initiated, Incident-Specific SMS
How Rapid Cortex supports dispatcher-initiated, incident-specific communication with 911 and public safety callers. Published as a public reference for toll-free number verification and carrier compliance.
Purpose of SMS
Rapid Cortex SMS is used only for dispatcher-initiated, incident-specific outreach tied to an active public safety contact. Recipients are individuals who have contacted 911 or another public safety communications center and are engaged in that incident context. Messages are not sent for marketing, promotions, advertising, or unsolicited outreach.
How Consent Is Collected
Live, On-Call Verbal Agreement
Before an SMS is sent, a trained public safety telecommunicator obtains the caller's (or other involved party's) agreement on the recorded or monitored voice channel, in line with agency policy and applicable law.
Platform Attestation Before Send
Dispatchers record consent by confirming within the Rapid Cortex application that the required verbal consent was obtained before the system sends the message. No message is sent from Rapid Cortex for this workflow without that confirmation.
“I'm going to send you a text message from our agency's number to help with [state the incident-specific purpose — for example, a secure link to upload a photo or video, a link to clarify a location, or translation assistance]. This text is only for this incident — not for marketing. Standard message and data rates may apply. Do you agree to receive this text?”
Agencies may adapt wording to policy; the script above reflects the intended meaning for toll-free and carrier disclosure. The dispatcher proceeds only after an affirmative response (for example, “yes,” “I agree,” or equivalent) consistent with agency procedures.
What SMS Messages May Include
Incident-related content may include, as appropriate to the situation:
- Secure upload links for photos or video related to the active incident
- Location clarification links
- Translation or language-assistance links
- Incident-specific follow-up instructions
- Requests for information related to the active incident
Consent Records
When an agency uses Rapid Cortex for this workflow, the platform is designed to support an auditable record aligned to agency operations. Depending on configuration, consent-related records may include fields such as:
| Agency ID | Identifies the public safety agency that initiated the workflow |
| Dispatcher user ID | The authenticated telecommunicator who attested verbal consent |
| Incident ID | Links the consent record to the active incident |
| Caller phone number | E.164 format or as stored per agency policy |
| Timestamp | Date and time of dispatcher attestation |
| Message purpose | Category or description tied to the incident |
| Consent confirmation | Dispatcher attestation that verbal consent was obtained |
Exact fields and retention follow the agency's configuration, contract, and applicable law. The privacy policy describes personal data handling at a high level.
STOP, HELP, and Frequency
| STOP | Recipients may reply STOP to opt out of further SMS from that workflow where supported by the carrier and agency configuration. Reply STOP may not unsubscribe the caller from emergency voice service or other non-SMS channels. |
| HELP | Recipients may reply HELP for a short explanation of the program or a support contact provided by the agency, when available. |
| Frequency & rates | Message frequency varies with incident activity. Message and data rates may apply. |
No Sale of SMS Consent for Marketing
We do not share, sell, or provide your mobile phone number or messaging consent data to third parties or affiliates for marketing or promotional purposes. SMS consent obtained for this dispatcher-initiated, incident-specific workflow is used only to deliver incident-related messages and operate the service. Communications are limited to public safety incident workflows and authorized agency use of Rapid Cortex.
Operator
Rapid Cortex is offered by Apps on Demand. For questions about this disclosure, contact your agency administrator or reach us via the contact page.
This page is publicly accessible without login for regulatory and carrier compliance review purposes.