Chat · Tickets · Help center · Automation · Reports
engageramo is the engagement layer behind every product you ship: a chat widget on your site, a shared inbox for your team, tickets from support@, and the automation connecting them — delivered through the email provider you already use.
The field manual
One 26-kilobyte script tag. A launcher that opens into chat, past conversations, and your help articles — rendered in a shadow DOM so it can never break your styles. Anonymous visitors, identified users, verified identities: all handled.
▸ boot → identify → converse
Live conversations stream in as they happen. Assign with round-robin, snooze until Monday, reply with /macros, leave @mention notes your customers never see. j/k to move, e to close. No page loads, no refresh button.
▸ j · k · e · / · @
Point support@yourdomain at the ingest endpoint and every email becomes a numbered ticket — threaded across replies with plus-addressing, subject markers, and Message-ID chains. Agents reply from the inbox; customers get a clean branded email.
▸ support@ → ticket #482
Rules route billing emails to the billing team, mark urgent things urgent, and answer instantly when you're asleep. SLA policies stamp deadlines on every conversation and set them on fire when they slip.
▸ if channel=email ∧ body∋refund → route(billing)
A public help center per workspace, searchable right from the widget. Draft in markdown, publish in one click, watch the 😃/😕 reactions tell you what's working.
▸ search @@ plainto_tsquery
Median first-reply and resolution times, CSAT distribution, channel mix, agent leaderboards — computed from the same tables the inbox writes, so the chart never argues with reality.
▸ percentile_cont(0.5)
How it's wired
yourapp.com ── widget.js ──┐ ┌── agents · inbox · SLA timers
yoursite.io ── widget.js ──┤ │
yournext.app ─ widget.js ──┼──▶ ENGAGERAMO ──────┼── help center /help/{workspace}
│ (one deployment) │
support@yourapp.com ───────┤ └── REST API · webhooks · reports
support@yoursite.io ───────┘ │
(email → ticket) ▼
your email provider
(SendGrid · Resend · yours — DKIM)One deployment, many workspaces. Each product gets its own widget key, its own inbox, its own help center — and its own sending identity. Plug in SendGrid, Resend, or any transactional email API, per workspace, and keep contacts linked to the lists you already run in SendGrid or Mailchimp.