# One agent for your business. In every conversation.

Your customers already have iMessage and WhatsApp open. Put an agent there that knows your business, uses your product, and gets things done.

[BOOK A DEMO](/book-demo) · [BUILD YOUR OWN →](/products)

NORTHLINE BIKES · IMESSAGE

**CUSTOMER**

The helmet I ordered arrived cracked. Can I get a refund?

**AGENT**

Sorry about that. I found your order and the photo you sent. I've asked the team to approve an $89 refund.

REFUND $89.00 · HELD FOR APPROVAL

APPROVED BY SAM · 4 MINUTES LATER

**AGENT**

Approved. $89 is on its way back to your card. Want me to arrange a replacement too?

ILLUSTRATIVE EXAMPLE

## Same memory. Same rules.  
Wherever the customer writes.

![](/integrations/imessage.svg)iMessage · ![](/integrations/whatsapp.svg)WhatsApp · ![](/integrations/slack.svg)Slack · ![](/integrations/email.svg)Email

## Teach it. Connect it. Bound it.

### Teach it what you know

Give it your documents and connect your knowledge base. It answers from what you gave it, in your voice.

### Connect what it can do

Connect your product's API or MCP server. Give it the tools to book, sell, refund, and get work done.

### Decide where it stops

Choose what it may do alone, what waits for a person, and how much it can spend. Then connect your channels.

## Your team stays in the conversation.

Approve a refund, take over a thread, or replay what the agent saw and decided. Sensitive actions wait for the right person.

-   Set approval rules for refunds, payments, and cancellations
-   Hand conversations to a person when judgment is needed
-   Resume when the customer replies, even days later

CONVERSATION ACTIVITY · EXAMPLE

WHATSAPP · REFUND REQUEST  
Held for approval by your team.

IMESSAGE · WARRANTY CLAIM  
Handed to Sam at the customer's request.

SLACK · QUOTE SENT  
Waiting for the customer to reply.

ILLUSTRATIVE EXAMPLE

## Your knowledge.  
Your tools. Your rules.

### Documents.

Start with the information your business already has. The agent uses it to answer in context.

### Your API or MCP server.

Connect your product so the agent can act on a customer's request.

### The SDK.

Prefer to build your own? Use the same platform underneath our agents.

[START BUILDING →](/docs/quickstart)

## Same platform.  
Same guarantees.

Every agent runs on Constal, with the same durability, isolation, and controls available to teams building on the platform.

### Picks up where it left off.

Sessions survive crashes and redeploys. Work can pause for days and resume with its context intact.

### A person before anything sensitive.

Gate actions behind an approval. Your policy is enforced on every call, every time.

### Everyone's work kept separate.

Each customer or person has their own identity and session history. Credentials stay outside the sandbox.

### Replay any run.

Every step is checkpointed and every call traced. See what the agent saw, decided, and did.

### Spend inside hard limits.

Set a budget and approval rules. Agents transact within those limits, with every transaction on the ledger.

### No compute charge while waiting.

An agent can wait on a customer, a webhook, or a person without keeping compute running.

[BUILD ON IT YOURSELF · READ THE DOCS →](/docs)

## Priced per conversation.

A unit that matches the work: a customer conversation, including the actions and follow-through it needs.

### Let's scope your setup.

Talk to us about your team, tools, and expected usage. We'll put together a plan for your workflow.

[DISCUSS PRICING →](/book-demo)

## Meet your customers where they already are.

[BOOK A DEMO](/book-demo) · [SEE ALL AGENTS →](/agents)