Notifications
Cross-channel out of the box: in-app feeds, email, Slack, and Teams, with batching, routing, broadcasts, and per-user preferences.
Stop letting deadlines die in unread inboxes.
Free tier. No credit card. First comment in 5 minutes.
Review Agent flagged 3 pricing claims on Q3 deck
“conflicts with the rate table on slide 4”
Maya assigned you the contract sign-off
contract.pdf · due Friday
Sarah resolved the Q3 forecast thread
forecast.xlsx · 12 updates batched
“Can you approve the revised projections before Friday close?”
forecast.xlsx · cell B12 · Q3Open in appMaya mentioned @Ethan on Q3 forecast
“Can you approve the revised projections before Friday close?”
app.acme.com/forecast3 pricing claims flagged on Q3 deck: opens to approve-or-reject queue.
2 replies · last 1m agoethan@acme.com · per-document or org-wide
ALL = every event · MINE = mentions & assignments · NONE = silent
Notification feeds running inside products at
What it is
Cross-channel notifications for the review layer, out of the box: in-app feeds, email, Slack, and Microsoft Teams. By default the inbox is connected to Comments — mentions, replies, and thread activity generate notifications automatically, and only for documents the user has access to. Your backend adds custom events through the REST API, an optional pipeline batches bursts into digests, and each user sets their own preferences per channel.
Margin Review Agent flagged 3 pricing claims on the Q3 deckagent
opens to findings
Maya assigned you the contract sign-off, due Fridayhuman
12 updates on the Acme renewal, batcheddigest
one feed, both actor types, consent where the agent’s work lands
How it works
Enable Notifications in the Velt Console, drop in the tool, and comment activity flows into the inbox automatically. Email, batching, and custom events layer on from there.
npm install @veltdev/react<VeltProvider
apiKey={VELT_API_KEY}>
<YourApp />
</VeltProvider>// enable Notifications in the Velt Console first
<VeltNotificationsTool />
// or embed VeltNotificationsPanelBy default the inbox is connected to Comments: mentions, replies, and thread activity generate notifications automatically, and only for documents the user has access to. Custom events from your backend land in the same inbox through the REST API with full CRUD. Email goes out through your SendGrid account or any email service via webhooks. An optional delay-and-batch pipeline holds notifications, suppresses delivery when the recipient already saw the activity, and groups the rest into digests. Preferences are per-user: set all, mine, or none per channel, per document or org-wide.
// comment activity flows in automatically · scoped to documents the user can access
Teams that build it budget weeks for the inbox and a quarter for the pipeline, then keep paying for the long tail. The 3 steps above replace the inbox; the capability wall below replaces the pipeline.
Skip the steps. Have your agent set it up.
npx -y @velt-js/mcp-installer
claude mcp add velt-installer -- npx -y @velt-js/mcp-installer
npx -y @velt-js/mcp-installer
npx -y @velt-js/mcp-installer
npx -y @velt-js/mcp-installer
Channels and pipes
Launch notifications this week.
No credit card. Works with React, Next.js, Vue, Angular, and HTML.
Capabilities
Each card is the live SDK. Toggle to Code for the exact snippet that renders it.
Maya mentioned you on Q3 forecastmention
“@you can you review before Friday?”
Sarah replied on the Q3 threadreply
forecast.xlsx · cell B12
Ethan requested your sign-offsign-off
contract.pdf · due today
React
Next.js
Angular
Vue
HTML<VeltNotificationsTool />
// panel opens automaticallyPrebuilt tool and panel components with For You, Document, and All tabs. The reviewer opens one feed and finds every mention, reply, and sign-off request waiting.
// SendGrid integration: API key,
// template ID, from address in consoleMentions and replies fire emails through your SendGrid account or any service via webhooks. The reviewer who hasn’t opened your product today still sees the sign-off request.
// delay-and-batch + already-seen
// suppression, configured in consoleA delay-and-batch pipeline holds bursts, drops what the recipient already saw, and delivers one digest. Deadline-day activity arrives as a summary, not forty separate pings.
<VeltNotificationsTool enableSettings />Each user sets all, mine, or none per channel, per document or org-wide, through the settings UI or REST API. The reviewer decides what reaches them.
POST /v2/notifications
{ "type": "deadline", "to": userId }POST your app’s own events into the same inbox: deadline alerts, counterparty updates, workflow steps. One feed carries everything your reviewers need to act on.
velt.webhooks.subscribe({
events: ["comment.*", "review.*"],
});Comment and review events fire to your endpoint with full payloads; route them to Slack or any channel you run. Your pipeline, your rules, Velt supplies the events.
Finished overnight: 3 findings ready as an approve-or-reject queue.
// agent comments + inbox auto-
// connection to CommentsAn agent is a user: its findings notify the assigned reviewer like anyone’s. The agent works overnight; the reviewer finds the approve-or-reject queue at nine.
// notifications fetched only for
// documents the user can accessNotifications generate only for documents the user can access. The counterparty sees their thread move; your team’s internal deliberation never reaches their inbox.
Mayamentioned you: “approve the revised Q3 projections?”
full content// notifications data provider →
// content on your infrastructureThe self-host data provider keeps notification content on your servers; Velt stores minimal identifiers. The deal blocked on data residency clears without a feature trade.
Approval requests used to sit unread until the deadline passed. With the inbox and email out of the box, the approver sees their turn the same day — our campaigns stopped slipping.
Marketing ops lead · content platform
Little big details
Shipped functionality leads; draft items render after engineering sign-off. This is the part of an in-house build that never ends.
Make it yours
Prebuilt Tool and Panel for the fast path, wireframes and primitives for fully custom inbox UIs, and a REST surface for custom events and preferences.
Prebuilt Notifications Tool and Panel for the fast path; wireframes and primitives for both for fully custom inbox UIs; template variables, global styles, dark mode. Your SendGrid email template is yours end to end.
Maya mentioned you on Q3 forecast
“@you review before Friday?”
Sarah requested your sign-off
contract.pdf · due today
<VeltNotificationsPanelWireframe>
// your markup
</VeltNotificationsPanelWireframe>Custom notifications via REST API; notification config API at document or org level; settings APIs with an extendable channel list; batching and delay configuration in the console; webhooks into your own channel pipeline.
POST /v2/notifications/config
{ "channel": "email", "value": "MINE" }We POST our own deadline and counterparty events into the same inbox as comment activity. Reviewers have one place to look instead of five.
Staff engineer · deal management platform
In production
Tabbed by vertical, with verified customer screenshots.
This Digital Sales Room gives you everything you need to move forward — from proposal to plan.
@Fin We need to make a working demo for Rene and his team
Brand and legal get the review request where they work: inbox, email, or their channel. The campaign deadline survives because the approver saw their turn today, not Thursday.For sales enablement
finance / receivables
Can we confirm the PO before approving this one? @Sarah
1 ReplyA sign-off request on the Q3 forecast reaches the controller as one digest, not a ping per cell. The close calendar holds because no approval waits unseen.For fintech and FP&A
Cotton Supplier Ltd.
AgriCotton Farms
Village Kheda, Gujarat, India
SpinCo Yarns
18 Narol Rd, Gujarat, India
DyeWorks International
Calle de Mayo, Mexico
Can you attach the GOTS cert for this lot before we approve? @Sean
1 ReplyThe shipment exception notifies your team in-app and the counterparty by email, each seeing only their side. Deskless reviewers get the request without living in your product.For operations
Privacy Risk Review
Wren discovered a feature request in Jira involving users' health data and triggered a review after analyzing the PRD in Confluence against company policy and US regulation.
JStarted by Juan MendezThis feature processes PHI, so HIPAA applies. I recommend a PIA and a vendor BAA review before any data flows. @Juan
The attestation request reaches the compliance officer where they work: inbox, email, or their channel. The filing deadline holds because the sign-off was seen today, not the morning it was due.For compliance
Superflow
1 · Subscription & Fees
Customer subscribes to the Service on a monthly basis and shall pay the then-current fees in advance of each billing period. Fees are non-refundable except as expressly set out in this Agreement.
2 · Term & Auto-Renewal
The subscription renews automatically for successive one-month terms unless either party gives at least thirty (30) days' written notice of non-renewal before the end of the then-current term.
3 · Limitation of Liability
Except for breaches of confidentiality, each party's total aggregate liability under this Agreement shall not exceed the fees paid by Customer in the one (1) month preceding the event giving rise to the claim.
4 · Governing Law
This Agreement is governed by the laws of the State of Delaware, without regard to its conflict-of-laws provisions, and the parties consent to the exclusive jurisdiction of its courts.
The redline review reaches outside counsel by email and your team in-app, each seeing only their side. The matter moves because no request waits unread in someone’s queue.For legal
Make the hero headline punchier and add a primary CTA.
Done — rewrote the headline, tightened the subtext, and added a primary CTA in hero.tsx.
Add a logo strip with social proof under the CTA.
Added a five-logo trust strip below the CTA and wired it into hero.tsx.
Ship your app in a weekend
Get startedUse our brand orange on the CTA and cut the headline to one line. @Sean
Agent findings land in the reviewer’s feed the moment the run completes, batched into one digest. Generated work moves to a human decision instead of waiting to be discovered.For AI-native SaaS
See it running in products like yours.
30 minutes, with an engineer, not a sales deck.
Related primitives
Comment threads, approval steps, and agent findings all reach the inbox.
The default notification source: every thread event lands in the inbox.
Replied to your thread on the Q3 forecast
every thread eventthe inbox
A pipeline only completes if reviewers see their turn.
reviewers see their turnthe pipeline completes
Findings reach a human through the feed.
Flagged 3 pricing claims on the Q3 deck
agent findingsreach a human via the feed
Notification content can live on your infrastructure via the self-host data provider, with only minimal identifiers on Velt. Notifications generate only for documents a user can access, so internal deliberation never reaches the wrong inbox. See self-hosting and governance.
Book DemoProof
Reviews stopped stalling on unseen requests.
0 slips
Approval requests used to die in unread inboxes. Now the approver gets it in-app and by email the same day, and our campaign deadlines stopped slipping.
1 digest
Close week used to mean a ping per cell. Batching turned it into one digest a day, and the controller actually reads it.
1 day
We had a working inbox the day we dropped in the tool. The pipeline — batching, preferences, email — was already there.
FAQ
Install @veltdev/react, wrap your app in VeltProvider with your API key, enable Notifications in the Velt Console, and add the VeltNotificationsTool component where the bell belongs. The panel opens automatically; comment activity flows in with nothing else to wire.
In-app inbox components out of the box. Email through your SendGrid account or any email service via webhooks. Other channels like Slack via webhooks, with a Slack key in the per-user preference API.
Yes. POST custom notifications from your backend through the REST API and they land in the same inbox as comment activity, with full CRUD to update or remove them later.
Yes. Turn on settings on the tool or panel and each user picks all, mine, or none per channel. The same config is settable via REST API, per document or as the org-wide default, and the settings UI channel list is extendable.
Yes. An opt-in delivery pipeline holds notifications, suppresses delivery when the recipient has already seen the activity, and groups the rest into digests before sending. Configured in the Velt Console.
Yes. An agent is a user with type agent, so its comments and findings generate the same notifications as anyone’s: the assigned reviewer gets the agent’s output in their feed with the approve-or-reject step attached.
Knock is general-purpose notification infrastructure: you send it events and it orchestrates delivery across channels at scale. Velt notifications come pre-wired to the review layer: comments, mentions, and review activity generate notifications automatically, the inbox components are included, and your backend adds custom events via REST API. If you need a standalone notification platform for your whole product, that is infrastructure like Knock; if you need your review loop noticed without building the pipeline, that is Velt.
Yes. The notifications data provider keeps notification content on your infrastructure while Velt stores only minimal identifiers. See the self-hosting page.
Velt is priced on usage, not seats: you pay for documents with review activity in a month, and there is a free tier for development and early production. Notifications is part of the SDK, not a separately priced add-on.
Free tier. No credit card. First comment in 5 minutes.
30 minutes, with an engineer, not a sales deck.
@Jordan Auto-renewal needs 60 days' notice to match our policy, not 30.
@Maya Liability cap is one month of fees — Legal wants 12 months before we sign.
@Maya Governing law should be New York to match the MSA.