Logo

Company profile

Craft review for home-service operators

A practical guide to Craft’s AI CSR, lead-response, coaching, integration, pricing, and implementation fit for trades businesses.

Published by Broccoli Last reviewed August 11, 2026

What Craft covers

Home-services growth often creates a front-office problem before it creates a lead-generation problem. Calls arrive after hours, digital leads wait too long for a response, unbooked estimates go cold, and managers hear too few conversations to know why conversion is slipping. Adding volume to that system only creates more places for paid demand to leak.

Craft’s thesis is that those gaps belong in one connected operating layer. It is not positioned only as a virtual receptionist. Its product family includes an AI CSR for inbound calls, Text Agents for digital leads and missed calls, Speed to Lead, AI Follow-Up, Coaching & QA, and tools for recording and analyzing in-home sales conversations. Customer, job, appointment, and conversation data can move between Craft and CRM or field-service systems so that the next action starts with context rather than a blank screen.

That breadth is meaningful. A trades business can use the same product family to answer a new customer, book the work, re-engage an old opportunity, improve a CSR’s performance, and coach a salesperson in the home. Craft serves HVAC, plumbing, electrical, roofing, remodeling, flooring, painting, windows and doors, garage doors, pool service, and foundation repair, with a range that extends from growing owner-led companies to franchises and private-equity-backed groups.

The best way to understand Craft is as a modular AI front office. A company can start with its most expensive leak, but the larger promise is cumulative: faster response creates more conversations, better booking converts more of them, and QA and coaching help the team learn from what happens next.

How Craft connects the revenue journey
MomentCraft workflowBusiness result to measure
A customer calls24/7 AI CSR qualification, booking, and contextual transferAnswer rate, qualified booking rate, and bookable calls recovered after hours
A digital or missed-call lead arrivesText response across web, Meta, aggregator, form-fill, missed-call, email, and web-chat contextsTime to first response, contact rate, and appointments created
An opportunity does not convertVoice and SMS follow-up for aged leads, cancellations, unsold estimates, maintenance, and win-backsRe-engaged conversations, booked work, and completed revenue
A manager needs to improve performanceAutomatic notes, configurable scoring, alerts, coaching packets, and analyticsBehavior change, booking improvement, and coaching consistency
A salesperson meets the customer in the homeConversation recording and field-sales coachingClose rate, net sales per issued lead, and adoption by the sales team

How inbound booking works

Craft’s AI CSR answers around the clock, collects the service or project need, qualifies the opportunity, handles common objections, and books against live availability. Craft says the workflow can prioritize by lead value, urgency, representative availability, and market capacity. Once a time is selected, it can write the appointment to the connected calendar or CRM, send confirmations and reminders, reschedule, and update the customer record.

That is the core execution layer of the platform. A customer who calls during a busy afternoon or late at night does not have to wait for a callback, and the CSR team can reserve its attention for conversations that genuinely need a person. When human judgment is required, Craft can transfer the call with context rather than forcing the customer to begin again.

The value of that experience depends on how faithfully it follows the dispatch operation. A polished conversation that creates an impossible appointment is not a win. During rollout, teach Craft the company’s actual service areas, job types, emergency definitions, memberships, capacity rules, dispatch windows, and escalation paths. Then run the uncomfortable calls: a no-cool emergency near closing, an out-of-area customer, a warranty callback, a landlord arranging service for a tenant, a fully booked day, and a caller who changes the job type mid-conversation.

Follow each test through the transfer destination and system of record. The important outcome is not merely that the AI understood the words; it is that the right customer, job type, availability, notes, and disposition reached the team in a form dispatch can use.

Lead response beyond the phone

Craft’s front-office scope becomes more distinctive once the interaction moves beyond inbound voice. Text Agents can respond to web forms, Meta leads, aggregators, missed calls, email, and web chat. They can qualify, book, confirm, remind, reschedule, and re-engage, giving an operator a path from a new digital inquiry to a scheduled appointment without waiting for manual outreach.

For companies buying leads across several channels, this can be a direct conversion advantage. A prompt message reaches the homeowner while the need is still urgent and the shopping window is still open. It also lets the conversation continue asynchronously, which can be more convenient than repeated calls for both the customer and the contact center.

The same infrastructure supports revenue recovery. Craft describes outbound voice and SMS for unsold estimates, cancellations, maintenance reminders, seasonal offers, win-backs, nurture, and post-job “happy calls.” Those are not minor edge cases: many trades businesses already paid to acquire the customer or create the estimate. Consistent follow-up can turn neglected database demand into appointments without requiring the CSR team to work every list manually.

These workflows need clear customer-contact rules. Craft automatically honors text opt-outs such as STOP, while the customer controls lead-form consent language and remains the sender of record. Before launch, decide which lists may be contacted, how consent is retained, when quiet hours apply, how duplicates and suppression lists behave, and when a conversation moves to a person. If email matters to the intended workflow, confirm which email interactions and outbound actions are part of the proposed package.

Coaching, QA, and field sales

Craft does more than automate customer conversations; it also tries to improve the people having them. Its contact-center tools provide real-time guidance, automatic CRM notes, configurable call scoring, coaching packets, compliance alerts, performance tracking, and analytics. That gives a manager a wider view than listening to a small call sample and relying on anecdotal feedback.

