Coming soon

// 02 — Menus are a workaround.

Your systems, one conversation away.

Chat lets any business open a conversation with everything it provides — the website, the booking system, billing, the internal tools. Your users stop clicking around and simply ask. The agent answers from your content and acts across your systems.

Back to the essay →
chat — acting across systems
User: "Move my Tuesday appointment to Thursday
  and update my card to end in 4417."
→ booking system: Tuesday 2pm → Thursday 2pm
→ billing: card on file updated
✓ Both done. Confirmation sent to your phone.
// Two requests, two systems, zero clicking.
❯ ▍

Conversation that does things

Not a FAQ bot. An agent with hands.

Chat answers questions, then keeps going: it books the appointment, reschedules the delivery, updates the record, files the request. Your users get things done in one thread instead of hunting through menus, forms, and settings pages.

  • Ask, and the agent acts — across as many systems as needed
  • One conversation instead of five screens
  • Confirmations and receipts, without leaving the chat
  • Anything sensitive stops and asks a human first
// One thread, three systems
User: "Am I paid up, and when's my next visit?"
→ billing: paid to 30 Sep
→ calendar: Thu 2pm, Room 3
Agent: "You're paid up, and you're in
on Thursday at 2pm. Want the address again?"

Deep integrations

It works your stack like trained staff.

Connect the systems you already run — calendars, billing, CRM, internal admin tools. The agent uses them the way your team does, with the permissions you set. The deeper the integration, the less your users ever need to see the system at all.

  • Calendars and scheduling — booking, moving, cancelling
  • Billing and accounts — status, updates, receipts
  • Internal tools — your team chats with admin and ops too
  • Permissions per system, per action; nothing it's not allowed to touch
// The agent's toolkit
calendar    read · write
billing     read · write
crm         read
admin tools  scoped to team
// You decide what it may reach.

Every surface

Public for customers. Private for teams.

The same conversation meets people wherever they are: a widget on your site, branded chat pages, WhatsApp or Telegram. And your team gets the same access to the business — analytics, admin tasks, and operations through chat instead of dashboards.

  • Web widget — one script tag, your branding
  • Branded site chat pages
  • WhatsApp and Telegram for customers
  • Private surfaces: your team chats with internal systems
// Public
site widget · chat pages · whatsapp · telegram
// Private — your team
"How many bookings did we lose this week?"
→ pulls the numbers, no dashboard needed
// One agent, one persona, everywhere.

Voice

And when they'd rather call.

Connect a number and the same agent answers your phone: questions answered, appointments booked and moved, confirmations texted. Anything it can't finish lands with your team, with the caller's context attached.

  • Natural phone conversations, day and night
  • Books and moves appointments in your calendar
  • Complex calls routed to people, with context
  • Same systems, same permissions as chat
// A call, handled
Ring → agent picks up
Caller: "Can I move my Tuesday appointment?"
→ checks calendar
→ offers Thursday 2pm
→ books, confirms, texts the details
✓ done in 45 seconds

Chat is coming soon.

The conversation layer runs on Mark's corpus and your own systems. The reading layer it stands on is live today.

Use Mark todayBack to the essay →
anywaye