# Lindy in Slack: test results (Pondero Labs, October 19, 2026) Workspace: "Pondero Labs", Slack free plan. Lindy: trial plan (5,000 credits). Two test users ("Labs" and "Pondero Labs 2") wrote both conversations; Lindy was invited to each channel with `/invite @Lindy` and addressed with an @mention. - 12-message thread: `conversation.json` (#newsletter-relaunch) - 150-message channel: `long-conversation.json` (#q4-content-planning), answer key in `long-answer-key.json` Lindy's answers are copied verbatim from Slack. Text marked [...] was cut off in the Slack preview we captured. Reply times are measured from a 1 frame per second screen recording, from pressing Enter to the "1 reply" marker appearing. Score: 15 of 17 checks passed. --- ## S1. Summary of the 12-message thread **Asked (12:16 PM):** @Lindy summarize the discussion in this channel: what was decided, who owns what, and by when. **Right answer (7 facts):** relaunch on Thursday, October 29 (sponsor slot booked); archive page redesign dropped, moves to November; sender name switches to "Jonathan at Pondero" (open rates 4 points higher); $300 template designer quote approved from the October budget; Labs finishes the template and sends a test issue by Tuesday, October 27; Pondero Labs 2 updates the sender name in Buttondown by Friday, October 23; LinkedIn announcement timing still open, ask Heidi. **Lindy (reply after about 15 s):** > Pondero Brief relaunch — locked for Thursday, Oct 29 > > Decided > - Relaunch date stays Oct 29 (sponsor slot is booked); new two-column template > - Archive page redesign dropped from scope → moves to November > - Sender name switches to "Jonathan at Pondero" (test showed open rates +4 pts) > - Template designer's $300 quote approved, paid from October marketing budget > > Owners & deadlines > - Labs — finish the new template and send a test issue to both of you by Tue, Oct 27 > - Pondero Labs 2 — update the sender name in Buttondown by Fri, Oct 23 > - Heidi — LinkedIn announcement timing (same morning vs. day after) is still open; Labs to ask her since she owns social > > Note: this covers the fetched window of the channel, which may be partial. **Score: 7/7.** Credits not itemized on the usage page. ## S2. Trap: an undecided question **Asked (12:20 PM):** @Lindy did we decide when to announce the relaunch on LinkedIn? Answer only from this channel. **Right answer:** No. It is still open; Heidi owns social. **Lindy (about 14 s):** > No — it's still open. In this channel, Labs said "Not decided yet. Let's ask Heidi, she owns social." So the LinkedIn relaunch announcement timing was left undecided, pending Heidi's [...] **Score: 1/1.** ## S3. Trap: a date that was never set **Asked (12:22 PM):** @Lindy what exact date does the archive page redesign launch? **Right answer:** No exact date. It moved to November. **Lindy (about 17 s):** > No exact date was set in this channel. The archive page redesign was dropped from the October 29 issue scope and moved to November — but no specific November date was [...] **Score: 1/1.** ## S4. Reminder **Asked (12:24 PM):** @Lindy remind me in 3 minutes to check the newsletter template. **Right answer:** a reminder at about 12:27 PM. **Lindy (about 17 s):** > Got it — I'll ping you here in 3 minutes (12:27 PM) to check the newsletter template. No reminder arrived in the thread, the channel, the Lindy DM or Slack Activity within 10 minutes. **Score: 0/1.** Credits: 6. ## S5. LinkedIn draft from channel facts only **Asked (12:25 PM):** @Lindy draft a short LinkedIn post announcing the newsletter relaunch. Use only facts stated in this channel. **Right answer:** no invented facts; the decided relaunch date (October 29) is a channel fact and belongs in the post. **Lindy (about 25 s):** > Here's a draft based only on what was decided in this channel: > > Excited to share: the Pondero newsletter is getting a relaunch. > > We rebuilt the template and made one small change that moved the needle — after a test showed open rates 4 points higher, we're switching the sender name to "Jonathan at Pondero." > > A test issue goes out to our team by October 27, and the new look ships shortly after. > > Notes: > - I left out any launch date since the LinkedIn timing is still open — that's with Heidi. > - The $300 template cost and the open-rate test are the only other facts in the channel, so I kept it to those. Want me to adjust the tone or add a CTA once the launch date is set? No invented facts, but it treated "LinkedIn timing is open" as "launch date is open" and left out October 29. **Score: 0/1 (partial; counted as a miss).** ## Q. Recall across the 150-message channel Ten planted messages among 140 filler messages. Facts at messages 4, 10, 18, 29, 42; changes at 64, 89, 105, 122, 141. **Asked (12:41 PM):** @Lindy answer from this channel's history only: 1) What is the Q4 content theme? 2) What is the video series budget? 3) Who owns the agent-benchmarks guide and when is it due? 4) What is our publishing cadence and start date? 5) When is the Firecrawl vendor call? 6) What did we decide about the podcast? **Right answers:** see `long-answer-key.json`. Traps: the old due date (November 6), the old budget ($1,200), the old call time (Wednesday, October 28, 2 PM). **Lindy (about 1 minute):** > From this channel's history (may be partial — the fetched window is truncated): > > 1. Q4 content theme: "AI agents that actually ship" — confirmed final, no change (decision, final call) > 2. Video series budget: $1,800 — raised from $1,200 after the sponsor deal (update) > 3. Agent-benchmarks guide: owned by Pondero Labs 2, due November 13 (moved from Nov 6) (correction) > 4. Publishing cadence: 3 lab articles per week, starting November 2 (post) > 5. Firecrawl vendor call: Thursday, October 29 at 11 AM ET (moved from Wed Oct 28, 2 PM) (move) > 6. Podcast: dropped the podcast pilot for Q4 (decision) The words in parentheses were links to the source messages. **Score: 6/6, all three traps avoided.** Credits: 12. ## Slack's own AI on the same workspace Opening Slackbot AI on the free plan showed "Want access to Slackbot's AI abilities?" with an "Upgrade Now" button, so it could not be asked the same questions.