Frequently Asked Questions

DripLynx is a plug-and-play outreach automation platform for RVM, SMS, postcards, emails, and full campaign workflows. It helps businesses create campaigns, add selected contacts, schedule delivery, track jobs, manage callbacks, and work alongside the CRM or spreadsheet they already use.

No. Ringless voicemail is one channel inside the platform, but it is not the only focus. DripLynx is built around full automations, RVM, SMS, postcards, and email campaigns.

No. DripLynx is not meant to replace your CRM. It is the outreach automation layer that works alongside most CRMs through CSV imports, API workflows, webhooks, and custom field mapping.

It is built for insurance agents, sales teams, agencies, recruiters, real estate teams, contractors, appointment-based businesses, local businesses, and any company that has a contact list and needs consistent follow-up.

The platform is structured around five major areas: full automations, RVM, SMS, postcards, and emails. Each channel can be used by itself or combined into a larger follow-up workflow.

Yes. A business can use DripLynx only for RVM, only for SMS, only for postcards, only for email, or for combined automation workflows across multiple channels.

Yes. Contacts, consent fields, suppressions, campaign membership, and history are designed to work across the platform so the user does not have to manage separate lists for every outreach type.

A basic RVM sender is usually just a voicemail drop tool. DripLynx is being built as a broader automation workspace with multiple channels, campaign membership, scheduling, CRM-friendly imports, callback routing, notifications, billing, credits, and account controls.

Full automations are workflows that can trigger outreach based on dates, campaign membership, lead stages, contact fields, birthdays, renewals, manual actions, or future CRM events.

An automation can include RVM, SMS, postcards, emails, or a sequence that uses multiple channels together. For example: send an RVM first, follow up with SMS, send an email reminder, then send a postcard later.

Yes. Birthday campaigns can use contact DOB fields, and renewal-style workflows can be built around stored contact dates or imported CRM fields.

No. The goal is to connect to or work beside your CRM. Your CRM can keep storing records while DripLynx handles outreach execution, channel sequencing, and campaign tracking.

RVM stands for ringless voicemail. It allows a voicemail-style message to be delivered through supported provider workflows without being treated like a normal live phone call.

RVM campaigns can include browser recording, hosted audio URLs, campaign scheduling, birthday logic, selected campaign members, delivery jobs, failed-call notifications, callback routing, and contact-level history.

Yes. You can record voicemail audio in the browser or paste a hosted audio URL.

Yes. Failed delivery jobs can appear in delivery jobs, dashboard counts, notifications, and contact history.

SMS campaigns can be used for fast follow-up, reminders, confirmations, lead reactivation, appointment nudges, birthday messages, quote follow-up, and reply-driven workflows.

Yes. SMS should use the same controlled audience model, meaning contacts only receive SMS campaigns after being added to that campaign or workflow.

Yes. A workflow can use RVM and SMS together, such as sending a voicemail first and then sending a text follow-up later.

The intended workflow is to support reply and callback routing so responses can feed back into the business’s existing sales process, dialer, CRM, or phone workflow.

Postcards give businesses a physical follow-up channel for retention, renewals, local marketing, win-back campaigns, birthday mailers, seasonal promotions, and customer reminders.

Yes. Postcards should follow the same campaign membership model, so only selected contacts or selected segments receive the postcard campaign.

Yes. A business could run a sequence like email first, SMS reminder next, RVM follow-up later, and a postcard for contacts who still have not responded.

The intended structure is for postcard activity to be tied back to the contact record so the user can see outreach history in one place.

Email campaigns can be used for longer-form follow-up, announcements, newsletters, reminders, nurture campaigns, policy reviews, event notices, onboarding, and reactivation campaigns.

Yes. Email can be part of a multi-step workflow with RVM, SMS, and postcards.

Not necessarily. DripLynx is being designed around campaign execution and automation. Some businesses may use built-in email features, while others may use integrations with existing email tools.

Yes. Email should use the same contact and campaign membership structure so the user can manage outreach history across channels.

Contacts can include first name, last name, phone, email, date of birth, timezone, consent status, consent source, consent text, proof, notes, campaign membership, suppressions, and delivery history.

Yes. You can import contacts by CSV. Supported fields include first_name, last_name, phone, email, timezone, date_of_birth, has_consent, consent_source, consent_text, and proof.

Yes. Clicking a contact name opens the contact detail page where you can edit their information, add notes, see campaign membership, and view outreach history.

Global suppression blocks a number from every campaign. This is different from removing a contact from a single campaign.

Yes. Campaigns can be scheduled for a specific date and time, such as 9:00 AM on July 4th.

Yes. Birthday campaigns use the contact DOB field. You can send on the birthday or a selected number of days before the birthday.

Yes. The intended platform direction is for scheduling to support RVM, SMS, postcards, emails, and combined automation workflows.

Yes. Campaign schedules include timezone settings so scheduled sends run according to the selected timezone.

Yes. DripLynx is designed to work alongside most CRMs through CSV imports, API workflows, webhooks, and custom field mapping.

No. Your CRM can remain the source of truth. DripLynx handles outreach automation, campaign membership, scheduling, queueing, callback routing, delivery history, and multi-channel campaign workflows.

Common fields include name, phone, email, DOB, timezone, consent status, lead source, campaign segment, lifecycle stage, renewal date, owner, and custom identifiers.

Yes. Custom connectors can be built for proprietary CRMs, agency systems, industry CRMs, spreadsheets, dialers, or internal databases.

The Callback Number is the verified number selected when you create a campaign. When a client calls back through the provider number, the call can be routed back to the campaign's selected number.

Yes. A verified callback number is required when creating a campaign because it controls where callbacks should route.

No. Callback and reply routing can matter across multiple outreach channels, especially RVM and SMS.

Yes. You can store consent status, consent source, consent text, and proof on each contact.

No. DripLynx gives you workflow controls, consent fields, suppression controls, delivery history, and campaign membership tools, but you are responsible for how you use outreach campaigns and for following applicable laws, rules, and provider requirements.

No. Globally suppressed numbers are skipped when campaigns are queued.

Yes. A contact can be removed from a specific campaign without deleting the contact or removing them from every other campaign.

Yes. Use the Schedule Demo button to reach the demo page.

The account area is structured for Stripe-style billing, saved payment methods, subscription plans, and credit packs.

Credits are the usage balance for campaign activity. The account area can show current credits, credit purchases, and a breakdown of credits used.

Yes. The plan structure includes pay-as-you-go credit packs and monthly subscription options with included credits.

Yes. The intended workflow is self-serve: register, verify callback numbers, import contacts, create campaigns, add contacts to campaigns, and queue or schedule delivery.