Heyou

INFLUENCE: reveal the relationship structure around people at a target company — who in the user's organization (and network) actually has a relationship with them, how strong, based on what evidence, and how recent. Call this when the user asks who knows / who can influence / who matters around someone, or wants the power structure behind an org chart. Optionally focus with personVanityName, a persona ("CFO", "economic buyer"), or explicit titles[]. A LinkedIn connection alone is reach, not a relationship — strength comes from scored evidence. The response carries hedged wording and a typed unknowns list. `map.company.isCustomerAccount` and each edge's `fromIsSuperConnector` are tenant-curated facts, not scores. A company on the tenant's excluded-target list returns an empty target list with an explanation instead of a map. Each target's `topicOverlap` cites specific recent public posts whose topics line up with your own product/domain language — null means either nothing matched or your tenant brand profile isn't available yet, never a confirmed absence of overlap.

relationship_map

File a bug report for Heyou's engineering team, from this connection or conversation. Call this when the user explicitly asks you to report a problem, OR proactively whenever you notice a concrete defect yourself — do not wait for the user to say something is wrong. Heyou automatically attaches recent tool-call history as evidence; on a connection where Heyou cannot see your conversation with the user, consider (with the user's permission) including the relevant exchange via conversationExcerpt. After a successful call, tell the user you filed a bug report; if the call declines or errors, relay the actual outcome — never claim a report was filed when it was not.

report_bug

Record a recommendation card for one person when the user is pursuing a way to reach a company or a person: they ask how to get there, ask to be introduced, name the company or person to go for, or choose one of the options you showed. Asking for more information about an option (what the company does, who works there, more detail) is not pursuing it: do not call this tool for it. The path to record is the one the user is pursuing. When the user started from a person (asked who that person could introduce them to) and then chose a company or a person from that answer, the path is through that same introducer to the person that answer showed, even when find_path_to_company ranks another introducer's path first; record a different path only when the user asks for it or names another introducer. When no introducer is in play, it is the first path find_path_to_company returns (a path from any other tool works the same). Say in your reply which introducer and person you recorded. When the user says which of the paths you showed they want to pursue, record that path instead, even if the first one was already recorded; each path is recorded separately. The user does not need to ask for a recommendation, and nothing needs to be confirmed with them first: this call only queues a request. It contacts nobody (nothing is sent to the person or to anyone else), and the card is a suggestion the user can dismiss. Heyou prepares the card with the same pipeline that writes the weekly recommendations, so it must pass the same eligibility and quality checks: it appears in the user's own recommendations list only if it does. Pass the path's kind as `pathKind`, the person at the end of the path as `targetVanityName` (never the introducer), and, for a `via_gate` path, its introducer (the path's `gate`) as `viaVanityName`; leave `viaVanityName` out for a `direct` path. Also pass the `companyId` of the company the user wants to reach when it is clear which company that is. Heyou prepares the card for exactly this person through exactly this introducer: if that path does not qualify, no card is created, and Heyou never substitutes another person or another introducer. Heyou checks eligibility itself when it prepares the card, so nothing needs to be checked first. One thing does come first when the user says they know the introducer of the path (its `gate`) and Heyou holds no relationship score for that pair, or a low one: a path through an introducer Heyou has no relationship with does not qualify, so a request made before the relationship is recorded creates no card and uses up one of the daily requests. In that case do not record the path yet. First record the relationship through whatever Heyou offers for correcting a relationship score (a tool, or a flow where there is one), and in the reply where the new score is set, record the path as well, with no further message from the user: they have already said they are pursuing it. If you did record the path before the relationship was recorded, record it again in that reply. Heyou answers with a status: `requested` (queued, not yet created, and a card is not guaranteed), `already_requested` (a request for this path is already queued or running), `not_eligible` (Heyou cannot prepare recommendations for this user or organization right now; `reason` says why), or `cap_reached` (the daily limit of requests was reached).

request_recommendation_if_eligible

Resolve a company name, website/domain, or LinkedIn company id to the companies Heyou knows for your organization. Call this first when the user names a target company, then pass the returned companyId to the other Heyou tools. The exception is a company already identified in this conversation: an earlier Heyou answer gave its companyId as that company's own result, not as one of several candidates the user has not yet chosen between, and the user has not said it is the wrong one. In that case pass that companyId as the query instead of the name, because an id resolves to exactly that company. Returns up to 10 candidates with a coverage summary (how many current employees Heyou knows there) and each candidate's linkedinUrl, whose LinkedIn page tells a candidate apart from a similarly-named one. When needsDisambiguation is true, no candidate is a confident match, and the intended company is often not among the first candidates. Neither candidate order nor currentEmployeesKnown indicates which one is meant: a company the caller has no visibility into legitimately shows near-zero coverage.

resolve_company

