How Notifications Work in Listdom

Notifications keep a directory workflow moving

A directory has several moments where silence creates uncertainty. A contributor submits a listing and wonders whether it arrived. An administrator needs to know that a listing is waiting. A listing owner needs to hear when its status changes. A visitor sends an enquiry and expects it to reach the right person.

Listdom notifications connect those moments to a message. Rather than treating every email as a separate feature, think of the system as a simple chain:

an event happens → the right person is chosen → Listdom sends the right message.

That model makes it much easier to build a useful setup without filling an inbox with unnecessary alerts.

Start with the workflow, not the template

Before creating templates, decide what should happen after each meaningful event on your site. A curated local-business directory, for example, usually needs an administrator alert for a new submission and a contributor update when that listing is approved or returned for review. A service directory may also need the listing owner to receive contact enquiries promptly.

Start with these three questions:

1. What event should trigger the message?
2. Who needs to receive it?
3. What should that person do next?

If a message does not have a clear recipient or next action, it probably does not need to be a notification yet.

Where to manage Listdom notifications

Open Listdom → Notifications in your WordPress dashboard. This is where Listdom stores notification templates and connects each template to a hook—the event that causes it to send.

The notification list helps you scan the template title, its hook, and whether SMS is enabled. Open an existing template to edit it, or choose Add Notification when you need a new one. The notification title is also used as the email subject, so make it specific enough for a busy inbox: “New listing awaiting review” is more useful than “Listdom notification.”

The message editor supports normal email content and Listdom placeholders. Keep the content direct: explain what happened, identify the listing or request, and give the recipient a sensible next step.

Core notification hooks to understand first

The core hooks are the best place to begin because they cover the everyday directory workflow without relying on a feature-specific add-on.

New Listing

Use this for an administrator alert when someone creates a listing. It is especially helpful when your directory uses review before publication. Link the recipient back to the appropriate review path and keep the copy focused on the information they need to check.

If you are still shaping the submission experience, first configure the Add Listing form so the notification follows a form and ownership flow you actually want.

Listing Status Changed

This is the natural owner-facing follow-up to submission and moderation. A useful message should say that the listing status changed and point the owner toward the next step if one exists.

Status notifications work best when the moderation policy is already clear. For the policy itself—pending review, publication, guest submissions, roles, and packages—see how to moderate and approve listings in Listdom.

Contact Owner

Use this hook when a visitor contacts a listing owner. This is a lead-oriented notification, so the message should make it obvious which listing the visitor was viewing and what information the owner should reply to.

If you need the wider path from the visitor’s form to the owner’s follow-up, see how Listdom contact and Connect workflows handle directory inquiries.

Abuse Report

An abuse-report notification is an internal quality-control message. Send it to the person responsible for reviewing reports, not automatically to every administrator. A small, clearly assigned review queue is more useful than a broad alert that everyone assumes someone else will handle.

Add-on events are for feature-specific workflows

Listdom can add more notification hooks when you enable the relevant add-on. These are not substitutes for the core setup; they extend it for workflows your directory actually uses.

• Booking Add-on: booking and owner-booking updates, including approval, rejection, or cancellation events.
• Claim Add-on: claim requests and claim-status updates.
• Auction Add-on: offer and offer-acceptance events.
• Jobs Add-on: job-application and owner-application updates.

Only create templates for events that exist in your active workflow. For example, a booking notification is useful only after the booking journey, recipients, and approval policy are in place. Turning on every available event before that point usually creates duplicate or confusing messages.

Email first, SMS when it changes the outcome

Email is the practical baseline for most Listdom notification workflows. It gives administrators and listing owners a record they can return to, and it works well for submissions, status updates, and routine communication.

SMS is available through the Listdom SMS Add-on. Use it selectively for moments where speed matters more than a long explanation—for example, an urgent booking response or a time-sensitive owner alert. It should complement a clear email workflow, not replace it.

Before enabling SMS, check that the same event does not already produce an email and an unrelated follow-up message. A recipient should be able to understand why they received each alert without guessing.

A sensible first notification setup

For many new directories, three templates are enough to start:

1. New Listing → administrator so submissions do not wait unnoticed.
2. Listing Status Changed → listing owner so contributors know what happened after review.
3. Contact Owner → listing owner so leads reach the person responsible for the listing.

Then test the complete journey with a normal user account. Submit a listing, change its status, and send a contact request from the frontend. This is the quickest way to catch the difference between a template that looks correct in the editor and one that reaches the wrong person in a real workflow.

The test should follow the same access path your visitors use. If registration, guest submission, packages, or dashboard access changes the flow, review how Listdom login, registration, and access work before expanding your notification set.

Why a notification may not send as expected

When a notification does not behave as expected, work through the system in order:

1. Confirm that the intended event actually happened.
2. Check that the template uses the correct hook.
3. Confirm that the relevant add-on is active when the hook belongs to an add-on workflow.
4. Review the intended recipient and the listing or user data it depends on.
5. Test the same action with a normal user account rather than only as an administrator.
6. Check your site’s normal WordPress email delivery setup if messages are not arriving at all.

The most common issue is not an email template—it is a mismatch between the event you expected and the hook selected in the notification.

Keep the system calm as your directory grows

Good notifications reduce uncertainty. They do not report every small change to every person.

Add new templates when you introduce a real workflow: bookings, claims, applications, or another action that needs a timely response. Revisit the recipient list whenever you change your moderation or ownership model. A notification system should follow the directory you are building, rather than force your team into someone else’s process.

For deeper field-by-field configuration, refer to the Listdom notification documentation.

FAQ

Where do I configure notifications in Listdom?

Go to Listdom → Notifications. You can edit an existing template or add a new one, then choose the hook that determines when it sends.

Which Listdom notification hooks are available without add-ons?

The core setup includes hooks for Contact Owner, New Listing, Listing Status Changed, and Abuse Report. Additional hooks depend on the relevant Listdom add-on.

Is SMS included with Listdom notifications?

SMS is available through the Listdom SMS Add-on. Email is the standard starting point for most notification workflows.

Why is my Listdom notification not sending?

First confirm the event occurred and the template uses its matching hook. Then check any add-on dependency, recipient data, and your normal WordPress email delivery setup.