Submits the approved obituary to every outlet against its own deadline, confirms it actually published, and changes nothing the family wrote.
The obituary is one of the few deliverables in a funeral where the deadline belongs to a third party and the consequence of missing it is permanent. A notice has to appear before the service, because it is how people find out when and where the service is. Each outlet has its own submission deadline, its own format requirements and its own process — a newspaper's obituaries desk, the funeral home's own website, a state or regional aggregator, sometimes a fraternal or veterans' publication. Directors handle this between other work, and the failure mode is consistent: the notice is submitted to the main outlet on time, and the second and third outlets are done later or not at all, or a submission goes to a general inbox and is never processed. Nobody discovers this until the family asks why the notice did not appear, which is usually the day before or the morning of the service. This agent handles submission as a tracked deliverable per outlet. It takes the text the family approved and the funeral home signed off, submits it to each outlet in that outlet's required format ahead of that outlet's deadline, and then confirms publication rather than assuming it. It changes nothing about the text — not spelling, not phrasing, not a date the family wrote a particular way. Built on Agentplace: the agent runs on its own page, so a visitor finishes the whole request in the conversation.
It submits to each outlet on time and confirms it actually appeared.
Submits the approved text to every outlet the family selected, each in that outlet's required format.
Works backwards from each outlet's own deadline, because a regional paper and a website do not share one.
Confirms publication rather than assuming it, and chases any submission that has not been acknowledged.
Escalates a submission at risk of missing its deadline to a director while there is still time to act.
Changes nothing the family wrote — no spelling correction, no rephrasing, no reformatting of how they wrote a name or a date.
Records submission and publication status per outlet, so a family's question has an answer.
It is worth stating the consequence plainly because it is easy to file this as administrative. If the notice does not appear, people who would have come to the service do not know it is happening. The family experiences that as an absence at the funeral, and they attribute it — correctly — to the funeral home. There is no remedy after the fact. That puts obituary submission in a small category of tasks where the cost of failure is entirely disproportionate to the effort of doing it reliably, which is the strongest possible case for taking it off a person's memory and putting it on a tracked list. Confirming publication rather than assuming it is the specific discipline that matters. Most failures are not refusals; they are submissions that went to the wrong address, arrived in the wrong format, or sat unprocessed. A submission that was sent and never acknowledged looks identical to one that succeeded, right up until the morning somebody looks for the notice. Checking is what closes that gap. The rule about not editing the text is not a technical limitation. Families choose their words, sometimes with unconventional phrasing or spelling that is deliberate — a nickname, a name spelled the way the person spelled it, a form of words that means something within the family. Correcting any of that would be a small act of vandalism on the one piece of a funeral the family wrote themselves.
From approved text to confirmed publication.
The family approves and the funeral home signs off. The agent takes it exactly as approved and does not alter it.
In that outlet's required format, ahead of that outlet's own deadline, working backwards from each one separately.
Acknowledgements are chased, publication is verified rather than assumed, and anything at risk escalates to a director with time to act.
A second outlet that would have been missed.
Scenario: a funeral home had twice had a notice fail to appear, both times at a secondary outlet, and both times discovered by the family. For a Saturday service the family selects three outlets: the regional newspaper, the funeral home's own website, and a veterans' association bulletin. The obituary is approved Wednesday afternoon. The agent submits to all three that day, each in its own format, against three different deadlines — the newspaper's Thursday noon cutoff for Friday publication, the website immediately, and the bulletin's Wednesday evening cutoff. The website publishes within the hour and is verified. The newspaper acknowledges Thursday morning and the notice is verified in Friday's edition. The bulletin does not acknowledge by Thursday midday, which is the firm's escalation threshold, so it is flagged to the director, who calls and finds the submission address had changed earlier in the year. It is resubmitted and appears. The family's text is unchanged throughout, including a nickname in quotation marks and a spelling of a place name the family uses. Under the previous arrangement the bulletin submission would have been sent and assumed successful, and the veterans who read that bulletin would not have known about the service.
Anyone submitting notices against somebody else's deadline.
A missed notice changes who attends a funeral and there is no remedy afterwards.
Submission and confirmation stop depending on your memory between other work.
Every outlet has a tracked status rather than an assumption.
Secondary outlets are where failures concentrate, because the main one gets the attention.
The words you wrote appear exactly as you wrote them, in every outlet you chose.
This is a small task whose failure is remembered permanently.
It submits, confirms and records per outlet.
Submits to newspaper obituaries desks and association bulletins and captures acknowledgements.
Stores the approved text and the per-outlet format requirements.
Tracks submission and publication status per outlet against each deadline.
Escalates any submission at risk of missing its deadline to the responsible director.
Holds each outlet's deadline against the service date.
Confirms to the director that publication has been verified.
Publishes the notice to the funeral home's own website.
Holds the approved text exactly as the family wrote it.
Where tracked submission prevents an unfixable failure.
What funeral home owners ask before turning this on.
It is an automated assistant that submits the approved obituary to every outlet the family selected, in each outlet's required format and ahead of its own deadline, confirms publication rather than assuming it, and escalates anything at risk while there is still time.
Never. It submits exactly what the family approved and the firm signed off, including unconventional spellings and phrasing, which are usually deliberate.
Yes, and that is the point. Most failures are submissions that were sent and never processed, which look identical to successes until somebody looks for the notice.
It escalates to a director immediately rather than submitting and hoping. A deadline flagged on Wednesday can be solved; one discovered on Friday cannot.
Yes. A newspaper obituaries desk, a website and an association bulletin all want something different, and that difference is where secondary outlets get missed.
No. A family's chosen spelling of a name or a nickname is deliberate more often than not, and correcting it would be an intrusion into the one part of the funeral they wrote.
Submission and publication per outlet with timestamps, so when a family asks whether the notice went in, there is an answer rather than a recollection.
It runs on Agentplace. Agentplace is an AI agent platform where the agent gets its own page, talks to your visitors there, and carries the request through to the end instead of handing it to a form. You can open this template and change any step before you publish it.
Submits the approved obituary to every outlet against its own deadline, confirms it actually published, and changes nothing the family wrote. Open it in Agentplace and change any step before you publish.