Consider a cleaning inquiry that says twice a month. The coordinator records every two weeks. That small change creates a different schedule. A form can collect a complete answer while leaving the repeat pattern unclear.
Recurring service requests need a repeat pattern, a preferred start and an end rule when one applies. Collect those details for staff review before anyone turns the request into appointments or billing.
Separate one visit from repeated service
Start with a plain choice such as One visit, Repeated service or I need advice. Avoid making visitors choose a subscription plan when they are only asking about service. A recurring request can still need a quote or a conversation.
For repeated service, ask How often would you like the service? Use the choices the business actually offers, plus a way to describe an unusual pattern. Keep frequency separate from the number of visits when both affect the review.
If your form builder supports conditional logic, show repeat questions only when they apply. The guide to conditional form logic explains the broader approach. Put the repeat rule in visible instructions beside the choice, as W3C’s form instructions guidance recommends.
Name the repeat pattern precisely
Avoid a choice labeled biweekly. It can leave staff unsure whether the visitor means twice a week or every two weeks. Write the intended pattern in full.
Every four weeks and once each calendar month also differ. Keep the visitor’s selected wording in the saved request and the staff brief. Do not silently convert one pattern into another for convenience.
For a business that offers two monthly visits, a follow-up can ask Which dates or weeks would you prefer? If the visitor requests the first and third Mondays, preserve that wording for the coordinator. The form is collecting a preference, not deciding the calendar.
| Visitor means | Clear form wording |
|---|---|
| One visit each week | Once a week |
| One visit every second week | Every two weeks |
| Two visits in each calendar month | Twice each calendar month |
| Dates vary | Describe the requested pattern |
Collect the start and end preferences
Ask for a preferred start date when your intake process uses it for a quote or staffing review. If there is a preferred day or time window, label it as a preference. Staff still need to confirm availability.
Ask whether the service is ongoing, ends on a date or covers a stated number of visits. Use only options the business can discuss. A request for six visits should remain six visits in the brief.
Seasonal pauses and exceptions belong beside the pattern when they matter. For example, a fictional request might say Every two weeks from November through January, except the holiday closure. If the visitor is unsure, preserve that uncertainty and ask a focused follow-up.
Keep precise clock times with their zone when needed. The time-zone guide covers that separate timing question.
Keep AI review separate from scheduling
Where configured, the Entry Summary action can organize submitted information into a staff review aid. Check that it preserves frequency, preferences, end conditions and exceptions.
A fictional test request might say Every two weeks, Tuesday morning if possible, six visits, start date to confirm. A useful brief preserves all four details and identifies the dates as unconfirmed. Compare it with the original submission before planning the work.
The Missing Information Review action can propose follow-up questions for unclear details. Staff review the question and confirm the service through the business’s existing process. This is not an appointment scheduler or a recurring billing setup.
Sentient Forms supports Gravity Forms, Contact Form 7, WPForms, and Elementor Pro Forms. For after-submission review with Contact Form 7, WPForms, and Elementor Pro Forms, enable the Submission Ledger. Native entry features vary by builder. The current plugin listing describes those boundaries.
Test the whole repeat request
Use fictional submissions for one visit, every two weeks, twice per calendar month and six visits with a pause. Include an undecided start date. Check the saved record, any notification your configured workflow sends, and the staff review aid.
Each result should preserve the requested pattern without promising dates, availability or charges. If a brief drops an end rule, fix the review instructions and retest before relying on it.
You can track requests needing clarification about frequency or duration over a fixed review window. Compare the same form and service type before and after the field change. Record what question staff had to ask. This observation plan does not claim that the new form has already saved time.
Frequently asked questions
No. Every two weeks follows a fourteen-day interval. Twice per calendar month requests two visits in each month. Preserve the selected pattern and let staff confirm the actual dates.
A configured Sentient Forms review action prepares information for review; it does not create appointments or charges. The business’s scheduling and billing systems, configured workflow and required confirmations govern those steps.
Provide an option to describe the need or ask for advice. Keep the pattern unresolved in the staff brief and ask a focused question before confirming service.
If a service form receives vague repeat requests, replace one unclear frequency label. Submit Every two weeks for six visits as a fictional test, then check that both the interval and the visit limit reach the staff brief. Record any clarification still needed. Explore Sentient Forms review actions.
