Keep the form respectful and direct
Families may be contacting the cemetery during a difficult moment. A service request form should use plain language, avoid unnecessary fields, and clearly explain what happens after submission.
The form should collect enough information for staff to respond without asking families to repeat themselves: name, contact method, request type, related loved one or plot if known, preferred language, and message.
Route each request to a real workflow
A public form is only useful if staff can see, assign, and close the request. Requests should be categorized, timestamped, tied to the tenant, and visible in the dashboard with status and internal notes.
That workflow helps cemetery staff respond consistently and gives administrators a record of what came in.
- Use categories such as records, services, documents, memorials, and general contact.
- Show staff the source page and submitted details.
- Allow internal notes without exposing them to the family.
- Track status so requests do not disappear.
Treat spam protection as part of the product
Cemetery forms can be targeted by bots just like any other public website. Honeypots, rate limiting, suspicious-link scoring, and review queues help protect staff time without making legitimate families struggle.
A good spam system is quiet when families are real and firm when behavior looks abusive.