We have one phone and three staff. Does that work?

Yes. One number, one shared inbox, assignment and internal notes so two people never reply to the same customer, and roles that decide who can do what.

Can customers book without calling?

A public booking page shows the slots your service rules actually leave open, and creates or links the contact when someone books.

Do reminders send automatically?

They are prepared automatically and queue for approval, so a reminder never surprises you. Each booking gets one, tracked so it cannot go twice.

What if someone asks something the AI cannot answer?

It hands the conversation to a person with the full thread attached. Drafts show their sources, so a reviewer can see when there were none.

Can we reply to Google reviews here?

Reviews come into the same inbox with a drafted reply for approval, so the public record gets the same attention as a message.

Do we need WhatsApp to start?

No. Telegram connects in about a minute with no business verification, which is the quickest way to see it working. WhatsApp takes longer because Meta verifies the business.

Can different staff see different customers?

Yes. A member can be restricted to contacts assigned to them, and phone numbers and email addresses can be masked for staff who do not need them.

What happens to a message that arrives at 2am?

It is answered if it is routine and you enabled that, and otherwise it waits in the inbox with a draft already written for whoever opens it first.

Every message answered, even mid-appointment.

A clinic, salon, studio, or workshop cannot answer the phone while serving someone. Messaging is the only channel that waits patiently.

Local service businesses run on appointments, and most of their new customers arrive as a message asking about availability, price, or location. Business messaging replaces the missed call and the voicemail nobody checks: the question is answered from your own information, the booking is confirmed on the same thread, and the reminder goes to the phone the customer actually carries.

What usually goes wrong.

You cannot answer while you are working: The person who knows the answer is with a client. Calls go unanswered, and a caller who reaches voicemail usually calls the next business on the list rather than leaving a message.
No-shows are paid for twice: An empty chair costs the appointment and the slot somebody else wanted. A reminder on the channel the customer reads fixes most of it, and sending reminders by hand is the first thing that stops on a busy day.
The same three questions, all day: Opening hours, price, parking, whether you take a walk-in. Every one of those answers already exists somewhere, and every one is retyped several times a day by whoever is nearest to the phone.

What Otobiz does about it.

Messages answered while you work

WhatsApp, Instagram, Messenger, and Telegram land in one inbox, and routine questions are answered from your own hours, prices, and policies without anyone stopping what they are doing.

One shared inbox for the whole team
Hours, location, and price answered from your knowledge base
Anything unusual handed to a person with the full thread

Answers from your own information

The AI drafts from what you connect: uploaded files, your crawled website, question and answer pairs you write, and the contact's own history. Every draft names the sources it used, and says so plainly when it has none.

Files, your own website pages, written notes, and Q&A pairs as sources
Sources shown on the draft before anyone approves it
Replies written in the language the customer used

Bookings taken on the thread

Publish your services with a duration, a buffer, and the hours you actually work, and a public booking page shows only the slots that are genuinely free. Two customers cannot take the same slot, whoever checks the diary last.

Services with duration, buffer, price, and location
A public booking page that creates or links the contact
Two customers cannot take the same slot

Reminders that go out on their own

Confirmed bookings send a reminder ahead of the appointment on the channel the customer uses, once and only once. The reminder queues for approval like any other scheduled send, so nothing goes out that you did not want.

One reminder per booking, tracked so it cannot repeat
Sent on the customer's own channel
Queued as an approval before anything sends

Reviews answered in the same place

Google Business Profile reviews arrive in the same inbox as your messages, with a reply drafted from your own tone and information, so the public record of your business gets the same attention as a direct message.

Reviews pulled in beside messages and comments
Replies drafted and posted after approval
Review history kept on the customer record

A person on anything that matters

Campaigns, scheduled sends, and anything that writes to another system queue for approval. The approval is bound to the exact message you approved and re-checked at send time, so what the approver saw is what goes out.

Approve, edit, or reject before anything leaves
The message you approved is the message that sends
Every send logged with who approved it

What matters most here.

Common questions

We have one phone and three staff. Does that work?: Yes. One number, one shared inbox, assignment and internal notes so two people never reply to the same customer, and roles that decide who can do what.
Can customers book without calling?: A public booking page shows the slots your service rules actually leave open, and creates or links the contact when someone books.
Do reminders send automatically?: They are prepared automatically and queue for approval, so a reminder never surprises you. Each booking gets one, tracked so it cannot go twice.
What if someone asks something the AI cannot answer?: It hands the conversation to a person with the full thread attached. Drafts show their sources, so a reviewer can see when there were none.
Can we reply to Google reviews here?: Reviews come into the same inbox with a drafted reply for approval, so the public record gets the same attention as a message.
Do we need WhatsApp to start?: No. Telegram connects in about a minute with no business verification, which is the quickest way to see it working. WhatsApp takes longer because Meta verifies the business.
Can different staff see different customers?: Yes. A member can be restricted to contacts assigned to them, and phone numbers and email addresses can be masked for staff who do not need them.
What happens to a message that arrives at 2am?: It is answered if it is routine and you enabled that, and otherwise it waits in the inbox with a draft already written for whoever opens it first.