Meet
Understand how Meet profiles, discovery, matching, contact requests, Events, and Messenger fit together.
Meet is Infra One’s account-scoped directory for discovering and contacting other signed-in people. It uses a personal profile rather than an organization workspace: you need a confirmed, authenticated account, but you do not need an organization membership or organization role.
Meet runs at meet.infra.one. Its current product flow is profile setup, profile discovery, contact requests, profile reports, and handoff to Messenger. Meet does not currently schedule or join meetings.
The Meet model
| Part | What it does |
|---|---|
| Your Meet profile | Stores the identity, professional context, and interest selections used by Meet. Each account owns one profile. |
| Completed profile | Makes discovery available after all three setup steps are saved. Incomplete profiles return to setup. |
| Discovery candidate | A different account’s completed profile that is not deleted and is not hidden by a block in either direction. |
| Match score | Compares the two profiles’ asset classes, investment focus, strategies, and LP types. |
| Direct chat | Holds the contact-request state and conversation in Messenger. Meet starts or opens this relationship; Messenger manages it. |
| Event attendance | Lets published Events contribute an event filter and, in supported Event guest lists, links to completed Meet profiles. Event managers can also see profile completion and invite eligible registered attendees to setup from Events administration. |
Meet profile setup saves three steps separately: investor type, profile details, then interests. Completing the interest step marks the profile complete and opens discovery. Read Set up your Meet profile for the exact fields and limits.
The Meet workspace is account-scoped; the Events attendee-invitation action is not. That action lives on an Event’s protected attendee-administration route and uses the Event’s organization-member or direct-manager permission, not the manager’s own Meet profile state.
What other people can see
Meet’s web cards show an avatar, name, job title, location, and up to five interest tags, followed by +N more when more remain. The profile panel can additionally show shared interests, other interests, a bio, and published Events recorded as accepted attendance.
The setup form also stores Company/Organization, Profession, Industry focus, and an optional LinkedIn URL. Some of those values drive sections or filters, but the current Meet web card and profile panel do not display the company or LinkedIn URL. Do not use a saved field as proof that Meet publishes it in the web interface.
Discovery sections
The main page divides eligible profiles into four sections:
- Top picks for you orders the candidate pool by match score and shows the score badge.
- Meet LPs includes profiles whose investor type is LP.
- Meet GPs includes profiles whose investor type is GP.
- From your industry includes profiles with the same industry focus as yours and is hidden when there are no results.
The first view shows up to four profiles per section. See all expands one section. Name search and filters narrow the same eligible candidate pool; they do not broaden profile visibility.
How matching works
Meet compares four interest categories: asset classes, investment focus, strategies, and LP types. Within each comparable category, the score is the number of shared selections divided by the number selected by either profile. Meet gives each comparable category equal weight, averages the category results, converts the result to a percentage, and rounds it.
A category is excluded only when both profiles have no selections in it. If none of the four categories is comparable, the match score is 0. The score is a similarity aid, not an access decision or an endorsement.
Contact and safety boundaries
Selecting Request to contact creates a pending direct chat, enqueues a deduplicated asynchronous push attempt, and redirects to that chat on Messenger. Push delivery is not guaranteed, and Meet does not create a message. Meet then shows Waiting for acceptance while the request is pending and Send message after it is accepted. Reporting a profile creates a separate content report for review; it does not hide or block the account, change the chat, or retract a contact request.
Meet has no block control. Blocks managed by the shared account and messaging layer apply in both directions: blocked accounts are removed from ordinary Meet discovery, and new direct contact and message writes between them are rejected. Read Meet permissions and states before relying on profile or Event visibility.
Start using Meet
Follow Set up your Meet profile, then use Discover and contact people in Meet. Event managers should use Manage an event for attendee invitations. If setup, discovery, contact state, Event context, or reporting does not behave as expected, open Troubleshoot Meet.