Solution · Local services

Capture every lead while your team is busy serving the last one

OrcaLinq answers website and WhatsApp messages instantly, books slots when the calendar allows, and lets your team take over from the messaging app they already use.

The problem

Local service businesses lose money to missed messages

Customers expect a reply in minutes. Local teams answer when they can — between jobs, after the school run, before close. AI-first answering closes the gap honestly, without faking availability.

After-hours capture

Bookings, callback requests, urgency triage when the team is unavailable. Sonar reads intent so the right thing happens.

Booking with tools

Connected calendar tools mean the AI can hold and confirm slots without inventing times. No double-bookings.

Photo and detail collection

On supported channels, customers attach photos. The team gets the photo with the booking, not after they arrive.

Honest about availability

If no one is available, the AI says so and proposes a callback window. Never fakes capacity, never promises 'someone will get back to you' when that won't happen.

Conversation example

After-hours booking that actually happens

Saturday 9 PM. Team is closed. Without AI, this customer messages a competitor and you find out Monday.

Customer (WhatsApp, Saturday 9:14 PM): "Hi, dog grooming for a golden retriever this week?"

AI: "Yes! We groom golden retrievers most days. Standard groom for a large breed is ₹1,800 and takes about 90 minutes. Earliest open slots are Tuesday 11 AM, Wednesday 3 PM, or Thursday 10 AM. Want me to hold one?"

Customer: "Tuesday 11 works. Also, he's a bit anxious — does that matter?"

AI: "Anxious dogs are common — we keep a quiet bay for them. Could you share his name and any specific triggers? I'll add a note for the groomer. Slot is held; sending confirmation."

Customer: "Bruno. Hates clippers near his ears."

AI: "Got it. Tuesday 11 AM, Bruno, anxious near ears, scissors-only on ears. Confirmation sent. Anya the groomer will text you Monday evening to confirm. See you then!"

Anya wakes up Monday to a note in Wake: "Bruno, golden retriever, anxious, scissors-only on ears." No phone tag, no missed booking, no awkward arrival surprise.

Recommended setup

Three things to wire before launch

  • Website widget on every service page, with the service slug pre-filled in context.
  • WhatsApp Cloud API with your verified number for the channel most customers prefer.
  • Calendar integration — Google Calendar, Calendly, or your booking tool's calendar.
  • Approved knowledge: services, prices (where fixed), opening hours, location, holiday schedule, what to bring.
  • Routing policy: bookings → reception/owner; complaints → owner; out-of-hours → AI captures and queues for first morning slot.
Features used

What's doing the work

Semantic routing

Bookings, complaints, sales, and quote requests route to different humans (or stay with AI). Owner-defined.

Knowledge base AI

Services, prices, hours, location, parking, what-to-bring — all answered from approved knowledge with citations.

AI human handoff

Forced handoff on complaints, refunds, anything outside the menu. Customer never gets stuck in a bot loop.

Agent-native endpoints

Owner replies from WhatsApp on the road. No desktop dashboard required for day-to-day.

Wake

Every booking, every escalation, every missed slot logged. Owner sees what AI handled and what needed attention.

Metrics to improve

What a small team feels in week two

  • After-hours bookings captured — typically zero before, several per week after.
  • Phone-tag round-trips — fall as customers self-serve via chat with calendar holds.
  • Owner attention on routine messages — drops sharply, freeing time for the actual service work.
  • First-reply time on Saturday afternoons — goes from hours to seconds.
  • Lead-leakage to competitors — measurable after a few weeks of side-by-side comparison.
Local services FAQ

Frequently asked questions

What counts as a 'local service' business?

Salons, spas, dentists, vets, repair shops, electricians, gardeners, cleaners, mechanics, photographers, fitness studios, tutors, pet groomers, and any team where a missed customer message means a lost booking.

Can the AI book directly?

Yes — when a calendar tool is connected. The AI proposes a slot, holds it, and sends a confirmation. Cancellation and rescheduling follow the same flow with a Wake audit entry. Without a calendar tool, preferred times are routed to the team.

What about after-hours messages?

Customers don't stop messaging at 6 PM. The AI captures the request, qualifies it, and either books a slot or queues the conversation for the team's first reply window — depending on policy. The customer always gets an honest, immediate answer instead of silence.

What if our team only uses WhatsApp?

That's exactly the agent-native posture the platform supports. Your team replies from WhatsApp; customers can reach you via web, WhatsApp, Instagram, or any other connected channel. No new dashboard to learn.

Can the AI quote a price?

Only from approved knowledge. If your services and prices are uploaded, AI quotes from that document and cites it. If a price requires a site visit (most trades work this way), AI says so and books the visit instead of inventing a number.

What if the same customer messages us back?

Conversation memory is keyed by customer identity. Returning customers get the same agent where possible, prior bookings are visible, and the AI personalizes the greeting without inventing history.

Is this useful for businesses with one or two staff?

Especially for those. A founder-led service business can't sit at a phone all day; AI answers the routine while the team is on a job, and pages the right person when something needs attention.

See your booking workflow run on AI.

Bring your calendar tool and a couple of recent customer messages. We'll show what fully-booked, partially-full, and 'this needs a person' conversations look like.