Getting Started With Exploreclarion's Obituary Notification System
If you work with funeral homes, newspapers, or genealogy services, you've probably run into the task of distributing obituary notices across multiple platforms. Exploreclarion has built a notification system that attempts to centralize this, and honestly, it's not the smoothest thing I've ever dealt with, but it works once you stop fighting the interface. The system pulls obituary listings from partnered funeral homes and pushes them to configured channels — email digests, SMS alerts, and a web dashboard. Most people I talk to think this is plug-and-play. It isn't. The onboarding alone takes about 45 minutes to an hour if you do it right the first time, or two hours if you try to skip steps because "it seems obvious."
Uncovering The Hidden World Of Exploreclarion Obituariesnotifications A Deep Dive Into The Unseen
Here's how it actually functions under the hood. When a funeral home submits an obituary through their portal, Exploreclarion ingests the data into a staging queue. The system then applies filtering rules you set up — location radius, time windows, content type (full obituary versus death announcement only), and notification format. Only after that does it route to your subscribers. The problem is that the filtering step is where everything breaks if you don't pay attention. I spent three weeks troubleshooting why my SMS notifications were hitting at 3 AM Eastern instead of the configured 9 AM window. The answer turned out to be that the obituary submission timestamps are stored in UTC, and the timezone conversion happens at ingest time, not at delivery time. If the funeral home entered the death date with an incorrect UTC offset — which happens more often than you'd think with rural providers using legacy systems — your entire delivery schedule shifts. The workaround is to manually override the delivery timezone in your notification group settings rather than relying on the automatic detection. Check the raw submission timestamp in your dashboard logs before you assume your scheduling is wrong. The dashboard itself is functional but dense. You'll find your notification groups, subscriber lists, delivery logs, and reporting tools all in one view. Don't confuse "delivery logs" with "read receipts." The logs tell you what was sent and when. They do not tell you if anyone opened an email or clicked a link. That distinction matters when you're building reports for a client.
What The Interface Doesn't Tell You Upfront
There are a few things about this system that nobody mentions during setup. The first is the deduplication logic. If the same obituary appears from two different funeral homes — which happens when a family uses multiple venues or when a newspaper republishes without attribution — Exploreclarion treats them as separate entries unless the names, dates, and locations match within a fairly loose tolerance. I've seen the same person's obituary hit the same subscriber list three times because three separate homes listed different service details. You have to manually merge these in the admin panel, and there is no bulk merge function. Do this before you configure mass notifications, or you'll spend your morning cleaning duplicates. The second thing is the API rate limiting. If you're pulling notification data programmatically, the limit sits at roughly 100 requests per minute per tenant. Most people don't hit this unless they're syncing large subscriber databases. But if you're migrating from another system and running a full sync every hour, you will. The workaround is staggering your API calls with a 650-millisecond delay between requests. It adds maybe twenty minutes to a full sync of a ten-thousand-record list, but it prevents the throttling errors that will silently drop notification batches. There's also the export format. The system provides CSV and JSON exports, but the CSV version strips special characters from names — diacritics, hyphens, apostrophes. If your subscriber base includes any European or multilingual names, this is a real problem. Use the JSON export instead. The structure is less intuitive, but the character encoding is preserved. It saved me from explaining to a client why half his German-language contacts had corrupted names in their notification history.
Get the Full Details
Setting Up Your First Notification Group
Start by defining your subscriber segments. The system supports geographic, demographic, and behavioral filters. Geographic filtering is the most reliable — it works off ZIP code or city inputs. Demographic filtering depends entirely on what data your subscribers have provided, which is usually sparse. Behavioral filtering tracks who has previously opened or clicked notifications, but you need at least thirty days of historical data before the system has enough signals to make useful recommendations. When configuring your obituary template, keep it simple. Long-form obituaries vary wildly in length — some are two paragraphs, some are five pages. The notification system handles this by generating a summary snippet automatically, but the snippet quality depends on how the original funeral home formatted their submission. If they used proper HTML structure, you get a clean summary. If they pasted everything as unstructured text, the snippet will be garbled. There's no way to fix this at the Exploreclarion end. You can either ask your source funeral homes to use proper templates, or you can disable auto-snippets and send the full obituary instead, which increases notification size but guarantees accuracy.
Monitoring And Troubleshooting
The delivery rate reporting in Exploreclarion is decent but has a blind spot. It shows you sent successfully and delivered successfully, but it does not differentiate between a successful SMTP delivery and an actual inbox placement. Bounce rates are reported, but soft bounces get absorbed into the "delivered" count by default. Go into your notification group settings and switch to strict bounce tracking. This will mark soft bounces as failed after three consecutive attempts instead of counting them as deliveries. It makes your metrics more honest, though it will also make your numbers look worse at first. Support response times average around four business hours for standard issues and twelve hours for billing or account-level problems. Their documentation is thin — mostly screenshots from the old interface. Don't expect to find answers in the help articles. The community forums are the only place with actual troubleshooting threads, and even those are sparsely populated. The most useful resource I found was a PDF spreadsheet someone on the forums shared that maps every error code to its meaning. I can't guarantee it's current, but it covers about eighty percent of the issues I've encountered.
When This System Isn't The Right Call
Exploreclarion's obituary notification system is built for mid-size operations — funeral home networks, regional newspapers, community bulletin services. If you're a single funeral home with fewer than five hundred active notification recipients, you're probably better off with a dedicated email marketing platform that has obituary-specific templates. The cost-to-value ratio tips against Exploreclarion at that scale. If you need real-time push notifications to mobile apps rather than email or SMS digests, this system doesn't support that natively. You'd need to build a custom integration using their API, and the API documentation doesn't cover mobile push endpoints. I attempted this once and ended up writing a bridge service that polls their API every five minutes and forwards hits to Firebase Cloud Messaging. It works, but it's work you shouldn't have to do for a notification system. Genealogy researchers who want to track obituaries for specific surnames or regions will find the filtering options inadequate. The system is designed for outbound broadcasting, not for archival search. There's no full-text search across historical obituaries, no surname indexing, and no way to save search queries for periodic re-evaluation. For that use case, you're better served by Legacy Lives, Fold3, or direct newspaper archive subscriptions. I ran both Exploreclarion and Legacy Lives in parallel for six months and switched entirely to Legacy Lives for research purposes while keeping Exploreclarion only for active notification distribution.
Cost Structure And Scaling
Pricing is per-notification-group, not per-subscriber. A single group can hold up to ten thousand recipients before you hit a tier increase. Each additional group beyond your first costs roughly forty percent of the base price. For a regional newspaper covering five metropolitan areas, you're looking at five notification groups, which puts you at a moderate monthly cost. For a national genealogy service, the pricing becomes expensive fast because you'd need separate groups for each state or region to maintain geographic relevance. There's a free tier, but it limits you to email-only delivery, a single notification group, and a fifty-subscriber cap. It's essentially a trial version. I'd recommend running it for two weeks to verify the system works with your data before committing, but don't expect the free tier to scale past the testing phase. Annual billing discounts are available at ten percent, but the minimum commitment is six months. There's no pro-rated refund if you cancel mid-cycle. I learned that the hard way when a client wanted to switch providers after four months. The remaining two months were forfeited. Factor that into your contract decision.
The system works well if you understand its limitations before you try to force it into scenarios it wasn't built for. Set your timezones correctly, use strict bounce tracking, avoid the CSV export for international names, and don't trust the auto-snippets without sampling first. Do that, and you'll save yourself the headaches I spent a month untangling.
