💡 Feature Requests

Allow account-level (or per-list) configuration of "inactive" criteria, combining: Time-based rule: Contact is marked inactive if not uploaded/added to any list within X days (customer-configurable; DJ suggested starting at 30-60 days). Engagement-based rule: Contact is marked inactive if no click (or other defined engagement event — reply, opt-in confirmation, etc.) within Y days (DJ suggested 90 days). Logic combination: Contact should be treated as active if EITHER condition is met (recently uploaded OR recently engaged) — inactive only if both thresholds are exceeded. Inactive contacts should be automatically excluded from active sends/campaigns without requiring manual list management, but remain in the account (not deleted) and be eligible to re-activate if they later engage or are re-uploaded.

As a user, I want the ability to A/B test my text message.

As a customer, when someone replies to one of our SMS or MMS, I want to get an email with the name of the Broadcast, Campaign, or Trigger. Also, all the default contact info of the person who replied and the actual message they sent.

As a user, I'd like the ability to show my company name as the caller ID for my ringless voicemails.

I want the ability to use the Call Loop API.

As a user, I want to see a dashboard to see the stats on my account for broadcasts, campaigns, triggers, and more.

As a customer, I want to filter out or segment contacts that return specific error codes after an SMS broadcast.

Some of our members have picked up the phone on the first ring and heard silence. Then they called us asking why we called. We’d like to see the system play the voicemail recording when they pick up the phone instead of silence.

As a user I want to send RCS messages.

Summary: AI-powered inbox: classify and auto-respond to abandoned cart & welcome series replies using natural language Description: E-commerce customers running abandoned cart and welcome series campaigns need intelligent reply handling beyond basic keyword matching. The request is for an AI layer that classifies inbound SMS/voice replies in natural language, then automatically responds with contextually appropriate copy or triggers an opt-out. Handling edge cases like ambiguous questions, objections, and intent signals that keyword triggers miss entirely.