"Three new listings in your area dropped this morning."
2,400 avg list size
Upload a CSV, personalize with merge fields, and launch to thousands at once. Delivery, replies and STOPs update in real time — so you always know exactly how a send is performing.
$FIRST_NAME, $COMPANY, $CITY, $EMAIL, and any custom contact attribute.Drag in a CSV. Columns auto-map and every number is DNC-screened on the spot.
Write once with merge fields. The compliance checker scores it as you type.
Send to the whole list. Replies land in your inbox; STOPs suppress instantly.
Every inbound message runs through a two-stage responder — 20 preset response categories catch obvious replies first, then the AI takes the rest. Persona-aware, conversation-memory-aware, compliance-enforced.
Compliance auto-injected · STOP token added before send.
Conversation memory · last 10 turns recalled, no re-asking.
Last 10 messages passed back to the AI every turn. The model knows what was said earlier in the thread and responds in context.
Different sender personas reply differently — formal closer, friendly SDR, neutral support. Set per-organization, consistent across every thread.
Every AI response runs through the spam-scoring engine before send. Spam keywords, links, excessive punctuation — all blocked from the AI's mouth.
Configurable cadence — nudges continue until the lead responds or the cap is hit. Each follow-up can be AI-generated or pulled from your template library; admin picks per organization. Capped at 8 messages without an email capture to prevent spammy loops.
No shared defaults across tenants. Each org picks which AI model handles replies, sets its own daily caps, business hours, follow-up cadence, and approves which templates the AI can pull from. Settings apply org-wide the moment they're saved.
Which model handles inbound replies — switchable per org.
Per-user max auto-msgs / day. Default 6,000; tune up or down.
Open/close windows in any timezone. Default 8 AM – 7 PM ET.
Uniform delay between nudges, configurable per org.
Configure the personality your contacts text with. Set a name, age and gender, describe the style in plain English, or drop in custom rules — leave it blank and Fivra auto-generates a persona from the basics.
Configure the AI personality for this organization. Leave blank to use the default persona.
One rule per line, each starting with a dash. Leave blank for defaults.
Forty-seven rules — critical financial-services traps, urgency triggers, link shorteners, missing merge tags. Type a message and watch the score update on every keystroke.
Same rules the production sender runs against every message before it ships.
"Three new listings in your area dropped this morning."
"Hey {first}, did you have a chance to look at the proposal?"
"Solar credits expire end of month. Want a 10-min audit?"
"You're on the calendar Thursday at 2pm. Reply C to confirm."
Every template runs through the carrier-spam and TCPA wording check before it ships. 24 ready in your account on day one — categorized by industry, intent, and tone.
"Hey {first}, it's {agent} at {brokerage} — a new listing in {neighborhood} just hit at {price}. Want me to send details? Reply STOP to opt out."
"Hi {first}, following up on the {topic} thread — I have a 15-min slot at {time}. Worth a chat? Reply STOP to opt out."
"FINAL chance to lock at 6.2% before rates move!!! Click here NOW — limited offer expires tonight."
A full REST API for contacts, broadcasts, templates, analytics, and credits. JWT-authenticated, per-endpoint rate-limited. Native CRM connectors are on the roadmap — in the meantime, the API does what they would.
$ curl -X POST https://api.fivrasms.com/v1/... \ -H "Authorization: Bearer $YOUR_API_KEY" \ -H "Content-Type: application/json" \ -d @request.json # 200 OK { "id": "...", "status": "queued", "createdAt": "2026-05-29T14:02:00Z" }
No hard row limit. Lists are processed in chunks of up to 20,000 recipients with dynamic sub-batching (50–250 per sub-batch). Practical ceiling is a 10-minute per-transaction timeout, not the row count itself.
It depends on your active number pool. The token-bucket throttler defaults to 5 messages/sec with a burst of 10, capped to 3× your active DID count. A 10K-contact broadcast with ~6 numbers takes around 30 minutes; with 30+ numbers and a tuned rate cap, under 10.
Replies land in the team-visible inbox. Conversations are user-scoped by default; managers see their direct reports' conversations based on configurable visibility depth. You can also explicitly assign a conversation to another rep.
Synchronous handling — STOP, UNSUBSCRIBE, CANCEL, END, QUIT, OPT OUT, and REMOVE ME all trigger immediate account-wide suppression via the master suppression list. An auto-confirmation reply goes out.
Yes. Schedule by date and time (platform timezone) or set a drip rate (messages per hour) for slow rollout. A background cron processes due messages every minute. Per-recipient timezone scheduling and CRM event triggers are not built today.
$FIRST_NAME, $LAST_NAME, $AGENT_FIRST_NAME, $COMPANY, $EMAIL, $CITY, $STATE, plus any tag or attribute on the contact record.
Claude-powered template writing — describe the use case and tone, get a drafted message with compliance scoring built into the response. Each generated template runs through the same spam-scoring engine before it's saved.
Free tier handles 500 contacts. No credit card to start, no setup fee, no contracts.