# Norm: A natural language AI agent builder for phone calls

A phone agent is never finished. A caller asks something nobody planned for, a policy changes, a transfer number moves, and somebody has to change what the agent says. In most setups that somebody is an engineer, so the person who heard the call waits for a ticket to come back.

[Norm](/norm) is Bland's no-code way around that wait: a natural language AI agent builder for phone calls. You describe the change in plain English, and Norm makes it in your agent, tests it, and shows you what it touched before anything reaches a live call.

## What is Norm, Bland's natural language AI agent builder?

As Bland puts it, "Norm is the AI assistant built into Bland. You describe what you want in plain English, and Norm builds, edits, tests, and debugs your agents for you." Agents, tools, analytics, and triage all work from one conversation.

Bland builds AI phone agents that answer inbound calls and place outbound calls. Your team builds and edits them in plain English with Norm or in Bland's visual builder, with no engineers needed on your side. Enterprise customers also get Bland's forward-deployed engineers.

Salesforce, HubSpot, Cal.com, Calendly, Notion, and Slack connect from Bland's dashboard. Anything else connects through Bland's REST API and webhooks, which Bland's forward-deployed engineers can help with on Enterprise.

Norm is one of two no-code routes on Bland, and both are set out in [no-code AI phone agents](/no-code). The other is Bland's visual builder, the agent builder in Bland's dashboard, which draws a graph of how your agent fits together and is where you test it.

Norm edits the same prompts, pathways, tools, and settings that you edit by hand in Bland's builder, so a team can start with Norm and keep editing without it.

## What does Norm build from one instruction?

Norm builds an agent from one instruction, and Bland's own example is "Build me a full scheduling agent and integrate with my Cal.com." From that sentence Norm generates the prompt, persona, agent, pathways, validation conditions, extraction rules, and API integrations.

Two of those terms are worth a plain definition. A pathway is a flow you lay out yourself, with steps you place and connections you draw between them, for the parts of a call that have to happen in a set order, and a node is one of those steps.

Extraction rules decide which facts the agent pulls out of the conversation and reuses later in the same call, such as a caller's name, a date they asked for, or a member number.

Most agents start as a single prompt, and structure like a pathway is added only where a conversation needs it. Three common requests show the range:

- "Build me a scheduling agent that books appointments on Cal.com."
- "Add a node after intake that verifies the caller's policy number against our CRM."
- "Change the transfer fallback on this agent to go to billing instead of sales."

The first creates an agent, the second adds a step to a flow that already exists, and the third changes one transfer destination. That matters to a team without developers, because Norm "follows surgical-edit rules: it changes what you asked for and nothing else." You can also ask Norm to explain before it edits, with a prompt such as "Walk me through what you'd change before doing it."

To make a request like these, select **New chat** on your Overview in Bland's dashboard, or ask in the Overview composer, and type it in plain English.

Norm makes each change in development, where you can review it before it goes live. You can review diffs between the original and updated prompts, and simulate agent-on-agent calls to stress-test an agent before deploying it, so a simulated caller finds the edge cases before your customers do.

Norm "only ships changes when you're ready", so one instruction builds an agent and a separate step puts it on live calls. Bland's walkthrough for [building your first AI phone agent](/no-code/how-to/build-your-first-ai-phone-agent) shows how a new agent starts from a blank agent in Bland's dashboard.

<!-- screen: Norm chat in Bland's dashboard building an agent from one plain-English instruction, captured and dated for this page -->

## Can non-technical users build an AI voice agent in Norm without coding?

Yes, on Bland non-technical users can build an AI voice agent without coding, because Norm works from a plain-English description and needs no engineering resources on your side.

The reason is where Norm's knowledge comes from. Before Norm, customers often relied on Bland's forward-deployed engineers (FDEs), the Bland engineers who safely implement changes or launch new agents for a customer.

Bland says Norm "works the way an experienced Bland engineer would: it inspects the live state of your account before making changes, works in development so production keeps running, tests against real call data, and only ships changes when you're ready." Norm codifies what those engineers know and gives every customer the equivalent of its own FDE.

Norm also works from what your team already has. You can upload files or attach your existing knowledge bases for Norm to reference when it builds or modifies your pathways.

A team can also teach Norm its own habits. Skills are reusable workflows that scope Norm to a specific task, and a custom skill is one your team writes, scoped to your organization. Typing `/` in Norm chat opens the skill menu. Custom skills let you encode anything your team does repeatedly, such as brand-voice enforcement, common agent scaffolds, or your standard QA scenarios for every new agent.

