Business model

How Zwivio works

A single reference for assignment, fees, and how Zwivio differs from shared-lead marketplaces.

At a glance

Zwivio is a Wisconsin-built home service dispatch platform. Homeowner dispatch opens by service category and area once coverage is strong enough. Homeowner requests move through a governed assignment flow: coordinated routing and clear rules for when contact and responsibility transfer, not a shared-lead marketplace where the same inquiry is sold widely for service businesses to chase. Homeowners do not pay Zwivio to use the intake and coordination flow. Service businesses are charged only when a job is officially assigned to them under Zwivio's rules for that request type (including homeowner approval steps where those apply). Service businesses can join across home-service trades, configure services and coverage, and use Field Console while dispatch opens category by category.

Dispatch Network pricing and request availability vary by trade. Some service categories support Emergency, Urgent, Scheduled, and Quote requests, while others may support only the request types that fit the trade and current market coverage. Service-business onboarding may be open for a listed trade before homeowner intake is publicly opened for that same trade in every area.

Lifecycle at a glance

Homeowner request

Zwivio routes it

Offer accepted / approval if needed

Official assignment

Pro performs work

Homeowner approval may be required before assignment is finalZwivio coordinates dispatch; pros perform the work

What Zwivio is

Zwivio is software and operations that together coordinate how service requests are verified, routed, offered, and, when rules are satisfied, assigned within a network of eligible service businesses. For Emergency, Urgent, and Scheduled work, the product uses assignment-first dispatch-style routing: outreach is governed (including rounds or batches depending on configuration and conditions), not a public directory free-for-all, and homeowner contact for those job types is released in line with assignment policy, typically to the pro who is officially assigned, not to everyone who saw an offer.

Status, timing, and handoff updates reach homeowners and service businesses through text and in-product messaging. Many service-business actions can be handled by text once onboarded; the same operational model favors clear, documented state over informal phone tag.

What Zwivio is not

  • Not a shared-lead marketplace that treats every request as a list to sell in parallel to many buyers.
  • Not a service directory whose primary job is browsing, rankings-for-hire, or selling raw contact access.
  • Not the service company that performs repairs or installations in your home. Zwivio coordinates the dispatch layer; licensed contractors perform the work.

Does Zwivio provide exclusive leads?

Yes — but Zwivio is not a traditional lead seller.

Zwivio provides exclusive dispatch opportunities for home service businesses, not shared leads. We do not sell the same homeowner's contact information broadly to multiple service businesses. For Emergency, Urgent, and Scheduled requests, Zwivio routes toward one official assignment under governed rules. Many offers use a time-bound exclusive response window where one eligible service business is first in line before routing may continue.

Service businesses do not pay to receive, view, decline, ignore, or miss an offer. A Zwivio Dispatch platform fee applies only when the job is officially assigned under the rules for that request type.

Quote requests work differently because the homeowner is asking to compare options. In that flow, service businesses may express interest at no cost, and a fee applies only when the homeowner explicitly approves a connection.

Why this model exists

Shared-lead marketplaces optimize for volume and simultaneous competition. That often produces noisy homeowner experiences and service-business spend that does not track cleanly to assigned work. Zwivio is built around the opposite pairing: fewer simultaneous parties on a given dispatch-style request, routing that respects eligibility and history, and platform revenue that aligns with official assignment, not with merely competing for the same lead.

How the business model works

Homeowners do not pay Zwivio platform fees to submit a request or follow status through the product. On the service-business side, Zwivio charges platform fees on official assignment for applicable job types, meaning the job is locked to the service business under the product rules for that path, not merely offered or tentatively accepted while approval is still open.

Dollar amounts by request type are not published anonymously. Service businesses who complete verification can review the current schedule in the product; this page stays at the level of when a fee applies, not how much.

Homeowner flow (high level)

You describe the problem and service area, complete verification (including confirming your phone), and submit. Zwivio then runs guided dispatch toward qualified pros. What you see next (timing proposals, approval prompts, text updates) depends on whether you chose Emergency, Urgent, Scheduled, or Quote, and on your dispatch preferences where the product offers them.

Submit and verify

Your request enters the system with enough signal for routing and fraud reduction; verification keeps the channel usable for real emergencies and scheduled work alike.

Governed routing

Eligible service businesses are contacted through a structured flow (including rounds or batches as configured). There is no promise of a fixed offer order, fixed response time, or that the first person to tap “accept” automatically wins the job.

Toward assignment

A pro may accept with proposed timing. When the product requires homeowner confirmation, especially if timing drifts outside the window you chose, assignment stays open until you confirm. Until assignment is finalized under those rules, the job is not in a final assigned state for fee purposes.

Updates

You receive operational messages about routing, approvals, assignment, and trip status as the product rules allow for your job type.

Service business flow (high level)

When you are routable for a request, you may receive a time-bound offer with the context needed to decide. You respond in the channel the job uses (often text). Accepting may include proposed service timing, but the assignment is not final until any required homeowner approval or confirmation is complete. The network tracks outcomes for routing quality, but this page only states the business boundary: fees follow official assignment, not curiosity or partial progress.

Offer

You decide with enough detail to know whether you can run the job; the window is time-bound so homeowners are not left waiting indefinitely.

Accept or decline

Declining, timing out, or losing the assignment path does not move you into a billed assignment. No charge is triggered simply because an offer arrived.

Official assignment

Applicable platform fees attach when the job is officially assigned under Zwivio's rules for that request type, after any required homeowner approval and other product gates for that path.

