Schedule Engine: what the new service-business platform advertises

Which Schedule Engine is this?

This guide covers the product at myscheduleengine.com. The site presents it as a modern command center for cleaning, landscaping, HVAC, plumbing, roofing, contracting, and other service businesses. Its sign-in, privacy, and support links point to app.myscheduleengine.com; app.scheduleengine.com appears in product mockup labels.

That identity matters because this is not the older Schedule Engine at scheduleengine.com, which is now part of ServiceTitan. ServiceTitan describes that product as legacy and points customers toward Scheduling Pro. The legacy offering's history in online scheduling and human Live Services does not establish the ownership, capabilities, integrations, security, or customer record of the product at myscheduleengine.com. The shared name is not evidence of a relationship.

The new Schedule Engine should therefore be judged on its own promise: “Run your service business from one command center.” That is an attractive proposition for a contractor tired of moving between scheduling, messaging, accounting, and marketing tools. The rest of the evaluation is about how much of that connected experience is available and production-ready in the account a buyer can purchase today.

The advertised command center

Schedule Engine is positioned as an all-in-one field-service-management system, not merely a receptionist. Its advertised workflow begins with a customer request and continues through the office and field operation:

• Quotes, online booking, scheduling, and dispatch organize new work.
• Customer records, two-way text and email, appointment confirmations, reminders, and “on my way” messages keep the conversation attached to the job.
• Invoices, payments, receipts, expenses, time tracking, and staff payouts carry the work into financial administration.
• Recurring-job automation, review requests, reports, marketing, and growth workflows extend the relationship after the appointment.
• iMessage, WhatsApp, SMS, and website chat are shown as additional customer conversation channels.

There is real appeal in that scope. If one system can reliably connect the customer, job, schedule, technician, conversation, and payment record, a service business can reduce duplicate entry and give office staff a more complete view of the day. Schedule Engine's advertised AI Employee would add a natural language control layer for actions such as booking work, following up, pursuing unpaid invoices, requesting reviews, and rebooking customers.

The website does not yet explain the operating structure behind that breadth in comparable detail. Role permissions, audit controls, migration, onboarding, implementation services, support hours, response targets, uptime commitments, and service status are not defined publicly. The advertised 14-day Starter trial and Max-plan “priority support” provide ways into the product, but they do not by themselves define a production rollout.

Calls, booking, and dispatch

The AI Receptionist is the bridge between Schedule Engine's broad platform story and a contractor's daily revenue workflow. The site says it can answer calls, filter spam, gather the caller's name, contact details, address, requested service, date, and time, then create or update the customer record and send confirmations and reminders. In the intended flow, a live conversation becomes a scheduled job without office staff rekeying the information.

That flow is worth testing as a single chain. Good call handling is not enough if the appointment lands in the wrong window; a correct booking is not enough if dispatch cannot see the update; and an accurate dispatch record is not enough if the caller receives a contradictory confirmation. Availability rules, service areas, job duration, technician skills, capacity, existing-customer matching, duplicates, reschedules, cancellations, and emergency escalation all determine whether the all-in-one promise holds under real operating pressure.

The public site does not describe its phone provider or number-provisioning process. It also leaves forwarding and porting, simultaneous-call capacity, languages, recording, transfers, human fallback, after-hours escalation, and emergency handling unspecified. Those are not reasons to dismiss the product; they are the details that turn the advertised workflow into a deployable call and dispatch operation.

AI Employee and AI Receptionist availability

The same product page currently communicates three different maturity signals:

1. A prominent message says “AI Employee Comming Soon” [sic].
2. Another section describes the AI Receptionist as if it can already answer, collect job information, create or update records, and send confirmations.
3. The Max plan lists AI Receptionist as included, offers a trial action, and shows dashboard imagery with calls and active workflows.

The contradiction is straightforward: the site markets a working outcome while also labeling the underlying AI Employee as coming soon. Neither a pricing-card inclusion nor dashboard imagery establishes general availability. Until the vendor demonstrates an outside call, a completed booking, the corresponding customer and dispatch records, and the follow-up message in a live buyer-accessible tenant, treat both AI products as availability to confirm rather than capability to assume.

This qualification still gives the concept fair credit. An AI layer that can act across the native schedule, customer record, communications, invoice, and review workflow could be more useful than a disconnected answering agent. The decisive evidence is an end-to-end action in the purchased environment, plus written confirmation of which functions are generally available on day one and which remain planned.

