Quixo has two request paths on purpose. The preferred path for a provider's own website is direct routing through the widget. The marketplace path exists for public funnels, shared channels, and community-style demand capture where one request should be visible to multiple matching providers over time.
Direct routing vs marketplace routing
Direct routing
Best for provider-owned websites.
- Request routes to one intended business
- Used by the tenant-scoped widget
- Preferred public growth motion for Quixo today
Marketplace routing
Best for public or community demand capture.
- Request becomes visible to matching providers in stages
- Designed for fairness and response speed
- Used when one request should not belong to a single provider upfront
That distinction matters commercially too. Requests that start on your own website are your direct customer path. Marketplace economics apply to marketplace-sourced jobs, not to leads that originated on your own provider-owned entry point.
The 3 visibility tiers
Marketplace-distributed requests do not go to everyone at the same moment. Quixo stages visibility so premium integrations can respond first, then opens the request wider if it still needs quotes.
Tier 1 • 0 to 15 minutes
Webhook subscribers
Matching providers with active webhook or premium notification paths get the first shot at the request.
Tier 2 • 15 minutes to 1 hour
Authenticated provider marketplace
The request becomes visible inside the provider-side marketplace and incoming requests views so logged-in providers can browse and quote.
Tier 3 • 1 hour onward
Social and broader distribution
If the request still needs responses, Quixo can push visibility further into wider channels.
When a marketplace request closes
Marketplace requests are not left open forever. They close when one of the operational rules is reached:
- Five quotes have been received
- The customer accepts a quote
- Seven days pass without completion
- The customer cancels the request
- The job is marked as completed
Important context
The marketplace is an authenticated provider workflow. Quixo's current public strategy is not to expose a named public provider directory by default on RequestQuote. Public surfaces should emphasize anonymous availability and matching speed instead.
What providers see
Providers do not all see the same thing at the same time. The workflow depends on their visibility path:
- Webhook subscribers can receive immediate matched notifications.
- Logged-in providers can browse marketplace requests once the request reaches the marketplace tier.
- Unregistered providers generally only encounter the request when the broader distribution tier is used.
What customers see
Customers are not forced to think in tiers. They submit one request, receive a reference number, and follow the job through one tracking flow. They see progress, receive quotes, compare options, and accept the provider they want.
When to choose each model
Choose direct routing when:
- The lead came from your own website
- You want the customer to deal directly with your business
- You are replacing a contact form or request form on your site
Choose marketplace routing when:
- The request belongs to a public or shared demand funnel
- You want multiple matching providers to compete for the lead
- You are running a Quixo-owned or partner-owned intake surface
In short: your own website should usually use the direct widget. Public funnels should use marketplace routing when shared visibility is the point.
Want your own direct intake path?
Install the Quixo widget on your website so quote requests land on your business path first.
Read the Widget Guide