Launch messaging flows with
Use Claude, ChatGPT, Cursor, or Slack to build and manage your customer messaging. You review every message before it ships.
Prompt
Build an onboarding journey for new signups using Knock. Based on what we're building, create a welcome email on day 0, show an in-app guide on first login, and send a tips email on day 3 if they have not created a project. First make sure to install the Knock connector.
All starter prompts, for people and agents
Connect your agent to the Knock MCP server at https://mcp.knock.app/mcp, or install the Knock CLI with npm install -g @knocklabs/cli. Then use any prompt below.
- Knock: Build in Knock
- Claude: First make sure to install the Knock connector.
- ChatGPT: First make sure to install the Knock plugin.
- Cursor: First make sure to install the Knock plugin.
- Grok: First make sure to install the Knock plugin.
- Slack: First make sure to connect Knock in Slack.
- MCP: First make sure to connect the Knock MCP server.
- CLI: First make sure to install the Knock CLI.
Onboarding (Lifecycle)
Build an onboarding journey for new signups using [Knock](https://knock.app). Based on what we're building, create a welcome email on day 0, show an in-app guide on first login, and send a tips email on day 3 if they have not created a project.
Trial ending (Lifecycle)
When a trial has 3 days left. Based on what we're building, create an email and show an in-app banner with an upgrade button using [Knock](https://knock.app). Stop as soon as the account upgrades.
Win-back (Lifecycle)
Find users with no activity in the last 30 days. Based on what we're building, create a win-back sequence using [Knock](https://knock.app) across email and push. Stop the sequence as soon as a user comes back.
NPS survey (Lifecycle)
Based on what we're building, create an NPS survey using [Knock](https://knock.app) that shows in-app 30 days after signup. If a user does not answer within 3 days, send it by email.
Mentions (Transactional)
When someone is mentioned in a comment. Based on what we're building, create an in-app feed message using [Knock](https://knock.app) right away. If it is still unread after an hour, send one email per thread.
Feature launch (Promotional)
Based on what we're building, create a broadcast using [Knock](https://knock.app) that announces our new reporting feature to all workspace admins, with a matching in-app banner for one week. Use our default email layout.
Weekly digest (Product)
Based on what we're building, create a weekly digest workflow using [Knock](https://knock.app) that uses an agent step to summarize each user's activity from the past week, then sends it by email every Monday.
Usage limit (Product)
When an account reaches 80% of its plan limit. Based on what we're building, create an email and an in-app notification using [Knock](https://knock.app) for its admins, and again at 100%.
Failed payment (Transactional)
When a payment fails. Based on what we're building, create an email using [Knock](https://knock.app) for the billing contact right away and show an in-app alert to account admins until the payment succeeds.
Re-engagement (Lifecycle)
If a user has not logged in for 14 days. Based on what we're building, create an email using [Knock](https://knock.app), then a push on day 21.
Churn risk (Lifecycle)
When an account's weekly active users drop 50%. Based on what we're building, create a workflow using [Knock](https://knock.app) that sends an internal Slack alert to the CSM and a check-in email to the account owner.
Sync warehouse data (Setup)
Connect my Snowflake warehouse as a source using [Knock](https://knock.app). Based on what we're building, create a model querying the `users` table, then map the `email`, `name`, and `plan` columns to the matching user fields. Set the sync to run every hour.
Migration (Setup)
Read the templates and journeys in our current messaging tool. Based on what we're building, create workflows, templates, and layouts using [Knock](https://knock.app). List anything you could not migrate.
Unlock customer engagement that runs itself
Knock agents build cross-channel messaging, run inside your workflows, analyze and monitor performance, and suggest improvements to meet your goals.
Ship customer journeys, campaigns, and in-app guides from one prompt.
workflows / broadcasts / in-app guides
Your agent does the work.You decide what ships.
Your agent builds and tests changes on a branch. Nothing reaches customers until you review and publish it.
Review before you publish
Review workflow, template, and guide edits on a branch before you publish them.
Control what agents can access
Choose the tools, environments, and data each agent can leverage.
See and undo every change
Keep a history of every agent edit and roll back any change with a click.
Connect your favorite agent
No matter where you prompt, Knock offers native plugins to popular AI tools. Ask your agent to set up Knock or connect it via the MCP and CLI.
Knock
Anthropic
OpenAI
SpaceXSI
Extensions
How to connect Knock and Claude
Claude connects to Knock through the Knock connector.
Add the Knock connector from Claude's directory.
claude.ai/directory/connectors/knockAdd to ClaudeClick Connect, then sign in to Knock.
Ask Claude to build your first workflow.
Built-in customer engagement skills
Teach your agent how to build best-in-class transactional, product, and lifecycle messaging experiences in Knock.
npx skills add knocklabs/skills- knock-setupConnect Knock and build your first workflows.
- knock-cliEdit workflows, templates, and guides as code.
- knock-notification-best-practicesWrite and review notification copy for every channel.
- knock-in-app-uiAdd Knock guides to a React app, then debug them.
- knock-product-messaging-strategyPlan messaging that drives activation and retention.
- knock-lifecycle-opportunitiesFind onboarding, trial, and win-back moments in your code.
- knock-migrate-to-knockPlan your move to Knock from Braze or Courier.
- knock-email-template-migrationTurn your email templates into Knock layouts and partials.
Frequently asked questions
Agentic customer engagement is customer messaging that AI agents can build, run, and improve, with a person reviewing every change before it reaches customers. In Knock, growth, lifecycle, and ops teams use agents to build lifecycle workflows, email and in-app templates, and guides, then a person on the team publishes each change. Developers can do the same from their codebase with the Knock CLI.
Agents build the workflows, email and in-app templates, and guides behind your customer messaging. That includes onboarding sequences, trial-ending reminders, win-back campaigns, NPS surveys, feature launches, digests, usage-limit alerts, and failed payment notices. Once a workflow is live, the Knock agent can answer questions about its performance, like where users drop off, and suggest improvements.
Knock works with Claude, Claude Code, ChatGPT, Codex, Cursor, Grok, and any AI tool that supports MCP through the Knock MCP server. You can also use the built-in Knock agent in the Knock dashboard or in Slack, with no other AI tool needed.
Add Knock from your AI tool's directory and sign in with your Knock account. There's no local setup or service token. Claude uses the Knock connector, and ChatGPT, Codex, and Cursor use the Knock plugin. All of them run on Knock's remote MCP server at mcp.knock.app/mcp, which any MCP client can connect to. Add Knock's skills to teach your agent how to build messaging in Knock.
Use the Knock CLI when a coding agent like Claude Code or Cursor works in your codebase and needs to pull, validate, and commit workflows as files. Use the MCP server when your agent works in a chat app like Claude or ChatGPT. The CLI supports every Knock resource operation, while the MCP server covers a curated set for managing resources and data. Add Knock's skills to either.
No. Lifecycle, growth, and ops teams can prompt the Knock agent in plain language in the dashboard or Slack, or connect Claude or ChatGPT through the MCP server. Developers who'd rather work in their codebase can use coding agents like Claude Code and Cursor with the Knock CLI.
When you connect through the MCP server, you choose which capabilities to turn on, such as reading or managing resources. The Knock agent follows your roles and permissions, so it can't change anything you can't. Coding agents with the CLI can commit and promote, so limit CLI access to the people and environments that need it.
Yes. Ask your agent to rebuild your workflows and templates from Braze, Customer.io, Courier, or another platform in Knock. Have it work on a branch so your team can review everything before you switch.
Knock has a free plan with no credit card required, and the Knock agent is available on every plan. The Free plan includes 10,000 messages and 500 agent credits a month. Starter is $250 a month with 50,000 messages and 2,000 agent credits, then $0.005 per extra message and $0.01 per extra credit. Enterprise pricing is custom. See Knock pricing for details.