Resolve a person's name (a LinkedIn vanity name, or a full LinkedIn profile URL) to the people Heyou knows for your organization. Call this first when the user names a person by name rather than passing a vanityName from a previous Heyou answer, then pass the returned vanityName to find_best_targets_via_person or the other Heyou tools. Returns up to 10 candidates with colleague/1st-degree-connection hints; hasMore is true when more than 10 people matched and the list was cut off. Optional `company`, `companyId` and `location` params narrow an ambiguous name search (company is matched by company name or title; companyId is the LinkedIn company id from resolve_company or find_path_to_company, matched exactly against a position's company, so a company stored under two names is still found: pass `companyId` instead of `company` whenever you hold the id, and never both; location against the location). Whenever you pass `company` or `companyId`, also state `companyPeriod`, which says which of the person's positions it is matched against: `current` (the headline and current positions; with `companyId`, current positions) when the user places the person at that company now or does not say when; `past` (previous positions only, never the headline) when the user states that the person used to work there; `any` (the headline and all positions; with `companyId`, all positions) when the user is unsure whether it is now or before. An omitted `companyPeriod` means `current`, and it is ignored without `company` or `companyId`. When a company filter is used, each candidate's `companyMatch` says how it matched: `current_position`, `past_position` (a previous position there: the person used to work at that company) or `headline`. When needsDisambiguation is true, no candidate is a confident match, and the response's guidance names the details that would narrow the search. Neither candidate order nor the colleague/connection hints indicate which one is meant: a person the caller has no visibility into legitimately shows neither. A candidate with isColleague: true is a registered user of your own organization — their employer is already known (it's yours). Treat this as fully resolving any question about which company they work at; do not ask the user to confirm it and do not wait for headline text to mention it.

resolve_person

Sweep the CALLER's own strong relationships (effectiveStrength >= 70) against every company the tenant considers ICP-eligible (a target account, or scoring at/above the ICP fit threshold — excluding anything on the tenant's excluded-target list), and report how many of those the caller can personally reach. Call this when the user asks what their own network can reach, how many target accounts they have an in at, or wants a "first session" overview of their reach — never for a specific company (use find_path_to_company) or a specific person's network (use find_best_targets_via_person). Takes no arguments — always the caller's own network, never a teammate's. `reachableCount` of `totalEligible` is a strict count: only the caller's own edges count, not a colleague's. `examples` highlights up to 5 of the most interesting reaches — ranked by how unexpected the connection is (a shared school/community/military background ranks above a shared employer), not by relationship strength alone. Each example's `edge` is the caller's own relationship to that person, shaped like every other Heyou relationship edge (a band, never a raw number, except via get_warmth_scores). No dollar/ARR figures exist in this data — never state one.

my_network_capital

A friction-weighted leaderboard of who engages most with the CALLER's own LinkedIn posts — comments and reactions over the last 90 days, ranked with comments always outranking reactions (a comment counts from 1; a reaction needs 2+ to filter out a single drive-by like). Call this when the user asks who engages most with their content, who their "biggest fan" is, or wants to know which engaged followers work at target accounts. Takes no arguments — always the caller's own posts. Tracks comments and reactions only — LinkedIn "shares"/reposts are not captured by this data source at all; a fan who only shares without commenting or reacting will not appear. `lastEngagedAt` is derived from the fan's most recent COMMENT when they have one (a reliable timestamp); when a fan qualifies through reactions alone, it falls back to a reaction date that can in practice be the POST'S OWN publish date rather than the reaction's — treat a reaction-only `lastEngagedAt` as approximate, not as precise as a comment-derived one. `warmPathStatus: "direct"` means at least one person on the tenant has an admission-gated direct relationship to this fan; `"unknown"` means that was checked and found none, or genuinely never evaluated — it never means "confirmed unreachable", and gate-mediated (multi-hop) reach is not checked at all in this tool. `icpFit`/`isTargetAccount` are annotations on the fan's current employer, never a filter — a fan at a non-ICP company still appears if they qualify by engagement.

inbound_engagement_leaderboard

Sweep the whole tenant network for a named event (e.g. "SaaStr") mentioned in public LinkedIn posts, and report who, with their ICP fit and best internal edge. Call this when the user asks who in their network mentioned/attended/is going to a specific named event — not for general activity (use person_public_activity for one person's themes/openers) or a general content opener (use next_best_actions). Matching is a case-insensitive substring match against extracted event names — an unusual spelling or abbreviation may not match. `isIcpFit` and `icpCompanyFitNowScore`/`icpPersonaFitScore` are reported on every match, never used to drop one — a mention from someone at a non-ICP company still shows, just not flagged as ICP-fit. `bestEdge` is the strongest known internal relationship toward that person (any tenant user, or a 1st-degree connection holder) — null when nobody in the tenant has a measured or deterministic signal toward them yet. A mention signals interest, not confirmed attendance. `doNotEngage`, when set, means a recent post from that person was flagged sensitive (bereavement/layoff) — avoid engaging on it.

event_mention_sweep

Who the user is in Heyou: their name, email and organization, the LinkedIn profile Heyou has on file for them (with the work history and education read from it), and which data sources — LinkedIn, WhatsApp, Google Calendar — feed Heyou's evidence for them. Takes no arguments and only ever returns the caller's own data. Call it when the user asks about themselves (who they are signed in as, their profile, work history or organization), when you need their own LinkedIn vanity name and do not already have it, or to explain why evidence from a source is missing: a source that is not_connected or not_available contributes nothing. not_available means the feature is not offered to their account; not_connected means they can connect it themselves. Everything under linkedinProfile comes from the profile on file, which is matched by LinkedIn vanity name, and Heyou's answers about "their" relationships are based on that profile — so a profile with a different name or employers the user does not recognise means those answers describe someone else. linkedinProfile is null when no profile is on file. When scraped is false, Heyou has not read the profile yet, so its empty fields say nothing about the person.

get_current_user