所有帖子

使用 Jev 控制 Modem 何时采取行动。

在 Modem，来自客户的工单、电话、Slack 消息、电子邮件和应用内反馈全天不断涌入，我们希望 Modem 的智能体能在这些信息到达时立即处理——提醒你的团队、创建工单，或执行其他智能体工作流。但这意味着每个事件都要启动一次完整的智能体运行，即使根本没有需要处理的内容。

智能触发器改变了这一点。现在，在启动 Modem 智能体之前，我们会先使用来自 TypeSafe的决策模型 Jev，依据纯英文条件对每个事件进行评估。这些条件可由你自定义，评估耗时不到一秒，成本仅为 1/100 美分。智能体只会在匹配的事件上运行。

这意味着 Modem 用户现在可以运行多得多的自定义自动化，覆盖更多工作流—— 同时消耗更少的智能体使用额度 ——以满足整个组织对客户和产品可观测性的需求。而且该功能今天已向所有人开放。

使用 Jev 筛选触发事件

开始使用智能触发器最简单的方式，是通过 Modem 智能体创建或更新你的自动化，无论是在应用内，还是从 Slack 或 Discord 操作。Modem 会自动使用智能触发器，确保自动化只在需要时运行。

#支持

Beatriz上午 10:42

@Modem 每当 Intercom 上的客户说某个功能坏了，你能发到 #eng-triage 吗？

Modem应用上午 10:42

已完成。我创建了 升级功能故障报告. It only runs when the ticket actually reports a broken feature, so routine tickets won’t start the agent.

Whena support ticket has new activityFiltersSource is Intercom · Author is a customerOnly ifthe customer reports that a feature is broken or failingThenSummarize it and post to #eng-triage

But you can also create and update them manually from the Automations page.

The automation form: When 'a support ticket has new activity', with the scope tokens 'Source is Intercom' and 'Author is a customer', and the condition 'the customer reports that a feature is broken or failing' with the status 'Can be answered from the support ticket alone'
The preset picks the event, the tokens scope it by exact field matches, and the condition filters what is left per event.

First choose an event, like "a support ticket has new activity", and optionally scope the event using the + Filter selector. In the example above, support ticket activity is filtered to Intercom activity coming from customers.

Here's where smart triggers comes in. You additionally scope the event to trigger on a natural language prompt using the + Analyze button. In the example above, if Jev detects that a customer is reporting a broken product experience, the Modem agent comes alive and sends a triage update to #eng-triage.

This is just one example demonstrating the power of short triggers. Let's talk about some others.

Unlock new workflows

Tickets, calls, pull requests, issues, feedback and posts on X were too noisy to automate on when every event cost a run. Now an automation can subscribe to the whole stream, scope it to a source, channel or state change, and filter it down to the relevant events with your condition.

Here's some recipes you can try today:

Post a cancel risk to #churn-riskLog a promised date before the thread buries itTell #billing who a payments PR unblocksPage on-call for data loss or a security issueFile the workaround a customer describedOpen a Linear issue for a checkout crash

When

a customer sends a message

and Jev decides

the customer is frustrated or says they might cancel

Then the agent

Posts to #churn-risk with the account and the thread.

When

a teammate sends a message

and Jev decides

the teammate commits to a date, a fix, or a refund

Then the agent

Logs the commitment against the customer so it isn’t lost in a thread.

When

a pull request is merged

Base branch is main

and Jev decides

the pull request touches billing or payments code

Then the agent

Posts to #billing with the customers waiting on the topic the PR resolves.

When

an issue is opened

Source is Linear

and Jev decides

the issue describes a security problem or data loss

Then the agent

Posts to the on-call channel with the issue and whoever filed it.

When

a call has new activity

and Jev decides

a customer describes a workaround they built around a missing feature

Then the agent

Files it on the product topic with the transcript turns as evidence.

When

a feedback submission has new activity

and Jev decides

the report was sent from a checkout page and mentions an error or a crash

Then the agent

Opens a Linear issue with the session replay and trace attached.

Before smart triggers, the agent itself would evaluate these conditions with a slow and expensive frontier-level model - making many workflows cost-prohibitive. But since these conditions are now evaluated with Jev, it's feasible for any organization to run them at any scale.

Create one from your coding agent

Modem today has plugins for Claude, ChatGPT, Cursor, and of course any agent via MCP.

If you've plugged Modem into your agent, you can create smart triggered automations without leaving it.

Claude Code creating the automation from a plain-English ask.

Ask whichever one you already have open:

Whenever a customer in our help desk reports something broken, summarize it and post to #eng-triage using Modem.

Your agent uses Modem's MCP to create the automation, including the scope and the smart trigger condition.

A new age of customer workflows

Smart triggers and Jev are an exciting new change to the Modem platform. Now you can create bespoke custom workflows, triggered from activity detected in any of your customer channels. You can route concerns to the team that cares most, trigger coding agents to take a first pass, and many other agentic workflows. And the agent only does the work if there's work to be done.

Earlier this month we moved to modem.ai, and launched a whole new website positioned around how we find, fix, and follow up on customer concerns. Smart triggered automations, powered by Jev, is just one step of many we're making to make sure your teams have your customers covered.