RequestQuote Public Requests vs Teams Buyer Workflows
RequestQuote now has two clear modes: privacy-safe public intake for customers, and authenticated buyer workflows inside Microsoft Teams for organizations that manage approved suppliers.
A public customer and a facilities buyer are not asking for the same product. A homeowner may simply need to describe a repair and get matched privately. A buyer team may need supplier approval, routing policy, request ownership, and internal visibility. RequestQuote separates those needs instead of forcing one workflow to pretend it fits both.
Public RequestQuote is privacy-safe intake
The public RequestQuote surface is designed for customers who want to explain a job by voice or text without browsing a named public provider directory. It can capture the job description, area, photos, and preferred contact method, then match the request privately with providers.
- Customers start with the need, not a vendor spreadsheet.
- Public copy should emphasize privacy, relevance, and provider availability.
- Contact details are handled carefully and are not broadcast as public directory data.
- Providers still respond and quote through governed SendQuote workflows.
RequestQuote for Teams is buyer-side procurement
The Teams experience is for authenticated buyer organizations. It is not created from a public website form. A buyer organization uses the Teams app to manage its own request context, approved supplier lists, governed routing, and request tracking.
Approve suppliers
Keep supplier relationships governed by the buyer organization.
Route requests
Send work to approved suppliers first, then use fallback paths when needed.
Track status
Give buyer teams visibility without turning suppliers into a public directory.
Why this matters for public messaging
When these modes are blurred, the website can accidentally overpromise. Public RequestQuote should not claim that every customer is creating a buyer organization. Teams should not look like a generic consumer request form. The cleaner story is simpler and more truthful: public intake for customers, governed Teams procurement for buyer organizations.
How providers fit in
Providers use SendQuote to receive requests, build quotes, share them through supported channels, and track response status. Whether the request started from a provider-owned widget, public RequestQuote, or a Teams buyer workflow, provider-side quoting still stays human-confirmed.
Choose the right RequestQuote path
Use public RequestQuote for privacy-safe customer intake, and Teams for authenticated buyer organizations with approved supplier workflows.
Open RequestQuote