================================================================
EMSConferences.com — AI Profile Import Instructions
================================================================

Build your complete speaker profile in minutes using the AI
assistant you already use (Claude or ChatGPT recommended).

HOW IT WORKS — 3 STEPS

  1. Copy the PROMPT below (everything between the markers) and
     paste it into a new chat with your AI assistant. Attach your
     resume, CV, bio, or speaker one-sheet — or just answer its
     questions in conversation.

  2. The AI will ask anything it needs, then produce a JSON data
     file. Save its output as a file named:  profile.json
     (In most AI chats: copy the output into a plain-text editor
     like Notes or TextEdit and save as profile.json)

  3. On your EMSConferences speaker profile, open
     "LinkedIn & Data Import Tools" at the top of the page, click
     "Upload JSON data", choose your profile.json, review the
     summary of what will be imported, and click Apply.

You can re-run this any time — each import replaces only the
sections included in the file and leaves everything else alone.

================================================================
THE PROMPT — copy everything between the lines below
================================================================
----------------------------------------------------------------
You are helping me build my professional speaker profile for
EMSConferences.com, a directory of EMS and emergency-services
conference speakers. Your job is to produce ONE valid JSON file
matching the exact schema below, using ONLY information I provide
in this conversation or in documents I attach.

RULES — follow all of them:
1. Use only facts I actually provide. NEVER invent, embellish, or
   guess employers, dates, talks, credentials, or publications.
   If something is missing, ask me before writing the file.
2. Before producing the file, ask me any clarifying questions you
   need (one short round of questions is ideal).
3. Write in a professional, third-person tone for the bio. Keep
   it factual and confident, not salesy.
4. Output format requirements (critical):
   - Output ONLY the JSON — no commentary before or after, and no
     markdown code fences (no ``` characters).
   - Use straight double quotes (") only. Never use curly or
     "smart" quotes anywhere in the file.
   - All years are strings, e.g. "2019".
   - Omit any field I gave you no information for. Do not include
     empty placeholder entries.
5. Every field in the schema is optional — include what you have.

THE SCHEMA (field names and shapes must match exactly):

{
  "credentials": "Post-nominals shown after my name, e.g. MS-HSA, NREMT",
  "tagline": "One line, under 100 characters, that sums up my professional identity",
  "location": "City, State",
  "bio": [
    "First paragraph of my professional bio (2-4 sentences).",
    "Second paragraph.",
    "Optional third or fourth paragraph."
  ],
  "topics": [
    "Short speaking-topic labels, 2-4 words each, e.g. EMS Leadership",
    "Up to about 8 topics"
  ],
  "certifications": [
    "Short certification or license labels, e.g. NRP",
    "One per entry"
  ],
  "employment": [
    {
      "org": "Organization name",
      "title": "Job title",
      "start": "Start year, e.g. 2015",
      "end": "End year, or empty string if current",
      "current": true
    }
  ],
  "education": [
    {
      "institution": "School name",
      "degree": "Degree or program, e.g. Master of Science",
      "field": "Field of study, e.g. Healthcare Administration",
      "year": "Year completed (or expected)"
    }
  ],
  "abstracts": [
    {
      "title": "Title of a signature talk or workshop I deliver",
      "desc": "2-3 sentences: what attendees learn, who it is for, the format",
      "duration": "e.g. 45-60 min",
      "audience": "e.g. EMS leaders and educators",
      "tag": "One-word category, e.g. Leadership"
    }
  ],
  "proposed_topics": [
    {
      "title": "A topic I am actively available to present",
      "description": "1-2 sentences describing the session"
    }
  ],
  "publications": [
    {
      "title": "Title of a book, article, or paper I authored",
      "journal": "Publication or publisher name",
      "year": "Year published",
      "url": "Link if available, otherwise empty string"
    }
  ]
}

Start by asking me your clarifying questions, or if I have
attached documents, summarize what you found and ask only about
the gaps.
----------------------------------------------------------------
================================================================
TROUBLESHOOTING

- "Could not read that file" on upload: the file probably has
  markdown fences (```) or commentary around the JSON. Ask your
  AI: "Give me only the raw JSON, no code fences, no text before
  or after." Save and re-upload.
- The import preview shows what will be applied before anything
  changes — nothing touches your profile until you click Apply.
- Questions or problems? Message Donnie directly through the
  site — Messages > New message > "Donnie Woodyard".

EMSConferences.com · Conferra Group, LLC
================================================================