Back to shopper help
MSP shopper guideRFP and AI assistance

How buyer consent and contact sharing work

Buyer consent protects your contact information during the RFP process. MSP Ranked can use your request details to evaluate fit, but contact delivery to MSPs should follow the consent choices presented in the workflow.

Guide summary

Your RFP can preview matches first; MSP delivery requires explicit permission to share contact details.

Why consent matters

Managed services buying often involves sensitive business context, so contact sharing should be deliberate.

  • Your request may include company details, technology needs, timing, and budget context.
  • MSP Ranked can review the request without automatically distributing it to every provider.
  • Explicit consent creates a clearer boundary for when providers may contact you.

How contact delivery should work

The RFP workflow separates request review from provider outreach.

  • Your submitted request can be assessed for service, location, and fit signals.
  • Eligible paid partners may be considered for routed delivery when the request matches their profile.
  • Buyer contact information should only be shared when the relevant consent is present.

How to stay in control

Use the RFP form and direct provider conversations to manage the level of detail you share.

  • Provide enough context for fit, but avoid unnecessary sensitive credentials or internal secrets.
  • Ask providers to confirm their scope, experience, and next steps before sharing deeper technical detail.
  • Use MSP Ranked profile pages to evaluate whether the provider should continue in your process.