One pipeline, not twoWeb visitors type it, callers say it. Both end up as entries in the same form, with the same fields, in your WordPress dashboard.
Notifications you already builtA phone entry triggers the same notifications and confirmations as a web submission: the alert email, the routing, all of it.
Exports that stay wholeEntry exports and reports cover every lead, however it arrived, with no merging a call log into your form data at month's end.
An Entry Like Any Other
ABBY PORTAL · CALL SUMMARY
ANSWERED BY ABBY · 10:19 AMDuane Hollis
(614) 555-0117 · 5 min · New caller
Wants a quote on about 120 feet of cedar privacy fence; hoping for an install next month.
New leadQuote request
→GRAVITY FORMS · ENTRY #2417
FormRequest a Quote
NameDuane Hollis
Phone(614) 555-0117
ProjectCedar privacy fence · approx. 120 ft
TimelineNext month
SourcePhone intake · Abby
NotificationSent to sales@ · 10:22 AM
A homeowner calls about a fence project. Abby answers in your company's name and walks through the same questions your 'Request a Quote' form asks online: project type, footage, timeline, best contact.
The result is a Gravity Forms entry sitting in your dashboard next to the web submissions, notification already sent to your sales inbox. From WordPress's point of view, it's an entry like any other. From the caller's point of view, it was just a pleasant conversation.
Your Notifications Already Know What To Do
The reason to file calls into Gravity Forms instead of a separate call log is everything you've already wired to it: notification emails that route by service area, confirmations, conditional logic, add-on feeds pushing entries to your email list or CRM. A phone entry inherits all of it the moment it's submitted.
That's the WordPress way: one plugin, one pipeline, one place to look. Your team keeps checking the Entries screen they already check, and the phone stops being the lead source that lives on sticky notes.
Anatomy Of A Phone-Born Entry
1The form itselfThe same Gravity Form your website serves, with no shadow copy to keep in sync. Abby's intake script is built from its fields during onboarding.
2Contact fieldsName, phone, and email captured on the call and formatted the way each field expects, so validation, exports, and feeds behave.
3Choice fieldsDropdowns and radios are selected from what the caller actually said, which keeps your conditional logic and routing rules meaningful.
4The message fieldA plain-language summary of the conversation: what they need, when they're available, what was promised on the call.
5The source markerEntries are marked as phone intake per your setup, so you can filter the Entries screen and report web against phone.
6What fires nextNotifications, confirmations, and add-on feeds run exactly as they do for a web submission, because to Gravity Forms, it is one.
Where WordPress Answers The Phone
The contact form, spoken aloudSome customers will never type into a form; they call. Abby asks your form's questions in conversation and submits the entry for them.
Quote requests with complete fieldsProject type, size, timeline: the fields your estimate workflow needs are collected on the call, so quoting starts immediately.
Add-on feeds keep workingEntries Abby submits run through your add-on feeds like any other (the email platform, the CRM, the spreadsheet), exactly as configured.
Intake your site ownsEverything lands in your WordPress database, on your domain, in the plugin you already trust. No second intake system to subscribe to.
How It Works
1Onboarding builds Abby's intake script from your Gravity Form: its fields, its required questions, its choices.
2Abby's receptionists answer 24/7 and gather the answers in conversation, following your instructions.
3The call is submitted as an entry; it appears on your Entries screen, and your notifications and feeds fire as usual.
FAQs
Does Abby's virtual receptionist work with Gravity Forms?
Yes. Calls Abby answers are submitted as entries to the Gravity Form you choose, with the fields filled from the conversation.
Do notifications and add-on feeds fire for phone entries?
Yes. An entry Abby submits is a normal Gravity Forms entry, so notifications, confirmations, and configured feeds all run.
What about required fields and conditional logic?
Onboarding maps your form to the intake script: required fields become questions Abby always asks, and choice fields are answered with your form's own options.
Where does the data live?
In your WordPress database, like every other entry. Filter phone entries on the Entries screen, export them, or feed them onward. You own all of it.
We use a different WordPress forms plugin. Can you support it?
Almost certainly. If your plugin isn't in our catalog yet, we build the integration during onboarding at no charge, and Abby's AI receptionist option files entries the same way.
Use a tool we haven’t listed?
We build missing integrations for new customers during onboarding, free. Tell us what you run on and we’ll connect it.
Schedule a CallCall 877-303-5757