IMPLEMENTATION GUIDE
Define the program’s requirements
List the industries, operating scale, and headquarters regions relevant to your program. Use company description as context for a reviewer rather than proof of a specific capability. Certifications, service coverage, customer references, and delivery capacity need evidence from your application and partnership process.
Keep enrichment beside application answers
Store the original application and enriched fields separately. Headquarters does not establish every region a partner serves, and employee count does not establish the number of specialists available for your product. Use differences between an application and a profile as questions for review rather than automatic rejection criteria.
Build a review queue your team can inspect
Match the completed task to the application ID, then attach the fields and rule evaluation to the review record. Mark missing data as unresolved and retain reviewer decisions across refreshes. Your partnership system controls acceptance and follow-up; enrichment provides consistent business context.
Connect the workflow
Use the API overview for request and task handling, or the Loop guide for webhook delivery.
Company enrichmentReview available company identity, size, and location fields.Common questions
Does company enrichment verify a partner’s certifications?
No. Use company fields to understand business context. Verify certifications, references, and delivery capabilities through your partnership process.
Does headquarters identify the markets a partner serves?
Headquarters identifies the company’s returned headquarters location. Ask the partner about service coverage rather than assuming it from that location.