> ## Documentation Index > Fetch the complete documentation index at: https://docs.deepblocker.ai/llms.txt > Use this file to discover all available pages before exploring further. # Research a person before a call (OSINT) > Build a target exposure profile from public, professional sources, confirm the person, read the evidence, pick a suggested attack and launch a pre-filled campaign. The Research segment researches one person and their company from public, professional sources, then shows how exposed they are and what an attacker could use. The page is titled **Target research** and its heading is **Target Exposure Profile**. Every run needs a named authoriser, and a human confirms the person before anything is launched. > [!NOTE] > > Public sources only. Family, health, personal finances and home address are filtered out at collection. The profile records which categories were dropped. ## Before you start * The person's full name and company. An email address or LinkedIn URL improves certainty. * The name, email and reference of the person who authorised the research. * Research needs a search service that DeepBlocker switches on per deployment. Without it the page refuses with "No research provider configured". See [Troubleshooting](https://docs.deepblocker.ai/vishing/troubleshooting.md). ## Steps **1. Open Research** In the console, open **Red Team**, then **Research (OSINT)**. On the **Campaigns** page, **Research a target first** goes to the same place. On a contact, **Research this contact (OSINT)** opens a smaller form that links the result to that contact. Click **New research**. **2. Enter the person** | Field | Required | Note | | - | - | - | | **Full name** | Yes | | | **Company** | Yes | | | **Email (optional, improves certainty)** | No | | | **LinkedIn URL (optional, improves certainty)** | No | A profile address of the form `https://www.linkedin.com/in/` | | **Contact id (optional, seeds its memory)** | No | Links the profile to a person on your People list, so what is found briefs the caller | **3. Record the authorisation** Fill in **Authorized by (full name)**, **Authorizer email** and, if you have one, **Engagement / SOW / ticket reference (optional)**. Then tick: "I confirm I am authorized to run this research and have a lawful basis for it. Public professional context only. The Analyze and suggest attacks step sends the profile facts to an AI provider to infer a psychographic read; see the engagement DPIA." Click **Research target**. The page says "This can take up to a minute." **4. Confirm the person** The profile opens with **Identity certainty** as a percentage. At 70% or more it shows **Confident**. Below that the page says "Confirm this is the right person before using it." Read the profile, then click **This is the right person**. Nothing can be launched from an unconfirmed profile. **5. Read the profile** A short bio sits at the top. Three tabs follow. | Tab | What it shows | | - | - | | **Profile** | Four bars from 0 to 100: **Public professional data**, **Social footprint**, **Organisation intelligence**, **Recent-event exposure**. Under **Publicly discoverable**: headline, employer, domain, topics, email pattern, announcements, colleagues and the organisation's footprint, as found | | **Evidence & psychographics** | **Public writing and mentions** with links, **Recent context** with dates and sources, and a Big Five read with a confidence figure and caveats | | **Attacks** | The suggested attacks, below | The bars measure how much an attacker can learn. They never score anything sensitive. **6. Get suggested attacks** On the **Attacks** tab, under **What should the attack get them to do? (the objective)**, write the goal, for example "approve an MFA prompt". Click **Analyze & suggest attacks**. Each suggestion shows a title, the cover story, which facts it uses, a difficulty, why it fits this person, and an **Opener**. Click **Use this angle** to open a pre-filled autonomous campaign. **Or use the generic drafted scenario** offers **Use generic draft** instead. Both are disabled until the person is confirmed. **7. Launch the campaign** The new campaign opens as **Autonomous (AI-driven)** with the objective and opener filled in, and **Remember targets across campaigns** on so the caller reads the facts found here. You still pick the attacker, the number and the people, and record the authorisation. See [Run an autonomous campaign](https://docs.deepblocker.ai/vishing/campaigns/autonomous.md). ## Linking a profile to a person **Link to a contact** attaches the profile to someone on your People list. The dialog says: "Attach this research to a contact so a campaign can use it. This replaces any profile already linked to that contact." **Create a contact from this profile** makes a new contact with the name and company filled in and links it at once. ## Past research and deletion **Past research** lists your profiles with the date and the certainty. Each has a link icon and a delete icon. Deleting cannot be undone. Every profile carries an expiry date 90 days after it is created. Automatic deletion at that date is not switched on yet, so delete a profile yourself when you no longer need it, or write to [contact@deepblocker.ai](mailto:contact@deepblocker.ai). ## Problems > [accordion] It says No research provider configured > > The search service is not switched on for your deployment. Write to us. See [Support and contact](https://docs.deepblocker.ai/support.md). > [accordion] It says Confirm this is the right person before choosing an attack angle > > Identity certainty is below 70%. Read the profile, then click **This is the right person**. > [accordion] It says Enter a LinkedIn profile URL > > The address must be a member profile, of the form `https://www.linkedin.com/in/`. A company page is not accepted. > [accordion] It says No recent public events found > > Nothing recent was found in public sources. The draft scenario is generic. Add context to the campaign before launching, or try with an email or LinkedIn URL. > [accordion] It says These suggestions are for a different target > > You opened another profile after generating suggestions. Click **Analyze & suggest attacks** again on the profile you want. This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.