All professions
Appointments

The shop can be busy without the inbox going quiet.

The barber desk answers services and hours, captures barber and time preference, and leaves the request pending until the real book confirms.

VERIFIED OUTCOME

After-hours chat → service + barber preference → pending slot request

Uses the accepted salon request pattern, with its own profession profile

BarbershopsChecking API
Prepared
Real API when active. Fictional test data only. No external action is performed here.
DEMO RECEPTION

I am the barbershop demo receptionist. Use fictional details. Tell me the service and preferred day; the shop still confirms the slot.

Do not enter real names, phones, account numbers, medical information or secrets.

01

What a useful day looks like.

The agent does not “do everything.” It moves each conversation to the next authorized state and shows what is still waiting.

  1. 01

    After hours

    Answers hours, location and approved services.

    Answered
  2. 02

    Preference

    Collects service, barber and time without promising a chair.

    Captured
  3. 03

    Full book

    Offers waitlist or callback workflow after calendar evidence.

    Pilot
DELA / BARBERSRECEIPT
OUTCOME OBJECTAfter hours

Source recorded · human owner visible · destination pending until a verified response arrives.

Reviewable
02

More than chat: the complete profession desk.

Each module earns its status separately. A real conversation never implies that every external system is connected.

ANSWERPilot / Piloto

Approved answers

Services, hours, policies and terminology from reviewed sources.

CAPTUREPilot / Piloto

Structured requests

Turns a conversation into the exact fields the team needs.

SCHEDULEPilot / Piloto

Agenda

Availability, request and confirmation stay separate and visible.

RECORDS— / —

Records

Keeps the client or patient trail organized under the right permissions.

BILLING— / —

Billing

Prepares reviewable billing work without inventing fiscal validity.

PAYMENTSPilot / Piloto

Payments

Uses approved providers and marks paid only after a verified receipt.

ORDERS— / —

Orders

Builds a clean draft; stock, price and submission remain controlled.

FOLLOWUPPilot / Piloto

Follow-up

Recovers open work with consent, ownership and a visible state.

INTEGRATIONSPilot / Piloto

Connections

Read first, test safely and require evidence from the destination.

Professional boundary

No live chair, payment or message is created in the public demo.

03

What is connected, what needs a pilot, and what waits.

No integration becomes “live” because its logo appears in a catalog. It must pass the exact workflow test.

Profession agentPilot

Dedicated Lety profile must pass acceptance.

Booking calendarPilot

Availability and create/cancel scopes are separate.

SMS / WhatsAppPilot

Consent, approved channel and delivery receipts required.

See the DelAgentIA connection contract
04

Questions for Barbershops.

Specific answers, not generic AI promises.

Can it handle walk-ins?

It can explain the shop policy and capture a callback or waitlist request. It cannot guarantee a walk-in wait.

Can each barber have a schedule?

Yes as a pilot once the calendar exposes staff availability and permissions are mapped.

Is this the same bot as the salon?

No. The runtime is shared, but the profession profile, knowledge, limits and provider conversation are separate.

BARBERSHOPS

Start with one outcome. Connect the rest only after it works.

The initial web experience can prove the conversation. Operational connections are scoped, tested and priced separately.

Build this desk