Integration logos need a live test

Schedule Engine displays logos for QuickBooks, Gmail, Stripe, WhatsApp, iMessage, Google Calendar, Twilio, Slack, Google, Zapier, HubSpot, Mailchimp, Xero, Intercom, Notion, and Square. That range reinforces the all-in-one vision, but a logo does not reveal whether a connector is live, what records it reads or writes, which system owns each field, how often it syncs, or what happens after a failure.

QuickBooks illustrates the need for precision. One feature section marks it “SOON,” while the Max plan presents it as included. A production evaluation should connect a buyer-controlled test company, create and modify a record on both sides, introduce a conflict, disconnect and reconnect the integration, and inspect the resulting logs. Use the same pattern for calendars, payments, messaging, and any other connector required for launch.

No ServiceTitan integration is shown for the product at myscheduleengine.com. The new platform cannot inherit one from the unrelated ServiceTitan-owned legacy product simply because they share a name.

Advertised pricing and open costs

The website presents simple monthly plan cards:

| Plan | Displayed price | Advertised scope | | ------- | --------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------- | | Starter | $39 per month | Up to three users, core scheduling, quotes, invoicing and payments, booking page, reminders, inbox, time and expense tracking, reports, and a 14-day trial | | Pro | $99 and $79 per month shown | Up to ten users and 150 AI actions per month; the promotional or strike-through styling does not explain the lower price's duration or eligibility | | Max | $199 per month | Unlimited users, an “unlimited” AI Employee, AI Receptionist, priority support, QuickBooks, and growth and marketing features |

The app terms describe a 14-day trial, web and Apple billing, automatic renewal, cancellation, and refund handling. The plan cards do not identify the currency or resolve taxes, payment-processing costs, phone minutes, messaging, carrier and number fees, setup, migration, or training. They also do not define an AI action, overage treatment, throttling, or the fair-use boundary around “unlimited.”

The useful comparison is therefore an all-in launch and operating cost, not the headline subscription alone. A final order should tie the displayed plan to the purchase channel, discount period, included usage, overages, implementation, renewal, cancellation, and every production feature demonstrated during the sales process.

Company, security, and customer proof

The app privacy policy names Supabase, Render, OpenAI, Resend, Sentry, Twilio, RevenueCat, and Apple as providers. It also describes encryption, access controls, backups, and purpose-based retention. Those are useful baseline disclosures. The policy does not provide firm retention periods or evidence of security certifications, while the app terms say they were written for App Review and should receive legal review.

The public materials do not identify the contracting legal entity, address, governing law, headquarters, supported countries, billing currency, or carrier footprint. They also do not provide a named customer case study, a testimonial tied to a verifiable service operation, or deployed call and booking volumes. Percentages inside unnamed product mockups are interface illustrations, not customer outcomes. The legacy Schedule Engine's record under ServiceTitan cannot fill that proof gap for a different product.

Before production data enters the platform, the order form and supporting documents should name the contracting party and define data roles, locations, retention, deletion, backups, continuity, subprocessors, model providers, model-training policy, access logging, tenant separation, vulnerability testing, incident response, and breach notice. Call recording and transcription consent, messaging opt-outs, outbound-contact controls, payment-data scope, phone-number ownership, support, uptime, and termination assistance also belong in the operating agreement.

These are maturity signals to resolve, not proof of a specific failure. A vendor can close many of them with complete documents, named references, and a well-run technical validation. Until then, the available information supports the product vision more strongly than it supports a conclusion about production operating depth.

What to prove before signing

Run the evaluation in a live tenant, in this order, so each result becomes the input to the next step:

