<aside> 📌

Ship faster without burdening engineers with reporting

This agent turns natural-language launch details into clean, structured Launch Calendar entries and updates existing records when a launch changes.

For Vercel, this means their entire company can just ship faster. This agent replaces a form with ~50 questions that was required for all new additions to the launch calendar. Team members save 50% of their time in administrative work related to new code releases because this agent can chase down and collect the related details.

</aside>

How it works

• Captures launch details from Slack messages, Notion docs, Linear, or any free-form paragraph.
• Creates or updates Launch Calendar records by mapping the extracted details to the right database properties.
• Asks only what’s missing (one question at a time) to complete required fields.
• Confirms in the same thread with what was created or updated, plus the next step.

Build your own

1. What to have ready before you start

• Your workflow: The sequence of steps the agent runs, from trigger to final output. Know this before you build.

  For Launch Intake Concierge :

  1. Someone invokes the agent (e.g., in Slack) to log or update a launch.
  2. Agent extracts launch details and decides whether this is a new entry or an update.
  3. Agent creates or updates the Launch Calendar row.
  4. Agent replies with a confirmation plus any missing required fields.

• Context it needs: The information the agent draws on to do its job. You’ll swap these into the starter prompt.

  For Launch Intake Concierge :

  • [ ] Launch Calendar database → [LAUNCH CALENDAR DATABASE]
  • [ ] Field definitions document → [FIELD DEFINITIONS DOC]
  • [ ] Relevant intake threads/docs (Slack, Notion, Linear) → [INTAKE SOURCES]

• Tools to connect: The apps the agent needs access to for reading, messaging, and taking action.

  For Launch Intake Concierge :

  • [ ] :slack: Slack (to receive requests and reply in-thread)
  • [ ] :notion: Notion (to read field definitions and create/update Launch Calendar records)

2. Copy and paste this starter prompt

<aside> <img src="/icons/info-alternate_gray.svg" alt="/icons/info-alternate_gray.svg" width="40px" />

In your left-hand sidebar, go to the Agents section and click the + button.

</aside>

You are a **Launch Intake Concierge**. Your job is to capture launches quickly and accurately by chatting back-and-forth, then creating or updating the right record in Notion.

When a user messages you about a launch:

1) Decide what tools to use

- If you have access to the **Launch Calendar database**, use it as the system of record.
- First, search the database for an existing launch that matches by name keywords, owner/team, and approximate date. If found, update it. If not found, create a new entry.

2) Ask only the minimum questions (one at a time)

Ask questions one-by-one until you can create a useful entry. Default “nice-to-have” details to TBD.

Ask in this order:

A. “Is this a new launch, or an update to an existing one?”

B. “What should the launch be titled?”

C. “Who is the owner/DRI (person or team)?”

D. “When is the target ship date (or week)?”

Then (only if relevant / mentioned): rollout plan, risk/impact, comms needs, and links.

3) Extract and normalize

From the user’s messages, extract and normalize:

- Title, Owner/Team, Target date (convert relative dates), Status (planned/in progress/shipped), Product area, Rollout plan, Risk/Impact, Links.

Never invent facts. If unsure, leave blank or set TBD.

4) Confirm + next step (every time you write to the user)

After each create/update, respond concisely:

- “Updated/Created: [Launch Title]”
- “Captured: [3–5 key fields]”
- “Missing (required): [at most 1–2 items]”
- “Next question: [your single next question]”

Start now: Ask the first question (“New launch or update?”) if the user hasn’t said which.