Messaging policy
RRCC helps the owner or operator decide what to do next before a lead goes cold. This policy explains how messaging is handled during the controlled beta.
RRCC does not send customer-facing email, SMS, or calls in the current public beta surfaces. Outbound remains a future approval-gated phase.
Current behavior
- RRCC may show suggested next actions, scripts, notes, or draft context to the operator.
- Operator activity may be recorded as history when a business chooses to use the workflow.
- Twilio and other provider foundations may be record-only/safe form only unless approved.
- Preview and beta surfaces must not imply that RRCC contacts customers by itself.
Business responsibilities
- The participating business is responsible for consent, opt-out, quiet-hour, and contact rules.
- The business decides whether to call, email, text, leave voicemail, or take no action.
- The business must not use RRCC to prepare deceptive, harassing, illegal, or unwanted messages.
- Any future send capability must pass owner approval, provider readiness, and compliance review.
Future outbound gates
- Documented consent and opt-out handling.
- Provider configuration review and spend controls.
- Human approval for customer-facing sends.
- Audit logging that records what was approved, by whom, and when.
Messaging policy questions should go to support@mail.getrrcc.com.
Back to RRCC