Your AI Confirmed the Showing. The Calendar Didn’t.

By Anna with Oppy | October 17, 2026

A buyer types, “Friday at 2 works.” Your AI sees a calendar hold and replies, “Confirmed.”

One problem: the showing agent never accepted it. Another: the hold was for a mortgage consultation. A third: nobody specified the time zone.

The model wrote a perfectly good sentence about an appointment that does not exist.

The useful fix is not another reminder. It is an appointment-integrity gate: a small check between finding a possible slot and making a customer promise. Below is a proposed two-Oppy workflow, with instructions you can adapt and a test you can measure. It is a configuration design, not an announced Oppy feature.

Why this deserves attention now

In a HousingWire interview published October 16, Rudy Zabran, COO of Consolidated Analytics, described roughly 60,000 loans flowing through its operations in a typical month. He discussed its LoanDNA document technology, then made a point that applies beyond mortgage processing:

“You have to start with your governance, right?”

The quotation comes from HousingWire’s published interview text. The piece is Content Studio material, and the loan volume is the executive’s account, not an independently audited benchmark. The lesson is narrower than the scale: decide who can authorize an action before making that action easier.

Customer journeys are also crossing more service lines. RISMedia’s September 14 report on Berkshire Hathaway HomeServices Florida Realty’s redesigned websites describes property search across 22 counties and connections to title, mortgage, insurance and property management services. That does not establish shared scheduling. It illustrates why appointment type and responsible team cannot be inferred from the customer’s name.

The same person can be a buyer, borrower and insurance prospect. “Friday at 2” still needs a noun.

Six facts before “confirmed”

Keep a short appointment packet in an approved shared record. These are suggested workflow fields, not a native Oppy schema.

  1. What: Appointment type, property or service resource, and duration. A showing and a loan consultation are different commitments.
  2. When: Exact date, start and end time, and named time zone. Store the corresponding offset or unambiguous timestamp when your scheduling system provides it. Ask rather than infer.
  3. Capacity: Availability evidence from the designated source, when it was checked, and whether the slot is merely held or actually booked.
  4. Customer acceptance: The message or other approved record showing that the customer accepted this particular appointment and time.
  5. Accountable owner: The person or role authorized to commit the required resource, plus their acceptance evidence. A name in the CRM is not acceptance.
  6. State and wording: proposed, held, verified for confirmation, confirmed, cancelled, or needs resolution, alongside the exact customer draft.

If a material fact changes, the earlier approval no longer applies. A moved slot, different property or replacement host should trigger a fresh check. Do not send an old approved draft against a new appointment packet.

Configure two Oppies with different jobs

Oppy describes dedicated agents and connections to existing tools, including through Zapier and Make. That does not verify a particular account’s calendar access, booking permissions or approval controls. First identify your actual tools and permitted actions. If the required source is unavailable, the workflow should stop at a question.

Oppy 1: Appointment Verifier

Give this role approved read access where available. Begin without calendar-write or customer-send authority.

ROLE: Appointment Verifier

Use only the designated, enabled sources.
Build the six-field appointment packet:
WHAT, WHEN, CAPACITY, CUSTOMER ACCEPTANCE,
ACCOUNTABLE OWNER, STATE AND WORDING.

Never infer a time zone or owner acceptance.
A calendar hold is not a confirmed booking.
Customer interest is not acceptance of an exact slot.

If a field is missing, stale under the team's policy,
or contradictory, return NEEDS RESOLUTION.
Name the missing fact and the person who must resolve it.

Return VERIFIED FOR CONFIRMATION only when the
approved source and owner support the same appointment
accepted by the customer.

Do not create, move, cancel, or confirm external events.
Do not send customer messages.

OUTPUT:
STATE:
SIX-FIELD PACKET:
EVIDENCE REFERENCES:
CONFLICTS:
NEXT OWNER ACTION:

Oppy 2: Customer Draft

This role translates verified facts into a readable message. It does not repair missing facts with enthusiasm.

ROLE: Customer Draft

Work from the Appointment Verifier's packet.
Do not upgrade its state.

If NEEDS RESOLUTION, draft one clarification question
or return NO CUSTOMER DRAFT if internal review is needed.

If VERIFIED FOR CONFIRMATION, prepare a short draft
stating appointment type, full date, time zone,
location or joining instructions, and host.
Do not include internal evidence links or private notes.

Label every output DRAFT FOR HUMAN REVIEW.
Do not send, book, or mark the appointment CONFIRMED.
If the packet changes, discard the earlier draft.

The responsible person checks the live scheduling source immediately before release, resolves any conflict and sends through the approved channel. Record confirmed only after the required booking and customer communication steps are complete under your process.

A prompt is not a transaction lock. If you later automate release, use your workflow software to enforce permissions, recheck the current record and prevent duplicate or stale actions. Do not expect prose instructions to provide those guarantees.

Test the failure, not the happy path

Use draft-only mode for ten business days. Oppy’s setup guide recommends preserving earlier instructions, pausing or delaying replies after material changes, inspecting generated messages and testing them manually.

Seed the test with four awkward cases: an unspecified time zone, a held slot with no owner acceptance, two appointments for the same customer, and a time changed after the draft was approved. Each should stop or request the relevant clarification, not produce a ready-to-send confirmation.

Track unsupported-confirmation rate: drafts using confirmed language without complete supporting evidence, divided by all confirmation drafts. Set a proposed release threshold of zero in the test sample. That is an acceptance criterion, not a promise about future performance.

Also measure median resolution time and the proportion of appointment packets needing human review. Zero unsupported confirmations achieved by blocking every appointment is not a successful design. It is a very polite outage.

Where should you pilot? Mike DelPrete’s analysis of 2024 CoreLogic/Cotality data found the top 20% of producing agents completed 65% of transactions, while the top 1% handled 18%. The dataset covered 3.4 million sales and 840,000 producing agents, representing 85% of the market; team production was attributed to one agent.

Those figures do not measure appointment errors. They suggest starting where volume concentrates, then measuring your own baseline rather than designing for an imaginary average agent.

Make the promise smaller than the evidence

The workflow also fits a property manager scheduling a visit, a title office arranging a signing, or a dental office coordinating an appointment. The resource changes. The distinction between available, held and confirmed does not.

Keep sending permission separate from scheduling certainty. A verified slot is not permission to initiate any call or text. Twilio’s A2P 10DLC documentation describes carrier registration for application-originated messages over U.S. ten-digit long-code numbers. Registration does not establish a recipient’s consent or resolve applicable legal requirements.

An Oppy can help collect the facts and prepare the words within its approved scope. A person owns the commitment.

“Confirmed” should describe what happened, not what the system hopes happens next.

References