Questions we get asked

Homer identifies itself as an assistant if asked, and we recommend it always does. We're not trying to trick anyone — in practice callers care far more about being answered at 4am and getting a real appointment than about who took the details.

You control the greeting, the name, and the disclosure. Some states require call-recording notice; Homer handles that automatically based on where the caller is.

It says so, and either takes a message with full context or transfers to a human — your choice, configurable by topic and time of day. It does not guess at prices, promise arrival times it can't verify against the schedule, or invent policy.

Every call where Homer hit the edge of what it knows gets flagged for review, so the gaps get closed rather than repeated.

It recognises escalation and routes it to a person quickly — that's the design. A complaint about a job that went wrong is exactly the call you want a human on, and Homer's job is to get them there fast with the history already pulled up, not to manage it itself.

Yes. You keep your number — most customers forward it, either entirely or as overflow after a set number of rings. It works with RingCentral, Twilio, Google Voice, and standard SIP. Nobody has to reprint a truck.

Yes, and it switches mid-call when the caller does. Job records are written in English so your office and techs read one language, with the original transcript kept alongside.

Good, we wouldn't ask you to. Homer's autonomy is set per action. Most companies start with it suggesting — it drafts the board, proposes the assignment, drafts the quote — and a human approves. As you watch it get things right, you turn individual actions loose.

A common path: after-hours booking in week one, dispatch suggestions in week three, autonomous dispatch within the month, quoting under a dollar threshold after that.

It will, occasionally — so will your dispatcher. The difference is that every autonomous action is logged with what Homer knew and why it chose what it chose, so a mistake is diagnosable rather than mysterious, and the rule that caused it can be fixed.

Anything with real financial consequence — discounts, refunds, quotes above your threshold — sits behind human approval unless you deliberately open it up.

Most of our customers don't cut people — they stop hiring the next one, and move the people they have onto work that actually needs a human: memberships, difficult customers, following up on big estimates.

We'd rather tell you that plainly than pretend the question doesn't come up. If your plan is to reduce headcount, Homer can support it — but the companies that get the most out of it tend to redeploy instead.

About two weeks for most companies. Week one is data and configuration — customers, equipment history, price book, service area, job types. Week two, Homer takes overflow and after-hours calls while your team reads the transcripts, then takes more as you get comfortable.

Yes — customers, job history, equipment records, price book, and open work orders. We've done the common platforms and can work from an export or an API connection. On Growth and Custom this is included, not a professional services line item.

The honest test is whether it saves them time on day one. Techs talk instead of typing, the app works with no signal in a basement, and the write-up is done before they're back in the truck. Adoption problems usually come from software that adds steps; Homer removes them.

Starter exists for one-truck operations, and a solo operator who can't answer the phone while under a house is arguably who benefits most. But if you're doing a handful of jobs a month, you probably don't need this yet — and we'll tell you so on the call rather than sell you a plan.