One record for every customer. Your team and your agents work from it.

Yappily is the customer system of record for teams running several brands with AI agents: one contact per person across every channel and brand. Start with every reply approved. Let agents send the ones you trust.

Kettle & Paw Co.
Maya Okafor
Ticket TK-311 · Replacement lid
Royal KettleOpen
Mon 8 Nov
Order #1042 placed · Hearth kettle 1.7 L14:02
Fri 12 Nov
Maya OkaforWebsite chat10:01
Has #1042 shipped yet?
Support agentWebsite chatSent at once · Order status is on Auto
It has. #1042 left our warehouse this morning and should reach you on Tuesday.
Today
Maya OkaforInstagram DM09:12
Hi! The lid on my Hearth kettle cracked after a week. Can I get a replacement?
Maya OkaforEmail09:20
Photo of the cracked lidHere's the crack, it's from order #1042.
lid-crack.jpg
Support agentdrafted a reply · Instagram DMWaiting for approval
Sorry about the lid, Maya. A replacement lid for your Hearth kettle is on its way at no charge, and you don't need to send the cracked one back. I've added it to order #1042 so you can track it there.
Answered from Royal Kettle knowledge base: Replacement parts
Replacement parts is on Approve

Write a replyInstagram DM

Sample data. Royal Kettle and Northpaw are fictional brands.

Lena is one person, not four threads.

Each person gets one contact across every channel and brand, with one timeline: messages, tickets, lifecycle stage and customer events such as orders and signups.

Every handle points to the same record

Instagram, email, Messenger and a website chat, across two brands, all land on Lena.

@lena.and.pipNorthpaw
lena@ortiz.exampleRoyal Kettle
Lena OrtizNorthpaw
Website chat visitorRoyal Kettle
Lena OrtizCustomer · 2 brands
  • Order #1042 placed
  • TCK-311 · sizing question
  • Signed up · Royal Kettle

One timeline, both brands

Whoever picks up Lena's next message, a person or an agent, reads all of it first.

  1. 12 MarSigned up for the newsletterRoyal Kettle
  2. 4 NovOrder #0988 placed, trail harnessNorthpaw
  3. 9 NovInstagram DM: does the harness come in a medium?Northpaw
  4. 10 NovEmail: can I add a second lid to #1042?Royal Kettle
  5. TodayWebsite chat, ticket TCK-311 openedRoyal Kettle

Each kind of reply waits for a person, until you set it to Auto.

New workspaces start in dry run, so every agent reply is a draft that waits in Needs approval. When you trust the agent with a kind of conversation, such as order status, someone on your team switches that category to Auto and those replies send at once.

  1. An agent writes a draft

    From the API, MCP or the CLI, using the brand's knowledge base.

    Maya · replacement liddrafts.create
    Sam · where is my order?drafts.create
  2. Yappily checks its category

    A person chose Approve or Auto for each kind of conversation.

    Replacement partsApprove
    Order statusAuto
  3. On Approve, your team approves or edits

    In the inbox, on the contact's timeline, with the whole history beside it.

    Waiting in Needs approval
  4. Yappily sends it

    On the channel the customer wrote in, from the right brand.

    Sent after Jo approved10:14 · instagram dm
    Sent at once10:02 · website chat
Reply categoriesRoyal KettleSettings, in the app
  • Order statusWhere is it, has it shipped, tracking linksset to Auto
  • Replacement partsLids, filters and other sparesset to Approve
  • RefundsReturns, refunds and creditsset to Approve
  • Product questionsSizes, materials, careset to Approve

Start with every reply approved. Let agents send the ones you trust. Only someone on your team changes these, here in the app.

Same action, four ways in

An agent creating a draft reply does exactly what a person does in the app. Pick the door: the result is the same draft, on the same conversation.

# an agent drafts a reply from its terminal
yappily drafts create --conversation cnv_8f2 \
  --body "Hi Hana, yes, we can gift wrap it…"

draft drf_31c created on cnv_8f2

Needs approvalGift wrap questions are on Approve at Royal Kettle, so this one waits for a person in the inbox.

Every part of the record, running

These are screens your team and your agents share. Each one is a piece of the product, with the same data an agent reads through the API.

