Understand what you are asking
Ask in plain English.
Ask about a release, PR, incident, customer signal, team priority, or a specific piece of engineering work directly from Slack.
Ask Ellie
Ask Ellie: An AI Assistant That Answers Real Engineering Questions
Real answers from your engineering data. Ask in Slack, get context instantly.
Chart context · Streaming answers · Report mode · Lives in Slack too
AI contribution+18%
Payments · last 14 days
Ask Ellie
Context attachedAI contribution · +18% · Payments · 14d
Why did this move?
Acceptance held steady while longer Cursor sessions on the billing release pushed volume.
Next Break down by engineer · Draft a lead update
Streaming answer · Report available
Ask a follow-up…
Built for where engineering work happens
The question starts in Slack. Ellie follows it into the work.
Release questions, review handoffs, incident triage, and planning decisions already happen in Slack. Mention Ellie there. She can inspect the connected systems behind the question and bring the answer, supporting evidence, and next step back to the team.
Mention Ellie and she can inspect the connected work relevant to the question, then return the answer, supporting context, and next decisions to the same conversation.
The team stays in the conversation. Ellie gathers the context behind it.
En+
Engineering
Channels
#general
#eng-leads
#deploys
#incidents
Apps
@Ellie
# eng-leads3 members
AM
Aisha10:42 AM
@Ellie why did AI contribution jump for Payments last week? Anything we should care about before the leadership review?
EL
Ellie10:42 AMAPP
Looking at Payments for last week…
AI contribution · Payments
Lift came mostly from longer agent sessions during the billing release, acceptance rate held steady.
- Top drivers: two authors on billing-api
- Review latency unchanged
- Suggest: share this thread with finance partner
Message #eng-leads · mention @Ellie to ask
See Ellie at work
Watch one Slack question become evidence, action, and follow-through.
Ask Ellie walkthrough: start with a real question in Slack, show the connected systems Ellie checks, the evidence she returns, the work she updates, and the next team update she sets up.
What Ellie can do
Engineering answers with workspace context
Four surfaces that make Ask Ellie feel like a teammate who already has the metric open, not a blank chat.
Investigate the connected work
Pull the relevant context together.
Ellie can inspect connected code, tickets, meetings, incidents, product analytics, and AI usage instead of making the team search each source separately.
Show what supports the answer
Make the reasoning inspectable.
Every answer carries source-backed facts, provider connections, and information that still needs verification before the team acts.
Close the loop
Move from finding to follow-through.
Create or update supported Linear and Jira work, attach commentary or thread context, assign an owner, add priority or timing, and set the next update.
- Slacknot needed here
- Linear23 issues
- GitHub31 PRs
- Jiranot needed here
- PagerDuty9 incidents
- Sentry1,204 events
Ellie#checkout-guildonline
Which PRs from this week are most likely to cause a regression?
✓Read 1,267 items across four sources
Two of the thirty-one.
- ✓PR 4412 changes the retry path that INC-1908 and INC-1877 both came from.
- ✓PR 4390 drops a null check that Sentry flagged 214 times last quarter.
- ✓The other 29 touch code with no incident history in twelve weeks.
- ○PR 4405 has no linked issue, so its intent could not be checked. Unverified.
Linked, gathered and corroborated from four connected sources.
Ask Ellie about any release, PR or incident…
From answer to follow-through
Ask now. Keep the team updated until the work is done.
Tell Ellie what to investigate, which work to create or update, and what your team should receive tomorrow, next Friday, or at the end of the month. Choose the Slack channel or direct message where the update should arrive.
Find the evidence behind the question
Ellie inspects the connected systems and returns what she can support.
Keep the evidence with the work
Findings, threads, owners, priority, timelines and next steps stay attached.
Set the next update in plain English
Specify when it lands, where it lands, and who it goes to.
Answers now. Updates when they matter.
Ask once. Get the next update without asking again.
Ellie can answer the question in front of you, keep the work current, and send a daily, weekly, or monthly update to the Slack channel or direct message you choose.
Get the update you need, when and where you need it
Ask Ellie to send your priorities daily, your team updates, check weekly summaries, or deliver monthly recaps. Choose the channel or direct message and adjust the schedule anytime.
WeeklyDailyMonthly#eng-leadsDMWeekly engineering briefOn
Keep the evidence with the work
Add findings to the ticket, project, or workstream so the next person sees the source, owner, and timeline behind the decision.
Tickets and projectsSources attachedPrevious contextENT-2214Attach evidencePR 4127Checked cycle protectionINC-2287Create linked follow-up
Follow product signals back to engineering changes
Ask Ellie to link recurring behaviour, customer talks, tickets, incidents, and code changes, making drop-off or adoption a focused engineering issue.
Supported questionsCorrelatedWhich teams are over capacity?What's our defect rate per release?How did we get this over the quarter?
Move from finding to follow-through
Ellie can create or update tickets, assign owners, set priority and timelines, and prepare the next follow-up. Work with relevant context where supported.
RemindersPreparedSend me a weekly @Ellie review every Monday 9amMaya ChenMobileAlex ReyesPlatformDev PatelPayments
What people ask
The questions dashboards create every week.
Free-form engineering questions about PR health, delivery risk, AI adoption, incidents with history, so an investigation can continue tomorrow.
When PRs are aging, who?Draft a leadership review candidateAny Sev 2 themes in the last 30 days?What changed in this metric?Why did a bad ship for Friday?
Which incidents lack a follow-up?Turn this into a reportCompare this period with the last oneWhere are we leaking release time?Who is overloaded on reviews?Will this land on time?
Where is our response time?Continue where I left offDeploy frequency vs failure rateWhat should I expect first?Which team drove the fix last quarter?Support backlog vs bugs
Start with the work you already have open.
Attach the chart. Ask the reason. Follow up in the product, or in Slack, where the team already is.
- Permission-aware answers
- No training on customer code
- Web and Slack