The useful loop is simple: surface the missed opportunity, identify the behavior behind it, coach the CSR, and watch whether the behavior improves in later calls. Automatic scoring matters when it makes that loop faster and more consistent, not merely when it produces another dashboard. Agree on what counts as a qualified opportunity, a bookable call, and a successful handoff so the scorecard reflects the company’s real service model.

Craft carries that coaching model into the home. Its field-sales tools record and analyze in-home conversations so sales leaders can coach the interaction that happens after the appointment is issued. This is a genuine point of breadth for companies that want one improvement system across the contact center and field sales. Recording consent, device workflow, salesperson adoption, and attribution still need to be designed into the deployment.

Craft’s customer stories show how broad deployments can work. Express Flooring reported a 20% company-wide lift in close rate and 22% higher net sales per issued lead after using Craft across field sales, training, and follow-up. Handy Bros describes consolidating five AI vendors while using Craft across inbound voice, speed-to-lead, coaching, follow-up, and QA. These are company-specific results, not guarantees, but they demonstrate that Craft can extend well beyond a narrow answering use case.

Keep the internal measurement equally specific. Answer rate, booking rate, speed to first response, estimate recovery, CSR score, field close rate, and completed-job revenue each tell a different part of the story. Seeing them separately makes it easier to expand the parts of Craft that are earning their place.

Integrations and launch ownership

Craft lists more than 20 ready-made connections across CRM, field-service, and phone systems. Its directory includes ServiceTitan, Jobber, Housecall Pro, Salesforce, HubSpot, Zoho CRM, Microsoft Dynamics 365, AccuLynx, GoHighLevel, Workiz, and JobNimbus, alongside phone products such as RingCentral, Quo, Aircall, Five9, and NICE inContact. A bidirectional REST API extends the reach to appointments, recordings, summaries, extracted fields, CRM notes, customer and job context, and recording triggers.

That connector range is a real advantage for multi-brand groups and businesses whose revenue workflows span several systems. It creates the possibility of a common Craft layer without forcing every business unit onto the same software first. The proof, however, lives in the objects and actions—not the integration logo. Trace what Craft reads before a conversation, what it writes after, how quickly the data refreshes, and how timeouts, retries, and duplicate records are handled. If live booking is essential, have Craft show the availability source and appointment creation in the exact field-service system the team uses.

Craft describes a white-glove launch that includes discovery, configuration, custom training, and support, with a dedicated AI engineer for enterprise accounts. It says most teams are fully integrated in the first week. Treat that as a useful signal of launch velocity, then define what “integrated” needs to mean for the business: routing is correct, booking policy is encoded, records write cleanly, edge cases pass, managers can read the reporting, and staff know how to take over.

An internal launch owner remains important even with hands-on vendor support. Someone must approve routing and scheduling rules, supply realistic test calls, review CRM data, and decide when customer traffic is ready to move. The final plan should also make support hours, severity targets, monitoring, rollback, and the service level for the selected package easy to understand.

Price, contract, and data questions

Craft uses custom pricing, which is sensible for a platform that can span channels, modules, integrations, users, and locations. It also means the order form is part of the product decision. A useful proposal should make the intended deployment visible: the AI CSR and follow-up modules included, expected call and message volume, locations, coaching seats, integrations, phone numbers, API access, implementation work, support, and any overage rates.

Craft’s terms say fees are set in the order form and are generally non-refundable under the agreement. Subscriptions renew automatically unless written cancellation notice is sent at least 30 days before renewal, and termination is tied to the end of the applicable contract term. The standard initial term is not posted, so the signed documents should spell out the initial and renewal periods, notice method, price changes, implementation fees, and exit support.

Data handling deserves the same clarity because Craft may process calls, recordings, messages, customer details, and job context across the revenue journey. Craft says customer data is stored on U.S. servers and that customers retain ownership of their content, recordings, and data. Its terms permit the processing required to provide the service and the use of aggregated or anonymized information. The privacy policy says de-identified and aggregated data may be used to develop, train, and improve AI models. Craft also says data remains exportable for 30 days after termination before deletion, subject to the agreement and applicable requirements.

Craft’s site currently says a SOC 2 Type II audit is in progress. A security review should confirm the latest audit status along with subprocessors, access controls, retention by data type, incident procedures, and any required SSO or role-based permissions. The terms assign customers responsibility for telemarketing, TCPA, AI disclosure, SMS consent, and call-recording compliance, so counsel should review the actual call and messaging flows that will go live.

Where Craft fits in practice

Craft is most compelling when several revenue leaks share the same underlying problem: customer conversations and next actions are disconnected. A multi-location HVAC group can use inbound answering, digital-lead response, QA, and field coaching across the organization while preserving location-specific rules. A roofing company buying leads from several sources can pair rapid text response with identity matching and appointment attribution. A plumbing company can begin with after-hours qualification, booking, and emergency transfers, then add follow-up once the inbound rules are reliable.

