Platform
Notifications
A notification ruleset decides which events alert your team and where the alerts go: Slack channels, email addresses or a Google Chat space. Rulesets are shared by every module, so one "sales team" ruleset can cover chat, bookings, downloads and email drafts, and a feature that needs to alert someone, such as a visitor asking for a human, points at a ruleset.
Where it lives
Settings → Apps → Meeton ai → General → Notifications. The list shows each ruleset with how many events are on, where it delivers, and its language. New ruleset opens a three-step editor: Details, Events, Destinations. Once created, every change saves automatically.
A ruleset, step by step
- Details
Name, which is how the ruleset shows up in the list and wherever a feature asks which ruleset to notify, for example Sales team alerts. Notification language, Japanese or English: Slack messages, emails and webhook posts from this ruleset are written in it. New rulesets default to your account language.
- Events
Per-event switches in five groups, below. Turn on only what this team needs: every event that is on goes to all of the ruleset's destinations. A new ruleset starts with New lead, Visitor asks for a human, Meeting booked, cancelled and rescheduled, Library form submitted and Email draft needs approval on.
- Destinations
Slack channels, email recipients and webhooks, below. A ruleset with events on but no destination warns you: those alerts reach nobody.
Events
| Group | Event | Fires when |
|---|---|---|
| Visitors & leads | First visit | A visitor lands on your site for the first time. |
| New lead | A visitor submits their contact details and becomes a lead. | |
| Target account visits | Someone from a company on one of your target lists arrives on your site. | |
| Target account shows high intent | A target-list visitor reaches a high engagement score. | |
| Lead returns | A known lead starts a new session on your site. | |
| Lead opens a key page | A known lead opens one of the pages you list on this event. See Key pages below. | |
| Chat | Visitor sends a chat message | Someone writes to the AI agent in the chat widget. |
| Visitor asks for a human | The AI agent hands a conversation over to your team. Needs Visitors can ask for a human on under Chat → Advanced, which points at the rulesets to notify. | |
| Visitor rates a chat | A visitor leaves a satisfaction rating after a conversation (customer-support agents). | |
| Visitor asks a question on an ad | Someone uses Ask AI on an ad's inquiry panel. | |
| Meetings | Meeting booked | A visitor books a meeting through the calendar. |
| Meeting cancelled | A visitor cancels their meeting. | |
| Meeting rescheduled | A visitor moves their meeting to a new time. | |
| Visitor asks a question while booking | Someone uses the AI chat beside the booking form. | |
| Library | Lead opens the Library | A known lead opens your document library. |
| Document downloaded | Any visitor downloads a document from the Library. | |
| Library form submitted | A visitor fills in the form that unlocks a document. | |
| Visitor asks a question in the Library | Someone uses the AI chat in the Library. | |
| Email draft needs approval | The AI has drafted an email that is waiting for your review. | |
| Email ready to send | An approved email is ready for you to copy and send (manual delivery mode). | |
| Daily email summary | A digest of the day's email drafts and sends, sent after each sending run that generated, sent or failed something. |
"Known lead" events fire only for an identified contact who is not disqualified. There are no further filters on a ruleset: no business-hours window, no country or language condition, and no digest except the daily email summary. Each event sends on its own, as it happens; a key page fires on every matching page view, since a repeat visit is a stronger signal rather than a duplicate.
Key pages
Under Lead opens a key page, list the paths that count as high intent, such as /pricing/ or /compare/*:
- Paths only, no domain, starting with
/.*matches anything, so/compare/*covers every compare page. - Letter case and a trailing slash are ignored; so are URL parameters, unless the pattern has a
?:/signup?plan=*matches on them too. - Up to 50 patterns per ruleset. The event alerts nobody until at least one page is listed.
Destinations
| Destination | How it is set up | What arrives |
|---|---|---|
| Slack | Connect Slack once under Settings → Integrations (an admin or editor installs the DynaMeet app into the workspace). Then pick one or more channels: public channels are listed and DynaMeet joins them itself; a private channel shows only if you are a member, and DynaMeet must be invited to it with /invite @DynaMeet. Test connection posts to every selected channel and reports which failed. | New-lead and chat-message alerts post as rich cards with View contact and Open conversation buttons; other events post as text. Visitor-typed @here and @channel mentions are neutralised. |
| Type any addresses, one per Enter. Each recipient gets every alert this ruleset sends. | HTML emails with subjects such as [DynaMeet] New lead or [DynaMeet] Contact opened /pricing, listing name, title, company, email, phone, custom form fields and a link to the contact. | |
| Webhook (Google Chat) | Add webhook, provider Google Chat, and paste the space's incoming-webhook URL (https://chat.googleapis.com/v1/spaces/…). | The same cards and text as Slack, posted to the space. |
Microsoft Teams is not a notification destination. Connecting Microsoft 365 under Integrations provides Outlook calendars and Teams video links for Meeton Calendar; alerts for a Teams-based team go by email or through a Google Chat webhook. SMS, browser push and in-app alerts are not offered.
What a notification contains
| Event | Body |
|---|---|
| New lead · Lead returns · Key page | Name, title, company, department, email, phone, every custom form field, a Target list line when the company is on one, and a link to the contact. |
| Target account visits | Company, the person's name, title, department and email when known, which target list matched, the visitor ID and a link to the visitor. The high-intent variant adds the intent score. |
| Chat message · asks for a human | The message and a link to open the conversation, so you can take over the chat. |
| Meeting booked · cancelled · rescheduled | Who, which calendar, when, and the host. |
| Email draft · ready to send | The draft with its recipient and a link to approve or copy it. In manual delivery mode this is how drafts reach you; see Sender & delivery. |
Where rulesets are referenced
- Chat → Advanced → Visitors can ask for a human lists the rulesets with Visitor asks for a human on, and warns when none has it.
- Email → Delivery, in manual mode, lists the rulesets that deliver drafts and warns when none has Email ready to send or Email draft needs approval on.
- Target accounts drive the two target-account events; the lists live on their own page.
Troubleshooting
| Symptom | Likely cause | What to do |
|---|---|---|
| Nothing arrives at all | The ruleset has no destination, or the event is off | The list shows No destinations — alerts go nowhere; open the ruleset and add one. Check the event's switch. |
| Slack: Channel not found | The channel was archived, or it is private and DynaMeet is not in it | In Slack, open the channel and run /invite @DynaMeet, then Refresh list and test again. |
| Slack: Invalid authentication, or channels will not list | The Slack connection expired | Reconnect Slack under Integrations. Only one Slack workspace per team; disconnect first to switch. |
| A private channel shows as Private channel with no name | You are not a member of it in Slack, so its name is hidden | Alerts still post there. Join the channel to see its name. |
| Escalations never notify | No ruleset has Visitor asks for a human on, or Visitors can ask for a human is off | Chat → Advanced shows the warning and links to the rulesets. |
| Email drafts reach nobody in manual mode | No ruleset with a destination has the email events on | Turn on Email ready to send or Email draft needs approval in a ruleset that has a destination. |
| Alerts are in the wrong language | The ruleset's notification language | Change it under Details. A ruleset with no language set sends in Japanese. |
| Too many key-page alerts | A broad pattern such as /*, which fires on every page view by a known lead | Narrow the patterns to the pages that mean intent. |
| Google Chat webhook rejected | Not a full https:// URL, or the space's webhook was deleted | Create a new incoming webhook in the space and paste the full URL. |
Frequently asked questions
Can different people get different events?
Yes: make one ruleset per audience. Sales with leads and meetings to the sales channel, Support with chat messages and escalations to the support channel, Marketing with downloads and key pages by email.
Can we limit alerts to business hours?
Not on the ruleset. The only business-hours setting is on the chat agent, under Visitors can ask for a human → Only during business hours, which changes what the agent tells the visitor outside those hours rather than when alerts are sent.
Is there a digest instead of one message per event?
Only for email: Daily email summary. Every other event sends as it happens.
Do notifications go through our own mail server?
No. Notification emails are sent by DynaMeet. Only Meeton Email's follow-ups to contacts go through your SMTP account.
Are rulesets per funnel or per team?
Per team: the same rulesets are available to every Meeton AI funnel in the workspace.