Sending RVM (Ringless Voicemail)

Drop Cowboy allows you to send ringless voicemail containing static audio or dynamic AI generated audio.

⚠️ Important: RVM Compliance & Sending Guidelines

All Ringless Voicemail (RVM) activity through Drop Cowboy must follow federal and state regulations, including the TCPA and Telemarketing Sales Rule (TSR).

Key compliance requirements:

• Obtain explicit consent from all recipients

• Provide a clear opt-out mechanism

• Use only approved number pools and audio recordings

Note: Drop Cowboy's API supports 1-to-1 RVM sends only — bulk or campaign-style submissions are not supported.

---

Sending Limits & Delivery Behavior

• Soft limit: 10,000 requests per second

  • Keep concurrent requests under 100 for best performance

• Scaling: If you plan to exceed 1,000 requests/sec, contact your Drop Cowboy account manager or support

• Contact frequency:

  • Default: 3 attempts in 3 days (TCPA)

  • FDCPA-regulated users: up to 7 attempts in 7 days (configurable)

• Delivery timing:

  • Most RVMs deliver within 5 minutes

  • Messages queued outside 8am–9pm local TCPA hours are automatically held until the next valid window

• Call forwarding: Avoid forwarding to toll-free numbers — some carriers block these connections, reducing callback success rates

---

Compliance Support

Drop Cowboy provides built-in tools and account-level configuration options to help you:

• Enforce contact attempt limits

• Manage local time compliance

• Track consent and opt-out requests

For advanced configurations or higher send volumes, contact Drop Cowboy Support or your account manager.

When sending RVM, you should be prepared to answer the following questions and configure your API request accordingly.

1. What account credentials are you sending from? (team_id and secret properties)

2. What registered brand in the account are we sending from? (brand_id property)

3. What caller ID should be shown for the customer to call back in response to the voicemail? (caller_id for explicit, forwarding_number for shared number pool use, or pool_id for private number pools depending on your use case)

4. What is the contacts phone number? (phone_number property)

5. Do we know the contact’s postal code? (postal_code property)

6. Are you sending static audio? (recording_id property or audio_url property if sending on BYOC SIP provider)

7. Are you sending generative AI based text to speech audio using Mimic AI? (tts_body and voice_id)

8. Is there an external record ID to tie delivery results back to your database? (foreign_id property)

9. Where should we send the delivery result? (callback_url property)

10. What format do you want the delivery results in? (callback_format property)

---

Explore our RVM Resources

• API Endpoint

• Webhooks

• Sending Limits

• Debugging