Bland released custom skills on 7 May 2026, with an editor that has five fields: command, name, description, when to use, and the content Norm should follow.

One place a developer may still come in is a system that does not connect from Bland's dashboard, which connects through Bland's REST API and webhooks, which Bland's forward-deployed engineers can help with on Enterprise. Building and editing agents is the part that needs no code, and [Bland's no-code AI call center guide](/no-code-ai-call-center) covers how the rest of a rollout fits around it.

## Where does Norm run?

Norm runs in Bland's dashboard, over iMessage, and inside a coding agent, so your team can reach Norm wherever the team already works.

In Bland's dashboard, Norm chat opens full page on your Overview and in a side panel everywhere else. Your own Norm conversations sit in a table on your Overview under your address book, newest first, with a **Last active** column.

The table shows 10 rows, and **Show all** lists older conversations. A row's menu lets you **Copy conversation ID** or **Rename** the conversation, and a conversation you leave open on the Overview carries on in the side panel when you move to another page. Read the full walkthrough in [Bland's Norm docs](https://docs.bland.ai/tutorials/norm).

<!-- screen: the Norm conversations table on Bland's Overview, captured and dated for this page -->

Norm is also available over iMessage, so you can text Norm to build, test, and monitor agents from your phone.

Underneath the no-code surface, the same agents are reachable with code. Developers use Bland's API, Bland's hosted MCP server, and the Norm plugin for Claude Code and Claude Desktop, which supplies skills and `/norm:*` commands to build, migrate, validate, and test agents from a coding agent. The plugin needs a Bland API key, and its build command asks before it saves an agent version.

## Can Norm answer questions about your calls?

Yes, Norm answers questions about your call data in plain English, and it picks the aggregation, time range, and visualization that fit the question. Examples include "how many calls failed yesterday?" and "transfer rate by agent this week", and the answer comes back as a table, a chart, or a single number.

Norm has direct access to your call logs and transcripts, so it can also work backward from a problem. When you point Norm at one, it gathers the evidence before suggesting a fix, and Bland's example is "Why did call `abc-123` fail to transfer?" Anchor on a real call where you can: paste the call ID, and Norm pulls the full call and reproduces the failure.

Norm can also fix a call your team flags. Flag a call as a Triage issue and hit **Norm Fix**, and Norm pulls in the failing call and its agent, reproduces the failure, applies a fix, and verifies it against the original call. Every change Norm makes is reviewable on the issue, so you can see exactly what it touched before the fix reaches production.

Bland's walkthrough for [fixing a bad call with Norm](/no-code/how-to/fix-a-bad-call-with-norm) follows these steps one at a time.

Idaho Housing and Finance Association saves $750,000 a year by replacing its IVR with Bland, which handles 4,000 inbound calls a day and cut average call time by 20%.

> "We save thousands of dollars a day."

Greg Blake, Chief Information Officer, Idaho Housing and Finance Association

## Frequently asked questions

### Does Bland have a no-code option?

Yes. Norm, Bland's AI assistant, builds voice agents using natural language descriptions, and Bland's dashboard includes a visual builder for non-technical users.

### Does Norm change live calls?

Not directly. Norm never edits what live calls run: it works in an agent's development environment and saves a version once it passes validation and any tests you run. Saving a version does not change live traffic. To reach live calls, the version is published to staging and then promoted to production, and an agent's first publish goes straight to production. Bland's [guide to how Norm works](/norm/how-it-works) covers each stage.

### Can I see what Norm changed before it goes live?

Yes. Norm shows diffs between the original and updated prompts before you deploy. When Norm fixes a call from a Triage issue, every change it makes is reviewable on that issue before the fix reaches production.

### Does Norm cost extra?

No. Norm is available within the Bland platform at standard pricing, as Bland announced on 26 March 2026. Bland charges $0.14 a minute on the self-serve Start plan. Enterprise pricing is custom, set with Bland's sales team. Phone is billed separately, on a customer's own carrier or Bland's at pass-through cost. Bland's [pricing page](/pricing) lists the plans.

### Can developers use Norm too?

Yes. Developers can reach the same Bland agents through Bland's API, Bland's hosted MCP server, and the Norm plugin for Claude Code and Claude Desktop, which builds, migrates, validates, and tests agents from a coding agent.

### Is Bland only for outbound calls?

No. Bland builds AI phone agents that answer inbound calls and place outbound calls.