ChannelsRoyal Kettle
  • EmailLive
  • Website chatLive
  • Facebook MessengerLive
  • Facebook comments and reviewsLive
  • Instagram DMs and commentsLive
  • Next
  • WhatsAppComing
  • ViberComing
  • TelegramComing
  • SMSComing
  • Your own
  • Custom channel through MCPPlug in

Channels, live and coming

Email, website chat, Messenger, Facebook comments and reviews, and Instagram are live. WhatsApp, Viber, Telegram and SMS are next. Anything else, you plug in through MCP.

POST https://hooks.northpaw.example/yappilySigned
  1. 10:07:12draft.created20084 ms
  2. 10:05:03message.received20091 ms
  3. 09:40:27customer_event.added20077 ms
  4. 09:40:21customer_event.added503 · retried2.1 s
  5. 09:12:48conversation.created200102 ms

Signed webhooks, with the delivery log

Every change on the record goes to your endpoint, signed, and every attempt is logged. A failed delivery is retried and stays visible until it lands.

Hana OkaforMerged
  • hana.okafor@mail.exampleEmail · Royal Kettle, Northpaw
  • @hana.and.biscuitInstagram · Northpaw
  • Hana OkaforMessenger · Royal Kettle
  • Chat visitorWebsite chat · Royal Kettle

One contact per person

Her email, Instagram, Messenger and chat sessions are one contact, with one timeline, whichever brand she wrote to.

MCP toolsyappily
  • conversations.listread
  • contacts.getread
  • drafts.createwrite
  • tags.addwrite
  • conversations.assignwrite
  • customer_events.addwrite
  • webhooks.registerwrite

Your agents get the same tools

What the app does, agents can do through MCP, the API and the CLI. Approving drafts and setting categories to Auto stay with your team, in the app.

Lifecycle · Hana OkaforNorthpaw
VisitorChatted on the site
LeadLeft an email
SubscriberSigned up
CustomerFirst orderCurrent
RepeatSecond order
Signed up · 12 MarOrder #0988 · 4 NovOrder #1042 · today

Lifecycle stages from real events

Orders and signups land on the timeline as customer events, and the stage moves with them, so an agent knows who it is talking to before it drafts a word.

Knowledge baseRoyal Kettle
  • help.royalkettle.exampleSynced
  • Gift wrappingSynced
  • Shipping and returnsSynced
  • Enamel care guide.pdfIndexing

A knowledge base per brand

Agents answer Royal Kettle questions from Royal Kettle's pages, and say which one.

The channels your customers already use.

Five are live now. Four more are on the way. If yours isn't here, plug it in yourself through MCP.

Live
Email
Live
Website chatIncluding proactive messages
Live
Facebook Messenger
Live
Facebook comments and reviews
Live
Instagram DMs and comments
Coming
WhatsApp
Coming
Viber
Coming
Telegram
Coming
SMS
Yours
Your own channelPlug it in through MCP

Questions

Can an agent send a reply on its own?

Yes, for the kinds of conversation a person on your team has set to Auto. New workspaces start in dry run, so every agent reply is a draft that waits in Needs approval. When you trust the agent with a category such as order status, switch that category to Auto in the app and its replies send at once. Every other category keeps waiting for a person.

Who can approve a draft or switch a category to Auto?

Only a person, in the app. Agents can list conversations, read contacts, create drafts, tag, assign and add customer events through the API, MCP and the CLI. Approving and choosing what runs on Auto are not part of that.

Which channels work today?

Email, website chat, Facebook Messenger, Facebook comments and reviews, and Instagram DMs and comments are live. WhatsApp, Viber, Telegram and SMS are coming.

Can I connect a channel you don't support?

Yes. Plug your own channel in through MCP and its messages land on the same contact timeline.

I run several brands. Is each one separate?

Each brand has its own knowledge base and its own reply categories, but each person is one contact across all of them, with one timeline.

How much does it cost?

There's a free plan, and paid plans start at $40 a month. See the pricing page.

Give your agents one record to work through.

Connect your brands and channels, point your agents at the API, MCP or CLI, and choose which kinds of reply wait for your team.