A homeowner fills out your quote form on their lunch break. They’re comparing prices today, and they’ve probably asked more than one agency. If that lead sits in an inbox until someone exports it, re-keys it, or notices it, the first call may come after they’ve already talked to someone else.
If your team runs on Ringy, the fix doesn’t have to be another connector or another manual step. The new GravityCerts + Ringy integration sends every website form submission straight into Ringy as a new lead, so your agents can call or text within seconds. It’s built into the GravityCerts plugin and included with every GravityCerts plan.
Here’s why that handoff matters, how the integration works, and what happens on the rare occasion a lead doesn’t go through.
Why Speed to Lead Matters for Insurance Agencies
Speed to lead is the time between someone asking for help and your agency actually responding. One of the most cited studies on the topic, “The Short Life of Online Sales Leads” in Harvard Business Review, found that firms trying to reach online leads within an hour were nearly seven times as likely to have a meaningful conversation with a decision maker as firms that waited even one hour longer.
That research dates to 2011 and wasn’t specific to insurance, so it won’t predict your exact numbers. The underlying logic still fits agency life, though. A person requesting a quote has a reason to act right now: a renewal increase, a new car, a closing date, a contract that requires proof of coverage. That moment fades quickly, and a faster call gives your producer a better chance of catching it.
You can’t control how fast a producer picks up the phone with website settings alone. You can make sure the lead is already waiting in the dialer when they do.
Where Website Leads Get Stuck on the Way to Ringy
Agencies running Ringy usually get web leads there in one of three ways, and each one leaves a gap:
- By hand. Someone reads a notification email and types the lead in. It works until that person is busy, out, or asleep.
- By CSV import. Leads pile up and move in batches, which is the opposite of speed to lead.
- Through a generic connector. Zapier-style tools are faster, but they often pass only name, email and phone. They can also add per-task fees, and when a connection breaks, nobody may find out until leads have already gone missing.
The result is a lead that arrives late, arrives thin, or doesn’t arrive at all. If you want a broader look at this problem across your systems, our insurance agency CRM integration guide is a good place to start.
How the GravityCerts + Ringy Integration Works
Ringy is a built-in action in the GravityCerts plugin’s Gravity Forms feeds. There’s no extra plugin to install and no Zapier account to maintain. Once a form has a Ringy feed, the handoff runs in four steps:
- A visitor submits the form.
- GravityCerts builds the lead from your feed’s field mapping and sends it securely to Ringy’s lead-vendor API, using your agency’s own SID and Auth Token.
- Ringy replies with a Lead ID, and the result is saved on the form entry.
- If Ringy didn’t take the lead, the plugin retries or flags it, depending on why.
Here’s what that looks like from the visitor’s form to your team’s dialer:
- Products
- Auto, Home
- ZIP code
- 90210
- Lead source
- Website form
Send More Than a Name and a Phone Number
A fast lead is more useful when your producer knows what the person asked for. Each form gets its own feed, and nothing is hard-coded to a form or field ID, so this works on quote forms, contact forms and ad landing pages alike.
Name, email and phone are mapped with dropdowns. Phone is required, and it’s cleaned up automatically: numbers are reduced to 10 digits and a leading 1 is removed, so “1-202-555-0114” arrives as 2025550114.
Everything else goes in the Additional Fields table. Depending on your form, you might send:
- ZIP code, products requested, and notes
- Lead source or the page URL the visitor came from
- UTM source, medium, campaign, term and content
- Click IDs such as gclid, fbclid and msclkid
- Any custom field you’ve set up in Ringy
Ringy doesn’t publish a fixed field list. The accepted names are whatever you map on your Ringy lead vendor, and they’re case sensitive, so zip_code and Zip_Code aren’t the same field. To add a new one, type the name in the vendor’s field mapping, then use that same name in your feed. Ad tracking values also need hidden fields on your form to capture them. For marketers running paid campaigns for insurance clients, that means the source of each lead can travel into Ringy with it.
Decide Which Leads Go Where
By default, every submission is sent. Conditional logic on the feed lets you narrow that down with rules such as:
- Send only if the Producer field is empty, to skip leads that already have an owner
- Send only if Auto is checked, to keep one line of business in a specific workflow
- Send only if the consent box is ticked
That last one is worth a closer look. Ringy is a calling and texting tool, and a fast response doesn’t replace your agency’s consent obligations. Make sure your form collects whatever consent your agency requires, then use the feed condition to keep leads without it out of the dialer.
You can also send different forms to different Ringy lead vendors. A feed can override the site’s SID and Auth Token with its own, as long as you fill in both, so your ad landing page and your main quote form can show up in Ringy as separate lead sources.
What Happens When a Lead Doesn’t Go Through
This is where a built-in integration earns its keep. Connections fail, credentials get changed, and forms get edited. What matters is whether anyone can tell, and whether the lead is safe when it happens.
Every entry shows the outcome in a Ringy box: the status, Lead ID, Vendor Response ID, HTTP status, attempts, and any error message. The entry notes get a line too. Choose a scenario below to see how each one plays out:
- Form submittedA visitor sends your form
- Feed conditionYour rules decide if it should go
- Spam checkSpam entries are never sent
- Phone numberCleaned to 10 digits
- Sent to RingyWith your SID and Auth Token
- Ringy repliesThe result is saved on the entry
Ringy returned a Lead ID. The entry notes get a line, the Ringy Completed notification can fire, and this lead won't be re-sent automatically.
- Lead ID
- 7c1e40b2-93d6-4a57
- HTTP status
- 200
- Attempts
- 1
Three protections sit behind those outcomes:
- Automatic retries. If Ringy is down or the connection fails, the plugin tries up to 3 more times, after about 1, 5 and 15 minutes.
- Duplicate protection. A lead Ringy accepted is never re-sent automatically, and two processes can’t send the same entry at the same time. If you click Resend to Ringy on a lead it already has, you’re asked to confirm first.
- Safe handling. Spam entries are never sent, credentials are never written to logs, and a lead Ringy rejects is flagged instead of retried.
You can also use the “Ringy Completed” event to trigger a Gravity Forms notification, such as an email to the agent, as soon as a lead is accepted.
How to Set It Up in About 15 Minutes
A WordPress admin on your agency’s site can do this without a developer. You’ll need a Ringy account with permission to manage Lead Vendors.
- Get your Ringy details. Create or edit a Lead Vendor in Ringy, then copy the SID and Auth Token from Integration Details.
- Save them on your site. Go to Forms > Settings > GravityCerts, find the Ringy box, paste both values and save. You only do this once per site.
- Add a feed to each form. On the form, go to Settings > GravityCerts > Add New and choose Ringy as the Action. Map name, email and phone, then add extra fields and conditions if you want them.
- Test it. Submit the form, open the entry, and look for “Accepted by Ringy” and a Lead ID in the Ringy box.
One heads up: a test lead is a real lead in Ringy, so it can trigger calls or texts to the number you used. Use a phone number you control, let your team know before you test, and delete the test lead afterward.
The full walkthrough is in our support articles: Enabling the Ringy integration and How to send form submissions to Ringy.
Make the Most of a Faster Handoff
Getting the lead into Ringy quickly removes the delay on your website’s side. The rest is up to your process. A few habits help that speed pay off:
- Decide who owns new web leads before they arrive, so nobody assumes someone else is calling.
- Map what your producers actually use. Products requested and ZIP code help on the first call. A dozen fields nobody reads don’t.
- Keep your forms focused. A well-built quote form collects what your team needs without scaring people off on a phone.
- Check the Ringy box when something looks off. You don’t have to guess whether a lead made it. The entry will tell you.
Frequently Asked Questions
Does the Ringy integration need Zapier or a separate plugin?
No. Ringy is a built-in action in the GravityCerts plugin’s Gravity Forms feeds, so there’s nothing extra to install and there are no per-task fees.
Which GravityCerts plans include Ringy?
Every plan. You just need your own Ringy account.
How quickly does a lead reach Ringy?
Each submission is sent automatically, so a lead is normally in Ringy within seconds and your agents can call or text right away.
What information can I send to Ringy?
Name, email and phone, plus anything else you map in the Additional Fields table, such as ZIP code, products requested, notes, lead source, page URL, UTM values, click IDs, or Ringy custom fields. The field names must match your Ringy lead vendor exactly, including capital letters.
What happens if Ringy is down?
The plugin retries up to 3 more times automatically, after about 1, 5 and 15 minutes. If it still fails, the entry shows Failed and can be resent.
Can the integration create duplicate leads?
The same entry won’t be re-sent automatically once Ringy accepts it, and a manual resend asks you to confirm first. The integration doesn’t look up existing contacts in Ringy, so someone who submits your form twice is sent as two separate submissions.
What’s the minimum a lead needs to be sent?
A phone number. Without one the lead isn’t sent, and the entry says why.
Can different forms go to different Ringy lead vendors?
Yes. Fill in both the Lead Vendor SID and Lead Vendor Auth Token on that form’s feed, and it will use those instead of the site-wide settings.
Does the integration pull data back from Ringy?
No. It only sends leads to Ringy. Lead status and call outcomes stay in Ringy.
Do I need a developer to set it up?
No. A WordPress admin can set it up in about 15 minutes.
Getting Started
If you’re already on GravityCerts and using Ringy, you can turn this on today by following the setup guide. To see everything it does, visit the GravityCerts + Ringy integration page. New to GravityCerts? Book a demo to walk through it with our team, or view pricing to get started.