Use case · Service Bookings

Three quotes, one booking, no calls.

How Aule handles a service appointment end-to-end — calls vendors, gets quotes, recommends, books, pays, confirms, follows up.

Last updated · 2026-05-19

TL;DR

The household says “kitchen sink is dripping.” The layer calls three local plumbers, gets quotes, recommends one (with reason), books the appointment, pays on receipt, returns the receipted close, and remembers the vendor for next time. No phone tag, no scheduling juggle, no chasing the invoice.

Scene one

Tuesday morning — the prompt.

The household says: “kitchen sink is dripping under the cabinet, looks like the trap. Can you handle it?” That is the entire input. Nothing about budget, nothing about which plumber, nothing about scheduling. The layer holds those.

Scene two

Tuesday afternoon — the calls.

By 2pm Aule has called three local plumbers, described the diagnostic, gotten the quotes, and ranked the options. Here is what the household sees.

Three quotes for the kitchen-sink trap

Diagnostic: P-trap leak, no visible damage to the disposal. All three vendors are vetted; one is already in your household memory.

Reliable Plumbing — Frank (recommended)
Available Wednesday 10am. Quote includes parts; flat rate.
Quoted by Frank · 1.2 mi · used by household March 14
$185
Brookline Mechanical
Available Wednesday 2pm. Includes diagnostic fee credited toward repair.
Quoted by dispatcher · 3.4 mi · new to household
$240
AllCity Plumbing 24/7
Available today (emergency tier). Higher rate; not needed here.
Quoted by night dispatcher · 5.8 mi · emergency-grade vendor
$310

Aule recommends Reliable Plumbing — you used them in March (clean work, $215 for the dishwasher install), and their quote is the lowest of the three.

Scene three

The approval gate.

$185 is below the $200 spend threshold, so technically the layer could book full-auto. It does not. Vendor selection is a household-specific judgment call, and the layer treats it as a confirmation moment regardless of the spend size. The household taps approve.

Over the next several cycles, as the layer sees the household always pick the recommended vendor, the gate on recurring categories (plumbing, with Reliable Plumbing as the preferred vendor) can loosen to full-auto. The first few cycles are confirmation. That is how trust gets earned.

Scene four

Tuesday evening — the booking.

The layer calls Reliable back, confirms Wednesday 10am, sends Frank the diagnostic notes (P-trap, no visible damage to the disposal, the household will be home and the dog will be in the bedroom), and authorizes the payment method against the household's card. Confirmation arrives in the household's preferred channel - text in this case.

Scene five

Wednesday morning — the work.

Frank arrives at 10:04am. The trap is the trap; replaces in twenty minutes. Total: $185 (parts and labor). Frank photographs the finished work, sends the invoice through the channel Aule set up with the vendor, the payment runs.

Scene six

Wednesday afternoon — the receipted close.

The receipted close: the invoice, the photo of the finished work, Frank's note (“trap was original; the new one is brass and should last; the disposal is fine”), the suggestion that the bathroom-sink trap should probably be checked at the same time next visit. The household memory layer absorbs all of that.

What the layer learned

The household memory layer at work.

Frank from Reliable Plumbing is now a known vendor: clean work, fair pricing, communicates well. Next time something plumbing-shaped surfaces, Aule starts the search at Reliable's quote and benchmarks others against it. Frank's suggestion about the bathroom-sink trap is queued for the next regular maintenance window. The dog is noted as preferring to be in the bedroom during vendor visits.

None of that is in a settings panel. The layer learned it from one closed loop.

Under the hood

What ships today.

The service-booking loop runs on an outbound voice integration with operator-tuned vendor scripts per category, a payment-authorization layer for invoiced vendors, and the household memory layer that holds vendor quality signals. Service categories live in production include plumbing, electrical, HVAC, appliance repair, handyman/general contractor, and a handful of routine categories (lawn, gutters, pest). New categories are an operations request, not a product roadmap item.

Common questions

Honest answers.

01How does Aule actually call the plumber?

Through an outbound voice integration with operator-tuned scripts per vendor category. The layer dials, navigates the receptionist or the booking IVR, describes the diagnostic, asks for the quote and the next-available window, and logs the result back into the household memory layer. The vendor experiences a polite, well-briefed caller with a clear ask; the household experiences the same loop closing without needing to be on the call.

02What if Aule's three quotes are all bad?

The layer surfaces the quote round to the household with the diagnostic notes from each call. If the household says none of these are right, the layer extends the search - more vendors, broader radius, different category framing - and runs a second round. If the household has a preferred vendor not yet on the layer, adding them to the network is an operator-side update; the household does not have to manage the vendor list.

03What if the spend is below the $200 approval threshold?

Even below the threshold, the layer asks before booking a new vendor, because vendor selection is a household-specific judgment call. The $200 gate catches spend; the vendor-selection gate catches identity. Both gates loosen as the layer earns trust - over time, recurring vendors become full-auto.

04Does Aule pay the plumber on my card?

Yes, with confirmation. The household holds the payment method; the layer authorizes the payment based on the receipted invoice the plumber sends back. For known vendors and confirmed work, the authorization happens automatically once the household has approved the work; for first-time vendors, the household sees the invoice and confirms before the charge runs.

05What about emergency repairs?

If the household says it is urgent, the layer escalates - faster quote round, shorter triage, the operator on the line if needed. The full-auto path is for routine service; emergencies route through the human operations partner. The layer recognizes the urgency framing in the prompt and adjusts the workflow.

Two ways to keep going.

See your own number

Take the Mental Load Index.

A five-minute assessment of your household operating load.

Open the assessment →

Another loop

A week of meals.

The meal-planning loop, end-to-end - prompt to plate.

See the loop →

Continue with Aule