Meeton ai documentation
Turn your website into a sales channel. One tag, five AI modules.
Meeton ai is the AI SDR platform from DynaMeet. You paste two lines of HTML once, and from then on the AI talks to visitors, shows them the right offer, explains your materials, books meetings and follows up by email. These docs explain how it all works under the hood, and how to set each module up.
The three stages, five modules
Every module maps to one job of a sales development rep. You can run the first stage alone and add the rest when you are ready. All five share the same tag, the same visitor identity and the same dashboard.
Meeton Chat
The generative AI agent on your site. No scenario design, full visitor context, hands off to a booking.
Meeton Ads
On-site ads placed along the paths visitors actually walk: journeys, placements and creatives.
Meeton Library
Upload a deck or PDF, share a link, let the AI answer questions about it, track every read.
Meeton Calendar
Native meeting booking with routing, screening, CRM logging and notifications.
Meeton Email
AI-written 1:1 follow-ups fired by return visits, opens and document views.
Dashboard & Insights
Visitors, contacts and companies, the Insights reports and the per-module reports: where the five modules report back.
CRM sync & notifications
HubSpot and Salesforce sync, notification rulesets, target accounts, team members, security and plans.
What a visitor sees
How it fits together
There are three moving parts on the visitor's side, and one on yours.
Everything is outbound from the visitor's browser over HTTPS and a secure WebSocket. Nothing is installed on your servers and nothing connects inbound.
- The loader is a single script,
meeton.js, loadedasync defer. It reads yourteamId, checks it is not a bot and that the page's domain is on your allow-list, creates the visitor ID, and watches the page: navigation, your existing forms, scroll and dwell. - The widget frame is an iframe served from
app.dynameet.ai. The chat UI, booking form, library viewer and ad creatives all render inside it, so their CSS and JavaScript can never collide with yours. - The API and live connection carry configuration, chat messages, bookings and form data to DynaMeet, hosted in the AWS Tokyo region. Your dashboard and, if connected, your CRM read from there.
Quick start
- Add your domain
In the dashboard, open Settings → Meeton AI → Setup → Domains and add the hostnames the tag may run on. Wildcards such as
*.example.co.jpare fine for staging and preview environments. - Paste the tag
Copy the snippet from the same Setup page (or from Installation) just before
</body>, or into a Google Tag Manager Custom HTML tag on the All Pages trigger. - Watch it go green
Settings marks each domain Installed the moment the widget first loads on it. There is no manual verification step. Open Settings → Meeton AI → Chat to give the agent its identity and knowledge, and you are live.
Your site needs HTTPS. The loader relies on browser features that only exist on secure pages, so it stays silent on plain HTTP. Every production site qualifies; a local http://localhost page is the one exception the loader allows.
Where things live in the dashboard
The sidebar itself (Visitors, Contacts, Companies, Insights, Insights by Module) is described under Dashboard. Every module is configured under Settings → Apps → Meeton AI. The settings are grouped the way the product thinks about them, and the same groups are used throughout these docs.
| Group | Pages | What you do there |
|---|---|---|
| General | Setup · Notifications | Domains and the install snippet, your funnel's name and type, who gets alerted and where. |
| Agent | Prompt editor | Advanced prompt overrides for the chat agent. |
| Visitor experience | Chat · Theme · Lead form · Calendars · Library · Ads · Email · FAQ · AI translation | Everything a visitor can see or receive, one page per module. |
| Accounts | Target accounts | Lists of companies that alert your team when one of them shows up. |
| Data & tracking | Conversions · CRM sync | Ad-platform conversion events and the HubSpot / Salesforce connection. |
Technical facts at a glance
async defer; renders in its own frame.dynameetVisitorId, holding a random UUID for one year. DetailsFrequently asked questions
Do we have to use all five modules?
No. Most teams start with Chat, add Calendar when they want bookings inside the conversation, and switch on Ads, Library and Email later. Every module is off until you set it up, and they all share the one tag.
How long does setup take?
Pasting the tag and listing your domain takes minutes. Giving the agent a name, a welcome message and your website as knowledge takes an hour; the setup guide in the dashboard walks through it. Everything else is optional and incremental.
Where do we go when something does not work?
Each page in these docs ends with a Troubleshooting table for its topic. For installation problems start at Installation → Troubleshooting; for anything about the loader, JavaScript API → Debugging shows how to read its log.
Is there a Japanese version of these docs?
Yes. The EN | 日本語 switch in the header opens the same page in Japanese, and the site remembers your choice. A Japanese browser lands on the Japanese pages by default.