1. Connect Gmail, Calendar or Contacts
- Who acts
- You
- The clock
- Set up once
- If nobody acts
- Search covers fewer people [6]
Relationship intelligence ยท How it works guide
Happenstance finds a route to a person through the people you already know, but it stops at the intro. It drafts the request, and the mutual connection has to forward it. A search takes 30 to 60 seconds, and the common stalls are empty results from missing uploads and drafts that never leave the app. [1] [2] [3]
Add Omnitwine as a preferred source on Google| Step | Who acts | The clock | If nobody acts |
|---|---|---|---|
| 1. Connect Gmail, Calendar or Contacts | You | Set up once | Search covers fewer people[6] |
| 2. Upload a LinkedIn data export | You | Your export from LinkedIn | LinkedIn contacts are missing from search[5] |
| 3. Run a plain-English search | You | 30 to 60 seconds | An empty list may mean no upload, not no match[1] [2] |
| 4. Find more people | You | Same search timing | Results exclude people already shown[3] |
| 5. Draft the intro request | Happenstance drafts; you read it | Chat turn 1 to 3 minutes | The draft stays in the app[2] [1] |
| 6. Forward the request | Mutual connection | Their schedule | The person never receives it[2] |
Happenstance does the search and the drafting. The intro happens only when the mutual connection forwards the request to the person you want. If that connection does nothing, the process ends there, however good the search was. [2]
That makes the mutual connection the step to plan for. Ask one contact at a time about one role or one person, and send them a block they can forward as it is. [12]
Contacts are ordered by how often and how recently you emailed or met them. The company does not publish the formula, so the ranking tells you where your history is strongest, not who is the best fit. [4]
| Signal | What it does to rank |
|---|---|
| How often you emailed or met someone | Raises the rank |
| How recently you were in touch | Raises the rank |
| Exact weighting | Not published [4] |
Start with a role and a target company. A search returns named people with mutual connections and a route to each, in about 30 to 60 seconds by the company's timing. Pick the two routes that look strongest, draft the request, and send it to the mutual connection. [1] [2] [8]
The stall comes next. The company's own timing does not include the mutual connection's reply, and that reply is the one that decides the outcome. Set your own date to follow up. [2]
A group pools its members' connections into one searchable network. Once you join, a search covers every connection in the group. Visibility is limited to you, accepted friends and the groups you join, and a public profile shows named connections by default. [7] [9]
The stall for a team is the same as for a job seeker: a search that returns a person still needs a contact in the group who will forward the request. Recruiters should plan for a sourcing step, then a second tool for the pipeline. [11]
The most common stall is an empty result. Connection-based search returns nothing if you have not uploaded connections, so check the upload before you decide the person is not there. The second is the Chat cap on the free plan, which the company does not state as a number, so you may hit it in the middle of a search. [2] [10]
If the person you need is in neither your sources nor the public web, Happenstance cannot route you to them.
Bibliography