Answer as the organization, and prove it’s you.

A clinic, a shop, a school, a nonprofit or a public service gets a profile people can trust once it verifies its domain, and one inbox where its team answers customers as the organization. Customers write from the app they already use for everyone else in their life.

Start free Pricing

Specification

Verification: One TXT record on your domain. Verified shows on your page and beside your team; it is checked, never bought, and yours again if you ever close and come back.
The inbox: Every customer conversation in one place, sorted by who has waited longest, in six views: needs a reply, new, assigned to me, waiting for the customer, escalated, resolved.
The team: Owners, admins and members. A customer sees the organization, never which person answered. A seat that ends takes nothing with it.
Writing first: Your team may write to someone first. It arrives as a request: one message until they answer, and their answer opens the conversation.
The ai agent: Answers from what you wrote down (up to 8,000 characters), is marked as an AI, and hands over to a person the moment it isn’t sure. It never speaks for the team.
Bookings: Set bookable hours once. Customers pick from the open slots, your AI agent offers the next few and books the one they choose, and every booking is an appointment your team confirms.
Apps: A helpdesk, a CRM or your own bot: a token that reaches only your conversations, a signed webhook, and cards of your own design.
Updates: Post to everyone who follows you. Nobody sees who follows, and nothing about following reaches anyone’s inbox.
Spaces: Spaces for the team, a project or a branch, started from the organization’s page, with your team already there to pick from.
Calls: Voice and video, one to one and in groups of up to 8, in the browser.
Insights: How fast the team answers, how many customers write and what is still open. On Business.
Price: Free for a team of 3, with one app. Business for the rest: pricing.

A customer’s day · pick a step

01 A customer writes 02 The agent answers 03 The team answers 04 Your tools hear it

01 · A customer writes

It lands in the inbox, first if they’ve waited longest.

Lina writes to Nile Dental from the app she uses for everyone else. The team sees one conversation, its state and who has it; Lina sees the organization, never which person.

Needs a replyLina · Can I book a cleaning on Thursday?

new · nobody has it · 2 min

02 · The agent answers

From what you wrote down, and it says so.

The organization’s AI agent answers only from its knowledge (up to {n} characters you gave it), is marked as an AI, and hands over to a person the moment it isn’t sure. With bookable hours set, it offers the open slots and books the one the customer picks; with orders on, it writes down what they ask for from the menu. The team confirms each, reads the sentence of its knowledge every answer rests on, and says what it may do and when it answers.

I can offer Thursday 10:00 or 10:30. Which suits you?

AppointmentCleaning · Thursday 10:00 · requested

Nile Dental · AI agent · automated

03 · The team answers

Whoever answers has it; the customer hears from the organization.

Answering takes the conversation. Assign it, escalate it to an owner or admin with a note, or resolve it; it comes back the moment the customer writes again.

10:00 is yours. See you Thursday.

Waiting for the customerYou have it

04 · Your tools hear it

A helpdesk, a CRM or your own bot, in the same conversation.

An app’s bot replies as the organization, marked automated, and never counts as the team’s answer. Its webhook hears each message and each change of state.

business.threadresolved · by person

kit.movedBooking · confirmed · by customer

Start free For developers