/lynqu-event-blitz

name: lynqu-event-blitz
description: Run a conference, trade show or booth end-to-end in Lynqu. Set up the event and campaign, capture leads, attribute them, then start follow-up. Requires the Lynqu MCP server connected.

Lynqu Event Blitz

You run an event as a complete motion: set it up before, capture cleanly during, attribute and follow up after, and answer the only question that matters afterwards: **did this event make money?**

Most event lead capture fails in one of two places, and both are avoidable. Setup is skipped, so nothing is attributable and the ROI question is unanswerable forever. Or follow-up starts a week late, by which point the conversations have evaporated and the leads are cold. This skill exists to make both hard to get wrong.

Invocation

/lynqu event <name | "SaaStr next month" | "post-event for last week's show">

Phase 1: Before the event (setup)

Skipping this is the expensive mistake. Do it even the night before.

1. **`list-events`**: does it already exist? Someone may have set it up. Without `events.manage` (admins by default) this lists only the events live right now, so a draft someone else created will not show; ask before creating a second one. 2. **`create-event`**: name, dates, location. Events can be open-ended if the dates aren't fixed yet; that's better than not creating it. 3. **`create-campaign`**: the money side: budget, goals, members. The event holds the *when and where*, the campaign holds the *spend and target*. You need both to answer the ROI question. 4. **`link-event-to-campaign`**: the link **is** the attribution spine. Without it you have two records that never talk. 5. **`create-campaign-goal`**: a real target: leads captured, pipeline value, meetings booked. `list-metric-catalogue` shows what can be measured. A goal set afterwards is a story; set now it's a target. 6. **`add-campaign-member`**: who's working the booth. Takes the **`organization_user_id`** (not the user id). `list-team-members` returns both. 7. **Capture route**: `list-capture-forms` and set up a capture form for the booth iPad or QR code. `get-capture-form-stats` later tells you which route actually worked. 8. **Pipeline**: decide now whether event leads go to their own board (`list-lead-pipelines`, `get-pipeline-stages`). Event leads mixed into outbound are indistinguishable within a week. 9. **Target list**: `lynqu-lead-research` against the exhibitor and speaker lists. Walking a floor with a ranked list of who to find beats wandering. 10. **Tickets**, if the org runs its own event and holds the ticketing add-on: `issue-tickets` and `list-event-tickets`. Skip cleanly on `ADDON_REQUIRED`. 11. **The post-event sequence, drafted now.** `create-followup-trigger` with `event_id`: the recap template the morning after, pricing or a booking link a few days on, up to five steps. `enabled: false` until the org's postal address is on file and the copy is approved; `update-followup-trigger` switches it on. Writing it before the show is what makes the 48-hour window hold without anyone remembering to send

Phase 2: During the event

• Badge and card **scanning happens in the Lynqu mobile app**. It handles OCR,

offline queueing and bulk mode. Say so rather than inventing a workflow

• The capture form covers everyone who prefers to type
• Mid-event, the one thing worth doing daily: **capture the context while it's

fresh**. A note saying *"asked about Salesforce sync, has 40 reps"* written on day one is worth more than everything the badge scan produced

• `update-campaign-status` to keep the campaign live and reporting

Phase 3: After the event (the 48 hours that decide the ROI)

Speed beats polish here. A good-enough follow-up on day two outperforms a perfect one on day ten, and it isn't close.

1. **Capture the backlog**: hand to `lynqu-lead-capture`: parse, dedupe against contacts and each other (two reps scanning the same person is the norm at a busy booth), create. 2. **Attribute everything.** `attach-leads-to-campaign` for the money side and `attach-leads-to-event` for scans made without the event picked (≤ 100 per call each). Say first that attaching to the event runs its sequence, so the recap can go out from this step. Attribution is only possible now. Nobody backfills it. 3. **Triage by what was actually said**, not by title. `bulk-update-leads` (≤ 100) to set temperature:

• **Hot**: asked for pricing, a demo, or a date → task due within 24 hours
• **Warm**: real interest, no ask → sequence within 48 hours
• **Cold**: badge swap for the swag → nurture, low effort, no guilt

4. **Score**: `lynqu-qualify` on the warm and hot bands. 5. **Follow up**: `lynqu-outreach` (post-capture angle: you *met* them, so this isn't cold) or `lynqu-sales-followup` where a real conversation happened. Reference the booth conversation specifically, or don't bother. 6. **Book the meetings**: `propose-booking` while the event is still recent enough to be a reason. 7. **Close the event**: `update-event-lifecycle` when the capture work is done, so it stops showing as active.

Phase 4: Did it pay?

• **`get-event-portfolio`**: the roll-up across events: leads, pipeline value,

won value, cost. This is the answer to "should we do this show again", and it only works if Phase 1 was done

• **`get-campaign`** and **`list-campaign-goals`**: actual against target
• **`get-capture-form-stats`**: which capture route worked
• **`get-forecast`**: what the event actually put into the pipeline
• **`get-followup-performance`** with the campaign's `campaign_id`: whether the

post-event emails got replies and meetings. Trust a reply rate only on 20 or more delivered emails, and only while `replies_tracked` is true

• **`update-campaign`** if the real spend differs from the budget set in Phase

1, after a yes. Cost per qualified lead is only as honest as that n