• Establish the commercial baseline. Identify the legal contracting entity, purchased plan, day-one AI features, supported country and currency, implementation scope, included usage, overages, phone and messaging charges, support commitments, data terms, renewal, and exit rights.
• Configure the real operating rules. Load buyer-controlled services, service areas, hours, job durations, availability, dispatch priorities, escalation paths, staff roles, and confirmation language; then verify who can change each rule and whether changes are logged.
• Place outside calls into a provisioned number. Use a new lead, returning customer, after-hours request, ambiguous job, spam call, urgent request, and unsupported service; verify disclosure, caller interruption, transfer, fallback, and transcript behavior.
• Complete the booking chain. Watch the receptionist collect the required fields, match or create the customer, offer only valid slots, book the job, update dispatch, and send a consistent confirmation. Then reschedule, cancel, create a conflict, and check duplicate prevention and the audit trail.
• Stress the operation. Run simultaneous calls, every required language, a failed transfer, a telephony interruption, and an application outage path. Measure response delay, accuracy, recovery, escalation ownership, and what the customer experiences.
• Exercise AI Employee actions. Trigger follow-up, an unpaid-invoice reminder, a review request, and rebooking; verify approvals, consent and opt-out handling, action counts, audit history, and reversal of a mistaken action.
• Validate each required integration with buyer-controlled accounts. Inspect authorization scopes, records in both directions, source-of-truth rules, timing, retries, duplicates, conflicts, disconnect behavior, and the support owner for a failed sync.
• Close the evidence loop. Export and delete a test customer, inspect what remains in backups, recordings, transcripts, connected systems, and model-provider systems, review named customer references, and attach every material sales commitment to the order or service description.

This sequence gives Schedule Engine the chance to prove its strongest claim: that the receptionist, command center, schedule, dispatch board, communications, payments, automation, and integrations behave as one system. It also prevents a polished dashboard from standing in for the operational evidence a buyer needs.

Where Broccoli is the clearer choice today

Schedule Engine is aiming at the service business's broader system of work. Broccoli is purpose-built around a different priority: converting home-services demand into booked and completed opportunity. It is an all-in-one lead-management platform for the trades and home services, spanning inbound and outbound voice and SMS, website chat, speed-to-lead, qualification, booking and dispatch, follow-up, QA and coaching, and multi-location reporting.

That connected scope matters when the operational problem is larger than answering a phone. A new digital lead can receive an immediate response; an inbound caller can be qualified and booked; an urgent job can enter a dispatch path; an open estimate or membership opportunity can receive follow-up; and managers can review conversation quality, coach CSRs, and compare performance across locations. Teams can evaluate the full lead-conversion loop without first asking one new platform to replace every scheduling, invoicing, payment, and staff-management function.

For a contractor that specifically wants a more established, purpose-built lead-conversion evaluation with supportable operating depth today, Broccoli is the clear choice. Schedule Engine remains an interesting option for teams exploring a new all-in-one FSM command center and prepared to prove its availability, integrations, and operating terms. The distinction gives Schedule Engine's broader ambition fair credit while making the current buying decision practical.

Bottom line

Schedule Engine at myscheduleengine.com offers an appealing idea: one system for the customer conversation, booking, dispatch, field work, payment, and AI-directed follow-up. Its advertised breadth is the reason to consider it. The present site, however, gives contradictory AI and QuickBooks availability cues and does not yet supply the company identity, operating commitments, security evidence, or customer proof needed to judge that vision as a mature production platform.

Put Schedule Engine on the shortlist if replacing several service-business tools with one command center is the goal and the vendor can pass the live sequence above. Choose Broccoli when the priority is a more established, trades-focused lead-management operation across inbound and outbound voice and SMS, website chat, speed-to-lead, qualification, booking and dispatch, follow-up, QA and coaching, and multi-location reporting. For that lead-conversion brief, Broccoli is the stronger choice today.

Book Demo to run your real calls, lead sources, booking rules, dispatch paths, follow-up workflows, quality standards, and location structure through Broccoli.

Sources

1. Schedule Engine product and pricing page — The substantive source for the new product profiled here.
2. Schedule Engine app terms — Trial, billing, renewal, cancellation, refund, account, and legal-document limitations.
3. Schedule Engine app privacy policy — Named providers, baseline safeguards, processing purposes, and nonspecific retention language.
4. ServiceTitan Schedule Engine documentation — Used only to distinguish ServiceTitan’s legacy product from myscheduleengine.com.
5. ServiceTitan Scheduling Pro — Identity and replacement-path context for the legacy ServiceTitan product only.
6. ServiceTitan products — ServiceTitan product-family context only; not support for new-product claims.
7. ServiceTitan Marketplace: legacy Schedule Engine — Identity disambiguation only.
8. Legacy Schedule Engine and RYNO page — Historical identity context only; unrelated to the claims on myscheduleengine.com.