When service businesses are charged

The durable rule is simple to state and worth repeating: Zwivio charges service businesses only when a job is officially assigned to them under the rules for that job type. The details below explain how that rule applies in different situations.

  • Receiving an offer is not a charge event. A text or in-app offer is an invitation to respond, not a billable assignment.
  • Accepting or expressing interest alone is not a charge event when assignment is still subject to homeowner approval, timing confirmation, or other product gates. Until those are satisfied, the job is not in a final assigned state for platform fee purposes on dispatch-style paths described here.
  • If homeowner approval is still pending, assignment is not yet final for those flows, and a platform dispatch fee does not apply on that basis alone.
  • When the product records official assignment, applicable fees follow the published schedule for verified service businesses (including any quote-specific rules where quotes differ).

Zwivio does not publicly guarantee routing outcomes, offer order, or that every request becomes an assignment on a fixed clock. Fees follow the official assignment status recorded in Zwivio.

How quote requests differ

Emergency, Urgent, and Scheduled requests use the dispatch-style path summarized above: governed outreach, assignment-first contact release aligned with policy, and fees keyed to official assignment where that model applies. Quote requests intentionally follow a different shape. Multiple service businesses may express interest; homeowners review candidates and explicitly choose who may proceed. Contact details flow only to service businesses the homeowner approves in that quote flow, and fee rules for quotes are described separately for verified service businesses because the milestones differ from a single dispatch-style assignment.

Quote requests follow a different process from Emergency, Urgent, and Scheduled requests. The page you are reading applies the shared vocabulary (assignment, approval, fees) to both paths, but it does not claim the steps are identical.

How Zwivio differs from shared-lead marketplaces

The contrast is structural, not personal: two different ways to match supply and demand. Here is a quick side-by-side comparison.

Typical shared-lead pattern

  • The same homeowner request is often sold to multiple service businesses at once.
  • Service businesses pay to enter a race for the same job; spend accrues even when they do not win the work.
  • Homeowners may get a burst of competing outreach instead of a single coordinated path.

Zwivio's approach

  • Not a browse-first service directory and not pay-to-chase access to homeowner contact for dispatch-style jobs.
  • Governed routing and assignment: outreach is structured, time-bound, and eligibility-aware, not a broad blast list.
  • Service-business platform fees are tied to official assignment under Zwivio's rules, not to merely seeing or responding to an offer.
  • Designed to reduce homeowner spam and service-business "lead chasing" for the same instant request.

When routing changes, slows, or needs escalation

Dispatch runs in software with policy and human oversight. Behavior varies by job type, market configuration, time of day, and pro availability. Zwivio does not publish a guarantee of offer order, response time, or that the first pro to respond becomes assigned.

  • If automation does not yield an assignment, the platform may widen or retry outreach subject to policy; operations workflows may take over where configured.
  • If proposed timing no longer fits what you asked for, the product may require explicit homeowner confirmation before finalizing.
  • If an assigned pro cancels or cannot complete, Zwivio may restart routing so the request can match again, with updates where the product supports them.

How offer priority is shaped

Zwivio does not treat every service business the same at every moment. Offer priority is shaped by practical dispatch factors such as readiness, location fit, service-window fit, and reliability over time. The goal is not to create a fastest-click race. The goal is to route work toward qualified pros who are realistically positioned to respond well and complete the job.

Location matters because dispatch quality is not only about who wants the work. It is also about who can reach it sensibly. When service businesses share current location or service-area context through the product, Zwivio can reduce unrealistic offers, limit wasted windshield time, and improve the odds that a homeowner is matched with someone who can actually run the request well.

Offers may also show estimated drive time and miles before acceptance, giving service businesses practical route context without turning the request into a shared-lead race.

Reliability matters because routing should reward follow-through, not just availability claims. Prompt responses, honoring commitments, accurate On-Call use, and strong completion patterns can improve how soon a service business is considered for suitable work over time.

Zwivio also tries to balance the playing field when multiple qualified service businesses are good fits for the same request. When appropriate, the platform may avoid routing every suitable job to the same service business. The goal is to support homeowner outcomes, realistic dispatching, and network fairness without turning routing into a public race.

This page intentionally explains the principles, not the internal scoring formula. Routing logic is governed in product and may evolve with configuration, market conditions, and operational learning. The durable point for service businesses is simpler: offers are shaped by fit, readiness, and trust earned over time, not by broad lead resale or pay-to-chase competition.

Roles and responsibilities

Zwivio coordinates routing, enforces service-business verification and eligibility standards for participation, runs the assignment flow in product, and delivers status communication (text and in-app) within the rules of each job type. Zwivio may facilitate contact or escalation when something breaks down, but it is not the technician on site.

The service business performs the work, diagnoses and recommends service, and sets service pricing and payment terms with the homeowner. The service relationship for the actual repair or install is between the homeowner and the service business; Zwivio is not a substitute for that relationship and does not perform the physical service.

The homeowner provides accurate request information, responds to verification and approval prompts when required, and communicates directly with the assigned pro for on-site service questions and billing for work performed.

Wisconsin focus

Zwivio is built and operated in Wisconsin, currently centered on Southeast Wisconsin. The counties currently open to homeowner requests are listed on our Wisconsin service areas page. Surrounding geography expands as network density and operations allow. Availability may still vary by trade, location, request type, and time.

Related pages

This page is meant to stand alone. Optional next steps:

ServicePros