BLOOMREL · HOUSTON PILOT / Illustrative data · No live demo requests
Built for the work beyond the call

You do the work.
We'll help keep
business moving.

An AI front office for busy service teams. Capture the request, give your team a clear next step, and see what turns into a job.

Starting with Houston plumbing teams · Human-led follow-up

A better handoff starts here
Jamie S.Illustrative caller · 7:42 PM
Request captured

“The kitchen sink keeps backing up. Can someone come tomorrow?”

ServiceDrain cleaning
Preferred timeTomorrow morning
Keep the outcome connected.Call → Follow-up → Job → Payment

Product illustration. A requested time is not a confirmed appointment.

A little less chasing. A clearer next step.After-hours intakeOwner-assigned follow-upJob & payment tracking

Answering is only
the beginning.

A good conversation needs a good handoff. The proposed pilot connects the request to the people responsible for what happens next.

01 / CAPTURE

Start with the right details.

AI intake collects the problem, service area, contact details, urgency, and requested timing using your business rules.

After-hours and overflow routing tested before activation.
02 / FOLLOW THROUGH

Make the next move clear.

Your team gets a request with an owner and a next action. Log a callback, record the outcome, and keep open requests visible.

People make follow-up calls in the first pilot.
03 / KNOW THE OUTCOME

See more than call counts.

Connect the request to a confirmed job and the payment your team records. Review what closed, what didn't, and what needs attention.

Recorded payments are not proof of incremental revenue.
The product, in three moments

From “I'll call back”
to a clear outcome.

Explore a fictional plumbing request. No call is placed, no calendar is changed, and no customer data is used.

REQUEST / EXAMPLE-001Illustration

A request. Not a promise.

Jamie wants help with a blocked sink tomorrow morning. The requested time is recorded for the office to review. No visit is confirmed by the AI.

Status: Needs review · Next action: Check availability
Illustrative scenario, not a recording or a real customer result.

Start focused.
Stay in control.

A supported pilot, not another system to figure out alone. We agree on the rules and test the handoff before routing customer calls.

The first pilot

One business. A clear workflow.

  • Business-specific intake rules
  • Service requests and preferred times
  • Owner-approved Google Calendar booking after connection
  • Manual follow-up with an assigned owner
  • Recorded job and payment outcomes
Connected in stages

Clear boundaries. No surprises.

  • Booking without owner approval
  • Automatic outbound calls or texts
  • Every CRM connection from day one
  • Collecting card details in a call
  • Guaranteed bookings or revenue

Early-stage product. Voice, routing, calendar, and fallback checks must pass before a customer pilot starts.

A connected workflow · Prepared

Your calendar.
Part of the picture.

Keep scheduling where your team already works. Google Calendar can be connected for owner-approved booking after we review permissions, availability, and booking rules.

Discuss your calendar

Google Calendar integration

Connection required
  1. Capture the requested timeThe caller's preference reaches the dashboard without a booking promise.
  2. Check availabilityAn owner approval checks the connected calendar for a conflict.
  3. Create the eventOnly an available, approved request is added. Your team then confirms it with the customer.

Prepared in the product; not activated for a business until its Google Calendar access and scheduling rules are configured and tested. No customer message is sent automatically.

Proposed pricing · For discussion

Start with a pilot.
Grow with evidence.

Agree on a focused scope, track the results, and decide on the next step together. No automatic upgrade from the pilot.

After the pilot · Planned

Ongoing service

$499/ month target

A target starting price for continued service, shaped by the pilot's volume and support needs.

  • Intake and follow-up workflow
  • Job and recorded-payment visibility
  • Ongoing rules and quality reviews
  • Usage and support agreed to your needs
Discuss your needs

Not available to purchase here. Calendar work is scoped separately.

Draft pricing in USD, not a binding offer. Included minutes, overage rates, pilot duration, any setup fees, taxes, and support limits are not finalized. Usage is not unlimited. Calendar integration, if feasible, requires a separate scope and quote.

Good questions

Let's keep
this simple.

Do we need to change our phone number?

The proposed setup starts with forwarding selected calls from your existing number. Compatibility, carrier costs, routing, and fallback behavior must be checked with your phone provider before activation.

Can it connect to our calendar or job software?

Google Calendar booking is prepared as an optional connection. Your team reviews a requested time, approves it, and the system checks for a conflict before creating the event. Business access and scheduling rules must be connected and tested first. Other job-software connections are assessed separately.

Who makes the follow-up calls?

Your office team does, in the first pilot. The dashboard organizes the next action and records each attempt and outcome. Automatic outbound calls and texts are not enabled.

What about urgent or unsafe situations?

We agree on escalation rules and test the fallback before activation. The assistant must not diagnose a dangerous situation or promise technician arrival. This is not an emergency response service.

How do we know if the pilot is working?

Agree on a baseline, then review captured requests, follow-up completion, confirmed jobs, recorded payments, and operating costs. A job that followed a call is not automatically a job created by the product.

What does it cost?

Our proposed pilot price is $249 per month. The planned ongoing service starts at a target price of $499 per month, subject to scope. Pilot duration, included minutes, overages, any setup or integration fees, and support must be agreed in writing before activation. These are draft prices, not a purchase offer. No payment is collected here.

Houston first. Built to grow.

Let's find the gaps
in your front office.

For plumbing teams with 3–15 service vehicles, room for more work, and someone who can own the follow-up.

Start with a short conversation about how calls arrive, who follows up, and what happens next.

Email Bloomrel directly:

This form prepares an email draft on your device. Review it, open your email app, and send it yourself. It does not submit a request to our server. Please do not include customer records or sensitive information.

No email sent until you send it in your email app · No appointment booked

Website privacy · Updated August 31, 2026

Know what happens
to your information.

This notice describes the current Bloomrel marketing preview and its email-draft contact feature. It does not cover future call handling, recordings, customer dashboards, or calendar integrations; those require separate notices and agreements before activation.

What happens when I fill out the form?

The form uses your name, business name, optional reply email, vehicle range, and selected topic to prepare a message in this page. Our form code does not upload these entries to our server or write them to browser storage. Opening the email link passes the draft to your configured email app, which may save or sync it under its own settings. Bloomrel does not receive the message unless you send it.

What happens if I send an email?

The message is addressed to Bloomrel at support@bloomrel.com. If delivered, its content and sender details are received in that Google Workspace mailbox so we can discuss your inquiry. Google and your own email provider process messages under their respective terms. Please do not send payment-card details, passwords, health information, or records about your customers.

Does this page use tracking?

This page includes no analytics scripts, advertising pixels, or embedded third-party forms, and its code sets no tracking cookies. The hosting provider can still process technical connection information, such as your IP address and request time, to deliver and protect the site.

Who can I contact about my information?

Contact Bloomrel at for questions or to request correction or deletion of a message you sent. This site does not establish a fixed retention period or guarantee deletion from email-provider backups.