Small companies
get an operations team

Inquiries land in one inbox, and you reply by editing an AI draft. We're building contracts and company documents next, so you can hand those off too.

Inquiries arrive by email, KakaoTalk, and forms.
You answer them in one inbox.

Run several services and still have one inbox. See who owns each inquiry and how far the reply has gone, on one screen.

No customer list to build by hand.
Every inquiry becomes a customer card.

Senders are recognized by email and saved with the service and channel they came from.

  • 22Domains we run send inquiry email hereRouted to this one inbox (as of Oct 12, 2026)
  • 4Ways to receive inquiriesEmail · KakaoTalk chatbot · Web form · Intake API
  • 1InboxEven across several services
  • MCPAI agent connectionOnly with the same access a person has

How it connects

How one inquiry becomes a customer and a deal

  1. 1

    Inquiry received

    Inquiries from email, KakaoTalk, and web forms land in the inbox as one conversation

    Support inbox

  2. 2

    Customer card

    The sender is added as a customer, with the service and channel attached

    Customers (CRM)

  3. 3

    Reply and notify

    Edit an AI draft to reply, while the team follows along through notifications and webhooks

    Support inbox · Platform

  4. 4

    Quote and contract

    When a conversation turns into a deal, it will carry over into a draft quote and contract (coming soon)

    Contracts and dealsIn the works

Use Cases

Where Scaler fits

🧭

Teams running several services

Each service has its own inquiry inbox, so you open several of them every day

Connect each service's intake to one inbox, then filter by service

💬

Teams taking inquiries on KakaoTalk

KakaoTalk inquiries only reach one person's phone

See KakaoTalk chatbot inquiries together in the inbox, and keep talking through a one-to-one web chat link

🤖

Teams running on AI agents

You want an AI agent to sort inquiries, but you worry about what it can access

Connect it with an MCP token. It acts with the token owner's role, only inside that person's teams

🏢

Early companies where the CEO does the admin

The CEO handles company documents and grant paperwork personally

We're building a company document box and a grant paperwork service. Until then, we can help through a consultation

Security

Your team owns customer data, and decides where it goes

Webhooks only send to addresses your team registers. AI drafts are made by calling an external AI model when someone clicks Create AI draft.

🏷️

Split by team

Conversations and customers belong to a team. Team screens and MCP requests go through the same access check

🔑

Roles set access

READ · EDIT · FULL. Only FULL members and owners can invite, and only owners can transfer ownership

🧾

Keys stored as hashes

MCP tokens and intake keys are never stored in plain text. You see them once, when they're issued

🤖

AI follows the same rules

AI agents (MCP) go through the same access check as people

Pricing

Pricing

Start free, upgrade to Pro when you need it.

Inbox · Customers · Platform

FreeSign up without a card
  • Intake by email · KakaoTalk chatbot · Web form · Intake API
  • Customer list and conversation history
  • Teams · Roles · Notifications · MCP connection
Start for free

Pro

₩29,000 / monthVAT included, renews monthly
  • Everything in Free
  • Priority support (reply within one business day)
  • Cancel anytime, full refund of any payment within 30 days
Start for free

Contract documents · Grant paperwork service

Quote after we talkWe price it once we hear the scope
  • Quotes · Contracts · Receipts written for you
  • Grant and review paperwork drafts (in the works)
  • Always checked before anything is submitted
Talk to us

Start your operations team with inquiries

Sign up and your team account is ready. Connect a channel and inquiries start coming in.