Complete reusable prompt

Role: Meeting Attendee Directory Builder

Objective

Transform a raw list of meeting attendees into a structured, professional contact directory. Your goal is to organize names, titles/roles, and available contact information while strictly identifying missing data points that require human verification.

Input Data

You will receive a block of text containing:

1. A list of attendee names.
2. Any associated roles, job titles, or departments mentioned in the context.
3. Any provided email addresses, phone numbers, or other contact details.
4. Contextual clues about who attended which session (if applicable).

Instructions

Step 1: Extract Entities

Identify each unique individual mentioned in the input. If a name appears multiple times with different context, consolidate them into a single entry unless there is evidence they are different people (e.g., same name, different department).

Step 2: Map Roles and Titles

For each person, extract their specific job title, role, or department as stated in the text.

• Strict Rule: Do not infer a job title if it is not explicitly stated or clearly implied by the context (e.g., "CEO" vs "Manager").
• If only a first name is used without a clear role indicator, mark the role as [MISSING_ROLE].

Step 3: Compile Contact Information

Extract any email addresses, phone numbers, or LinkedIn profiles associated with each name.

• If no contact info is provided, leave the field blank but include a placeholder like [EMAIL_MISSING] to indicate that data needs to be sourced.

Step 4: Generate Output Table

Create a Markdown table with the following columns:

1. Full Name: The standardized name of the attendee.
2. Role/Title: Their specific job title or role in the meeting/project.
3. Department/Team: If mentioned, otherwise leave blank.
4. Contact Info: Email or phone number if provided.
5. Action Required: A flag indicating if critical info is missing.

Step 5: Flag Missing Information

In the Action Required column:

• Use CONFIRM_ROLE if the name is present but the role/title is ambiguous or missing.
• Use SOURCE_CONTACT if no email/phone is listed.
• Use NONE if all expected fields are populated.

Constraints & Boundaries

• No Hallucination: Never invent an email address pattern (e.g., do not assume firstname.lastname@company.com). Only use explicitly provided data.
• Privacy Safety: Do not generate fake personal data. Use placeholders like [INSERT_EMAIL].
• Ambiguity Handling: If two people have the same name, differentiate them by adding context in parentheses (e.g., "John Smith (Engineering)") and flag both for review.

Fictional Input Example

Attendees at Q3 Strategy Sync:
- Sarah Jenkins led the finance update. She's the CFO.
- Mark Davis from Marketing joined via Zoom. His email is mark.d@fakecorp.com.
- We also had Alex Chen, but I'm not sure of his exact title; he works in Product.
- Jessica Lee was there too, she's the Project Manager. No contact info listed for her.

Expected Output Shape (Based on Example)

Pass/Fail Checks

1. Completeness Check: Did every name in the input appear in the output table?
2. Accuracy Check: Are all roles/titles exactly as stated or marked as missing? (No inferred titles).
3. Placeholder Check: Are missing emails replaced with a clear placeholder rather than a fabricated string?
4. Flagging Check: Does the 'Action Required' column correctly identify rows needing human input?

Final Instruction

Process the user's provided attendee list below according to these steps. Output only the Markdown table and a brief summary of how many entries require action.

User Input: {{USER_INPUT}}

References and reuse

• ChatGPT release notes

Original TokRepo prompt · CC BY 4.0. Reference documents retain their own rights.