A driver asks an agent to book the service. Everything rests on one answer.
People are starting to hand the whole service booking to an agent, in the car or on the phone. The agent can only book the appointment when the shop side is current and committable. Most service shops are not yet ready for an agent to find them accurately, read their real state, and act with confidence.
A few shops look possible, but the open bays and Thursday hours read as hours old. I cannot confirm a service appointment for that window without the shop own current answer.
The service list on the map and the capability on the shop site disagree, and technician skill is not exposed. I cannot be confident the shop can take this vehicle and this issue.
Public pages do not show parts lead time and disagree on whether an estimate comes before authorisation. I cannot commit the appointment without the shop confirming the parts and the estimate terms.
The agent-human transaction
A driver delegates the booking. The agent has one question.
The driver never sees the work behind the answer. The agent will only book the appointment when the shop side is current and committable. Obenan governs that merchant truth and makes the merchant side committable before the agent acts, then hands off to the booking and payment layer.
The driver says
“Book a brake inspection and oil change for my 2021 hybrid SUV near my office Thursday morning, dropped off before 8:30am, ready by 5pm, a shop that services hybrid brakes, parts available this week, and an estimate before any repair beyond the inspection.”
The agent asks
Can this merchant commit to this transaction, right now.
Current and committable
A confident yes. The appointment can proceed.
Stale or unverifiable
The appointment breaks here, at the service desk, after the driver thought it was set.
Why a service appointment rests on merchant truth
An appointment cannot be booked on stale facts.
Automotive service is not a clean prepaid purchase like parking or a fixed ticket, because the final scope and price often depend on diagnosis, technician skill, bay time, and parts. What the agent commits to is the appointment, and that appointment rests on facts that change through the day. The agent will only act when it trusts them, and only when the shop has actually made a promise it can keep.
Service menu and appointment type
An oil change, an inspection, a diagnostic, and brake work need different bay time and skills, and a booking fails on the wrong service type.
Bay capacity and the time slot
A shop cannot honor an appointment if the right bay time is not free for the requested window.
Technician skill and vehicle fit
Hybrid, EV, diesel, alignment, and diagnostic work can require skill matching, and a generic booking is not committable.
Parts lead time
An appointment is useless if the shop cannot source the likely parts before the promised completion window.
Drop-off, waiter, loaner, and pickup rules
The visit depends on whether the shop supports the requested drop-off, waiter, shuttle, or loaner style.
Estimate scope and authorisation
A variable repair is not a fixed-price purchase, and the diagnostic fee, estimate, and authorisation threshold must be explicit before commitment.
The transaction sequence
What happens when an agent is ready to book a service appointment.
Obenan makes the merchant side current and committable. The booking and payment layer handles the appointment and any money. No overlap, no checkout page, no card data.
A driver hands the task to an agent
Driver and agentThe driver delegates the whole booking: a brake inspection and oil change for a 2021 hybrid SUV near the office, a Thursday morning drop-off, a 5pm pickup, hybrid brake capability, parts available this week, and an estimate before any repair beyond the inspection.
The agent asks one question
AgentBefore it can act, the agent needs one answer: can this merchant commit to this transaction right now.
Obenan makes the merchant side answerable
Merchant truthIdentity and address, service entrance and hours, service menu and appointment type, bay capacity and the time slot, advisor availability, technician skill and vehicle fit, parts lead time, drop-off and loaner rules, warranty routing, and estimate and authorisation terms are governed and current, with a freshness and confidence signal the agent can read.
The merchant side becomes committable
Merchant truthWhen the service type, the bay time, the technician fit, the parts, and the estimate terms are all current, the question gets a confident yes. If anything is stale or unavailable, it stays discoverable and does not become committable.
The moment a stale answer would have broken the appointment at the service desk.
Obenan makes the merchant side committable, then hands off. No checkout page. No card data crosses this line.
Obenan hands off the current merchant answer
HandoffThe current, committable merchant answer passes to the booking and payment layer the shop already uses. The Obenan role ends here. No checkout page. No card data.
The booking and payment layer takes the transaction
Booking and paymentThe automotive or mobility platform, PSP, acquirer, or card network presents the appointment and any deposit or authorisation step, manages authentication, and handles all card data and compliance.
Confirmation returns to the driver
Booking and paymentThe confirmed appointment and its details flow back through the agent to the driver. The slot is held for the window, and the shop is notified through the systems it already runs.
Obenan makes true
Identity, service entrance, service menu and appointment type, bay capacity, advisor availability, technician skill, parts lead time, drop-off and loaner rules, warranty routing, and estimate and authorisation terms, with freshness and confidence.
The payment layer handles
Appointment, checkout, authentication, card data, deposit, authorisation, and settlement.
Obenan does not
Process payments, host checkout, handle card data, diagnose vehicles, source parts, or replace the shop, repair-order, or booking system.
The same service request, answered with current merchant truth.
When merchant reality is governed and queryable, the agent stops hedging. It answers with the right service type, a shop that fits the vehicle, parts confirmed for the window, and estimate terms a driver will accept, the shape a service shop wants for every agent-assisted booking.
Three shops near your office hold a Thursday morning slot for a brake inspection and oil change. The nearest reserves the bay until you confirm, checked against the shop own live schedule under a minute ago, with the drop-off and 5pm pickup window confirmed up front.
This one has a certified technician for hybrid brake systems on Thursday morning, taken from the shop own current record, not a stale listing.
The brake pads are in stock this week, and the shop confirms an estimate before any repair is authorised, from its own policy. I can hand this appointment to the booking step now.
The merchant layer is not theoretical for us
Already operating the merchant reality layer.
Service readiness is not a concept pitch. Obenan already governs merchant truth on the public surfaces where agents look, so AI systems can find, describe, and act on a service location correctly.
What the operating layer already does in production
Online and offline service truth
One governed record for identity, service entrance, hours, and service menu that stays true at the shop and across every surface a driver or agent reaches.
Found and read correctly by AI
Structured so assistants describe the shop, its service capability, and its policy accurately, not approximately.
Merchant-controlled updates across channels
Service menu, bay availability, technician skill, parts, and policy move from the shop outward, continuously, without per-channel rework.
Now extended toward agent-committable service
Merchant truth exposed in the shape an agent needs before any appointment begins.
Clear scope, clear boundaries
What Obenan does, and what Obenan does not do.
What Obenan does
- Keeps identity, service entrance, hours, and service menu governed and current
- Structures bay availability, technician skill, parts lead time, and policy for agent queries
- Reflects freshness and confidence in what an agent can rely on
- Gives shops a controlled path into agent-assisted booking
What Obenan does not do
- Does not process payments
- Does not host checkout or handle card data
- Does not diagnose vehicles, estimate repairs, or source parts
- Does not replace your shop, repair-order, or booking system
How early participation works
Three steps, no rebuild.
Make the shop readable
Identity, locations, service entrances, and hours become governed and queryable.
Make merchant state current
Service menu, bay availability, technician skill, parts, and policy stay fresh with confidence signals.
Make the handoff clean
Agents reach booking and payment on truth the shop already controls.
Early service readiness partner
The shops that shape agent-assisted service will be the ones moving before the category catches up.
This is not an open sign up. A small number of service teams will help define how merchant readiness works in practice, and the window to be one of them is the period before the shift becomes obvious to everyone else.
Twelve months from now, the question is not whether your shop is agent-ready. It is whether your shop helped define what agents can trust.
By industry
Next step
Talk to us about becoming a merchant an agent can book.
The next conversation is short and specific. Service and dealership leaders use it to understand where their merchant truth currently sits and what an early pilot could look like.