The platform can also connect demand recovery with sales improvement. A remodeler with a backlog of unsold estimates might use automated outreach to restart conversations while coaching helps managers understand what happened in the original appointment. That is the benefit of Craft’s breadth: it can act on the opportunity and help the team learn from it inside the same product family.

Smaller operators can still benefit from the AI CSR, but they should decide how much of the wider platform they expect to use. If the urgent need is simply after-hours phone coverage, the larger return story may take time to develop. If the goal is to coordinate inbound calls, digital leads, follow-up, coaching, and field sales, Craft’s broader operating model becomes much more relevant.

How to evaluate Craft

The strongest Craft evaluation feels like a working session, not a feature tour. Start with the revenue leak that matters most and follow it to the final record. For inbound calls, use the company’s hardest booking, rescheduling, no-availability, emergency, and failed-transfer cases. For digital leads, watch source attribution, consent, duplicate handling, response speed, qualification, and the move from message to appointment. For recovery, load a controlled audience and measure booked and completed work rather than replies alone.

Then show the operating aftermath. A dispatcher should be able to recognize and honor the booking; a manager should be able to locate the conversation and coach from it; and reporting should separate inbound conversion, speed-to-lead, follow-up, QA, and field-sales outcomes. Run this against the exact integrations, locations, and package in the proposal so the demo represents the deployment being purchased.

The final decision should be tied to a short production pilot with baseline metrics and acceptance criteria. That gives Craft’s platform promise a fair test: not whether every module sounds useful, but whether the connected workflow makes the customer journey faster, the team more consistent, and the resulting revenue easier to attribute.

Where Broccoli fits: one trades-specific path from lead to booked job

Craft’s broad home-services front office is a genuine strength, especially for an organization that wants published connector breadth and field-sales conversation coaching alongside lead response. Broccoli takes a tighter operating position: it is an all-in-one trades and home-services lead-management platform built around turning demand into booked work.

Broccoli brings inbound and outbound voice and SMS, website chat, speed-to-lead, qualification, booking and dispatch, persistent follow-up, QA, coaching, and multi-location reporting into one cohesive flow. A web lead, missed call, estimate opportunity, or live caller can be worked toward the same operational outcome, with the trade’s real service areas, job types, capacity, escalation paths, and system-of-record requirements shaping the journey.

That cohesion makes Broccoli the clear choice when the priority is a purpose-built lead-to-booked-job operating platform rather than a wider revenue enablement footprint. The overlap with Craft is substantial, but Broccoli’s advantage is the hands-on fit of its voice, messaging, chat, booking, dispatch, follow-up, and performance workflows for trades teams. Operators do not have to choose between fast response and accountable execution: the same platform can carry the lead from first contact through qualification, scheduling, recovery, coaching, and location-level visibility.

Read the

Craft versus Broccoli comparison

for a direct view of the two approaches, then book a Broccoli demo to run your real call flows, booking rules, dispatch constraints, and follow-up journeys.

Making the decision

Choose Craft when the operating goal extends across a broad revenue organization: inbound AI CSR coverage, digital lead response, outbound voice and SMS, automated follow-up, contact-center QA, and coaching for sales conversations in the field. Its integration directory, API, and product range can be especially valuable to multi-system or multi-brand groups prepared to design the workflows and measurements that connect those functions.

Choose Broccoli when the main objective is to run home-services leads through one purpose-built path from first response to booked and dispatched work—and to keep follow-up, QA, coaching, and multi-location visibility attached to that path. For most trades operators evaluating an AI lead-management layer, that cohesion is the more decisive advantage and makes Broccoli the stronger final choice.

Whichever route the team tests, make the decision on real demand: the hardest call, the fastest-moving web lead, the awkward scheduling exception, the stale estimate worth recovering, and the completed job that can be traced back to the conversation. Craft offers impressive breadth. Broccoli offers the clearer lead-to-revenue operating system for the trades.

Book a Broccoli demo →

Sources

  1. Craft home pagePlatform positioning, buyer scope, channels, and product modules
  2. Craft AI CSRInbound answering, booking, transfers, and CRM synchronization
  3. Craft pricingCurrent custom-pricing entry point
  4. Craft demo and onboardingCurrent onboarding and launch positioning
  5. Craft Contact Center AIAgent guidance, notes, QA, transfers, and contact-center scope
  6. Craft Text AgentsLead sources, messaging, qualification, booking, campaigns, and opt-outs
  7. Craft integrationsNamed integrations, API scope, data sync, and implementation timing
  8. Craft Coaching & QAScoring, coaching, alerts, and contact-center analytics
  9. Craft customer storiesCustomer index and reported outcomes
  10. Craft Handy Bros case studyMulti-product deployment and vendor consolidation
  11. Craft Express Flooring case studyField-sales, training, follow-up, and customer-reported results
  12. Craft privacy policyRecordings, transcripts, data use, SMS, retention, and privacy rights
  13. Craft terms of serviceData, customer responsibilities, renewal, cancellation, and content rights
  14. Broccoli AI product overviewVoice, SMS, chat, ServiceTitan workflows, follow-up agents, QA, coaching, and enterprise reporting

See Broccoli in action

See how Broccoli handles your calls and booking rules.

Book Demo