---
title: "Why Slack Is the Future of B2B Support"
episode: 40
podcast: "The LeanScale Podcast"
publisher: "LeanScale"
guest: "Tony Tom"
guest_title: "Founder & CEO of Orca"
date_published: 2025-10-29
date_modified: 2026-07-22
duration: 00:34:40
word_count: 5513
topics: ["ai-in-gtm", "gtm-strategy", "revenue-operations", "brand-positioning"]
canonical_url: https://leanscale-knowledge-hub.netlify.app/podcast/tony-tom-slack-b2b-support/
source: "LeanScale Podcast Knowledge Hub — https://leanscale-knowledge-hub.netlify.app"
license: "Free to quote and cite with attribution to The LeanScale Podcast."
---

# Why Slack Is the Future of B2B Support

_Tony Tom on Orca's account-first, AI-powered approach to B2B customer support_

**Episode 40 · The LeanScale Podcast**  
Tony Tom, Founder & CEO of Orca · Hosted by Anthony Enrico  
Published October 29, 2025 · Updated July 22, 2026 · 00:34:40  
Canonical: https://leanscale-knowledge-hub.netlify.app/podcast/tony-tom-slack-b2b-support/

**Topics:** AI in GTM · GTM Strategy · Revenue Operations · Brand & Positioning


## Executive summary

Most support software is built around the ticket. Tony Tom, founder and CEO of Orca, thinks that's exactly backwards for B2B. In this episode he sits down with LeanScale to make the case that in a B2B relationship the unit that matters is the account — and that the future of post-sales support runs through Slack, where most B2B teams and their customers already live all day. Orca is his answer: an AI-first customer support platform that treats the account as the centerpiece, ingests conversations across Slack, email, and Discord, and closes the loop between support, product, and leadership.

Tony's conviction comes from roughly a decade in B2B product management, including time at ZoomInfo. Building product for both small and large companies, he kept hitting the same wall: the voice of the customer never made it cleanly back to the teams building the product — you had to hunt for it. Orca began as a bridge between the go-to-market world (customers, prospects, what they want) and R&D. But as customers used it, he realized the customer-facing teams themselves couldn't keep up with the scale of post-sales — feedback and requests scattered across five different channels that nobody could manage. So Orca narrowed in on the post-sales team and rebuilt support around the account.

The through-line is 'account, account, account.' In pre-sales, everything is organized around the account you're trying to win; the moment a deal closes, the account disappears and support collapses into disconnected tickets. Tony's argument is that AI's real job in B2B support isn't answering a single question — it's assembling context: pre-sales data, call recordings, CRM history, and the human answers that already earned a thumbs-up, so you can treat the account well, not just close a ticket. Champions leave, users and buyers feel differently about the product, and 20% of features carry 80% of customers — none of which a quarterly 30-minute QBR can surface.

The bulk of the episode is a live product tour that doubles as a philosophy. Orca sits in Slack Connect channels and turns messages into tickets with AI-generated descriptions and auto-assignment; it groups stray, out-of-thread messages into a single ticket by context; it auto-triages each ticket — account, priority, type, original message — into one Slack triage channel so engineering, product, and leadership never miss context. Teams discuss internally in a per-ticket thread, reply back to the customer with a pre-set emoji, and can mute noisy customer channels entirely and just watch Orca. Discord and email flow in the same way, and for technical tickets Orca suggests answers (grounded in the customer's docs and even their GitHub codebase) rather than auto-sending them.

Two ideas land hardest. First, documentation: nobody owns it in a B2B lifecycle, so it's always incomplete — 'garbage in, garbage out.' Orca turns a Loom video into full step-by-step documentation with screenshots and no human touch, flipping it to 'quality in, quality out' and closing the data loop that makes AI answers good. Anthony immediately connects it to LeanScale, which Looms everything it builds but leaves that knowledge trapped in video. Second, AI beyond answering: Orca's in-house agent turns natural-language questions ('group all accounts by ticket count,' 'show me every Slack request from the last two weeks') into instant answers that used to require Snowflake, Tableau, and half a day of analyst work — then schedules them as workflows to leadership. The takeaway for founders, CS, and RevOps leaders: workflows plus AI, organized around the account, is how B2B support finally scales.


## Key takeaways

1. **Build support around the account, not the ticket** — Legacy ticketing platforms are horizontal — the ticket is the centerpiece. Tony argues B2B is different: in pre-sales it's 'account, account, account,' but the moment a deal closes the account vanishes and support fragments into disconnected tickets. Orca puts the account back at the center of post-sales.
   _Why it matters:_ If you run B2B post-sales, organize your support data, timelines, and sentiment at the account level. A tool optimized for individual tickets will always lose the relationship context that determines renewals and expansion.
   _For:_ Customer Success, RevOps Leaders, Founders

2. **AI's job in B2B support is context, not just answers** — Every AI company defaults to 'how do I answer this question?' because that's what ChatGPT does. Tony's contrarian point: B2B support is deeply contextual, so AI's real value is assembling pre-sales data, call recordings, CRM history, and previously-approved human answers to serve the whole account — not to reply to one message.
   _Why it matters:_ Evaluate AI support tools on how well they surface and reuse context across the account, not on raw answer generation. Context is the moat in high-touch B2B.
   _For:_ Customer Success, RevOps Leaders, Revenue Executives

3. **Account happiness and user happiness are different things** — A stakeholder or champion can be happy while the actual users are not — or vice versa. Champions also change jobs, and the incoming champion lacks context on why the product was bought and how it's used. Support built around tickets never sees any of this.
   _Why it matters:_ Instrument sentiment at the account level and watch for champion turnover. Treating a happy buyer as a healthy account is how B2B teams get blindsided at renewal.
   _For:_ Customer Success, Revenue Executives

4. **Quarterly QBRs can't carry the customer relationship** — Four 30-minute touchpoints a year is not enough to keep a customer paying $20K–$50K aware of everything you've shipped — especially when 20% of features drive 80% of usage. Most communication about value gets crammed into a cadence that's far too thin.
   _Why it matters:_ Don't rely on QBRs to convey value or feature awareness. Use always-on, in-channel communication (Slack) and AI-summarized patterns to keep accounts informed between reviews.
   _For:_ Customer Success, Revenue Executives

5. **Meet customers where they live — inside Slack** — More and more B2B companies run support through Slack Connect channels. Orca sits in those channels, tracks every message as a ticket with an AI-generated description, and auto-assigns it — so teams can even mute their customer channels and just watch Orca to stay on top of every conversation.
   _Why it matters:_ If your post-sales team already lives in Slack, route support through it rather than forcing customers into a separate portal. The channel with the highest engagement should be the system of record.
   _For:_ Customer Success, RevOps Leaders, Sales Leaders

6. **Group the mess: stray messages should become one ticket** — Customers rarely reply in tidy threads — they fire off related messages as standalone posts. Orca reads across the channel, figures out the actual context, and auto-groups related messages into a single ticket, so the same issue isn't tracked in five disconnected places.
   _Why it matters:_ Small workflow intelligence compounds. The intentional handling of real (messy) human communication is where a support tool earns trust — and prevents duplicated, dropped, or contradictory responses.
   _For:_ Customer Success, RevOps Leaders

7. **Triage the full context to the whole team automatically** — Orca auto-triages each ticket — account, priority, type, and the original message — into a single Slack triage channel so engineering, product, and leadership see the complete context without anyone manually forwarding or summarizing it.
   _Why it matters:_ Automating triage removes the human bottleneck that loses context between support and the teams who can actually fix things. Build the workflow so no team 'misses out on anything.'
   _For:_ RevOps Leaders, Customer Success, Founders

8. **Suggest answers — don't auto-send them — in technical B2B** — For technical, highly contextual B2B questions, Orca deliberately surfaces AI-suggested responses that a human reviews and sends, rather than auto-answering. A non-technical support rep can forward a grounded, documentation-backed draft to the CTO and keep the customer feeling responded-to.
   _Why it matters:_ In complex B2B, keep a human in the loop. Auto-answer works for simple horizontal cases; for contextual technical support, AI should accelerate a person, not replace them.
   _For:_ Customer Success, RevOps Leaders, Founders

9. **Turn Loom videos into documentation — quality in, quality out** — Documentation is always incomplete because nobody owns it in a B2B lifecycle. Orca converts a Loom video into full step-by-step documentation — screenshots included, no human touch — so the low-quality data AI draws from becomes high-quality. That flips 'garbage in, garbage out' to 'quality in, quality out.'
   _Why it matters:_ The knowledge already exists in the videos your team records for customers. Bake video-to-docs into the workflow to close the data loop that makes AI support answers actually good.
   _For:_ Customer Success, Founders, RevOps Leaders

10. **Nobody owns documentation — so automate it** — Ask five people who owns docs in a B2B company and all five say 'not me.' Product, CS, and support each assume someone else has it. That ownership vacuum is why documentation is perpetually stale and thin.
   _Why it matters:_ Stop trying to assign a documentation owner and instead generate it from the artifacts you already produce (Looms, demo videos). Automation beats a RACI chart nobody follows.
   _For:_ Founders, RevOps Leaders, Customer Success

11. **AI's biggest win is the backend, not the reply** — The unglamorous work — reporting patterns to leadership, product, and customers; finding where docs lack clarity; spotting cross-channel trends — used to take a support manager half a day to a full day using Snowflake and Tableau. Orca's in-house agent answers those natural-language questions in seconds and schedules them as recurring workflows.
   _Why it matters:_ The overlooked ROI of AI in support is collapsing analyst/reporting overhead and giving leadership continuous visibility — not shaving seconds off individual ticket replies.
   _For:_ RevOps Leaders, Revenue Executives, Founders

12. **Workflows plus AI is the B2B system, not answering questions** — Underneath Orca sits a workflow engine: triage workflows, condition-based routing (time zones, ticket type), and AI-driven workflows (bad sentiment escalates to a manager; a repeatedly breached SLA alerts a specific channel). Tony's thesis is that 'workflows plus AI' — not question-answering — is where B2B support is heading.
   _Why it matters:_ Orchestrating SLAs, routing, and escalation automatically is what lets a B2B company scale support. Treat the workflow layer, not the chatbot, as the core of your support system.
   _For:_ RevOps Leaders, Customer Success, Founders


## Frameworks

### Account-First (vs. Ticket-First) Support (03:38)

**Definition:** Structure B2B support around the account as the centerpiece — its timeline, sentiment, history, and stakeholders — rather than around individual, disconnected tickets the way horizontal ticketing platforms do.

In pre-sales everything is 'account, account, account'; post-sales, most tools drop the account and collapse into tickets. Orca carries the account through post-sales so support serves the relationship, not just the request.

### Context Over Answers (05:02)

**Definition:** In B2B, AI's role is to assemble and surface the full context of an account — pre-sales data, call recordings, CRM history, previously-approved human answers — rather than to generate a single reply to a single question.

Every AI company defaults to 'answer the question' because that's the ChatGPT pattern. Tony argues B2B support is contextual, so context assembly (not answer generation) is where AI creates real value.

### Suggest, Don't Auto-Answer (18:33)

**Definition:** For technical, high-context B2B questions, AI should draft a documentation-grounded suggested response that a human reviews and sends — keeping a person in the loop instead of auto-replying.

Auto-answer fits simple horizontal cases. Orca's stance is that complex B2B support requires human judgment, so AI accelerates a rep (even a non-technical one handing off to a CTO) rather than replacing them.

### Loom-to-Docs: Quality In, Quality Out (24:20)

**Definition:** Automatically convert existing Loom (and demo) videos into complete, screenshot-rich documentation, turning the thin, unowned docs AI draws from into high-quality source material — closing the data loop that makes AI answers good.

Because nobody owns documentation in a B2B lifecycle, the underlying data is poor ('garbage in, garbage out'). Generating docs from the videos teams already record flips it to 'quality in, quality out.'

### Workflows + AI (30:18)

**Definition:** A workflow engine (triage, condition-based routing by time zone and ticket type) combined with AI-driven workflows (sentiment-based escalation, SLA-breach alerts) — the layer Tony argues actually constitutes a B2B support system.

Rather than framing support as answering questions, Orca frames it as orchestrating the backend: routing, escalation, and SLA enforcement that let a B2B company scale post-sales.


## Quotes

_Speakers inferred from an undiarized transcript — verify before attributing._

> "Most of the ticketing platforms are built for horizontal use cases. It's more ticket is the center of that platform. But we see pre-sales, or anything until sales closure, is always account, account, account."
>
> — Tony Tom, The LeanScale Podcast Ep. 40 (03:38)

> "You have to keep account in your hands to cater to them, pamper them throughout. But when we get into post-sales, that gets stopped. Account is nowhere to be seen. So we want to bring that back in."
>
> — Tony Tom, The LeanScale Podcast Ep. 40 (03:38)

> "By default, every AI company starts there — how to answer this question. But when it comes to B2B, it's very contextual."
>
> — Tony Tom, The LeanScale Podcast Ep. 40 (05:02)

> "All that can be used to treat the account better, not just treat the ticket better."
>
> — Tony Tom, The LeanScale Podcast Ep. 40 (05:39)

> "A champion might not be happy, but the users could always be happy. That's another scenario."
>
> — Tony Tom, The LeanScale Podcast Ep. 40 (06:19)

> "Four times in a year, you're paying $20,000, $50,000 for a product. You talk to them four times a year, you have 30 minutes. How do you convey all of this?"
>
> — Tony Tom, The LeanScale Podcast Ep. 40 (07:00)

> "That account is the persona you're really trying to serve. So it's difficult to do that with the current solutions."
>
> — Anthony Enrico, The LeanScale Podcast Ep. 40 (08:12)

> "Now all our customers can mute their customer Slack channels and just look at Orca to be in the whole spectrum of listening to customers."
>
> — Tony Tom, The LeanScale Podcast Ep. 40 (16:21)

> "We believe in enabling AI to suggest answers rather than just auto-answering, especially in the B2B, very technical, very contextual questions."
>
> — Tony Tom, The LeanScale Podcast Ep. 40 (18:33)

> "This documentation was created totally from a Loom video, including the screenshots — no human touch at all."
>
> — Tony Tom, The LeanScale Podcast Ep. 40 (23:08)

> "Instead of garbage in, garbage out, it will become quality in, quality out. That's our way of closing the loop."
>
> — Tony Tom, The LeanScale Podcast Ep. 40 (24:20)

> "We Loom every single thing we build for a customer. A lot of that is just living in that video — it's not put into documentation that could train our own models as well."
>
> — Anthony Enrico, The LeanScale Podcast Ep. 40 (24:20)

> "Nobody owns the documentation piece in a B2B lifecycle. If you ask five people, all of them say, 'I don't own it.'"
>
> — Tony Tom, The LeanScale Podcast Ep. 40 (25:35)

> "People think support always relates to answering questions, which is where we come in and bring in a differentiation."
>
> — Tony Tom, The LeanScale Podcast Ep. 40 (29:28)

> "Workflows plus AI is the key in B2B — using the components to deliver what really, really matters."
>
> — Tony Tom, The LeanScale Podcast Ep. 40 (30:18)

> "Orchestrating the SLAs, the assignments, creating everything automatically is what's going to help a B2B company scale."
>
> — Anthony Enrico, The LeanScale Podcast Ep. 40 (31:48)


## Practical advice by role

### Founders

- Position your post-sales product around the account, not the ticket — in B2B the relationship, not the request, is the unit that renews and expands.
- Stop assigning a documentation owner nobody wants; generate docs automatically from the Looms and demo videos your team already records so AI has quality source data.
- Dogfood your own workflows — Orca ships a workflow that auto-invites new signups into a Slack channel so customers never have to ask for support access.

### Customer Success

- Meet customers in Slack where they already are; track every message as a ticket and mute the noise, watching one consolidated view instead of a dozen channels.
- Watch sentiment at the account level and for champion turnover — a happy buyer with unhappy users (or a new champion with no context) is a hidden churn risk.
- Don't rely on quarterly QBRs to convey value; use always-on communication and AI-summarized patterns so customers stay aware of the 20% of features that drive 80% of usage.

### RevOps Leaders

- Auto-triage full context (account, priority, type, original message) to engineering, product, and leadership so nothing gets lost between support and the teams that can fix it.
- Build the workflow layer — routing by time zone and ticket type, sentiment-based escalation, SLA-breach alerts — as the backbone of support, not a chatbot.
- Use natural-language AI over your support data to replace half-day Snowflake/Tableau reporting cycles and schedule recurring digests to leadership.

### Revenue Executives

- Treat post-sales visibility as a leadership asset: continuous, cross-channel pattern reporting beats waiting on a support manager to hand-build a deck.
- Keep a human in the loop for technical, high-stakes B2B answers — let AI accelerate the rep, not auto-reply on your behalf to your biggest accounts.


## AI takeaways

**Thesis:** In B2B support, AI's real value is assembling account-level context and automating the backend — triage, documentation, reporting, and workflows — not auto-answering individual tickets. Keep a human in the loop for the contextual, technical questions that define B2B, and use AI to make good data out of the artifacts you already produce.

- **Context beats answers** — Every AI company defaults to answering the question (the ChatGPT pattern). B2B support is contextual, so AI should surface pre-sales data, call recordings, CRM history, and previously-approved answers to serve the account.
- **Suggest, don't auto-send** — For technical, high-context B2B questions, Orca drafts documentation-grounded suggestions a human reviews — a non-technical rep can forward a grounded answer to the CTO instead of the bot replying.
- **Close the data loop** — AI answers are only as good as the docs behind them, and docs are always thin because nobody owns them. Generating docs from Loom videos flips 'garbage in, garbage out' to 'quality in, quality out.'
- **Automate the backend** — Natural-language questions over support data ('group accounts by ticket count') replace half-day Snowflake/Tableau reporting and can be scheduled as recurring workflows to leadership.
- **Workflows + AI** — Sentiment-based escalation and SLA-breach alerts layered on a routing engine — not question-answering — are what Tony argues make a B2B support system scale.

**Agent & automation ideas**

- A support agent that reads across a Slack/email/Discord channel and auto-groups stray, out-of-thread messages into a single ticket by inferred context.
- A triage agent that classifies each ticket by account, priority, and type and posts full context into one channel for engineering, product, and leadership.
- A video-to-docs agent that turns Looms and demo recordings into screenshot-rich, step-by-step documentation to feed the knowledge base AI answers draw from.
- A natural-language reporting agent over support data that answers ad-hoc leadership questions in seconds and schedules recurring cross-channel pattern digests.
- A sentiment/SLA workflow agent that escalates unhappy accounts to a manager and alerts a specific channel when an SLA is repeatedly breached.


## Operations takeaways

### Revenue operations

- **Auto-triage context.** Push account, priority, type, and the original message to one channel so engineering, product, and leadership never miss context.
- **Workflow-first.** Build routing (time zone, ticket type), sentiment escalation, and SLA alerts as the backbone — the chatbot is a feature, not the system.
- **Kill the reporting cycle.** Replace half-day Snowflake + Tableau report builds with natural-language queries and scheduled digests.
- **Feed the model.** Ground AI on the customer's own docs and (for technical accounts) their GitHub codebase before it drafts answers.

### Customer operations

- **Account is the unit.** Track timeline, sentiment, and history at the account level so post-sales serves the relationship, not disconnected tickets.
- **Live in Slack.** Route support through the Slack Connect channels customers already use; consolidate into one view and mute the rest.
- **Watch the champion.** Champions leave and buyers differ from users — instrument sentiment to catch the account risks a happy stakeholder hides.
- **Close the docs loop.** Auto-generate documentation from Looms so answers improve and knowledge stops dying inside videos.
- **Keep humans in technical loops.** Suggest AI answers for complex B2B questions and let a person send them — accuracy and trust over auto-reply.


## Metrics mentioned

| Value | Metric | Context |
| --- | --- | --- |
| 4×/yr · 30 min | Enterprise QBR cadence | Four 30-minute quarterly reviews a year is too little to keep a paying customer aware of everything shipped — the gap Orca's always-on model fills. |
| $20K–$50K | Annual contract value cited | The order of magnitude a B2B customer pays, making four short QBRs an inadequate way to convey value. |
| 80/20 | Feature-usage concentration | Roughly 20% of features are used by ~80% of customers, so keeping every account aware of the rest is a real support challenge. |
| 11 screenshots · 0 human touch | Loom-to-docs output | A single documentation page Orca generated entirely from a Loom video — step-by-step instructions plus 11 screenshots, no human editing. |
| ½–1 day → ~3 seconds | Support reporting time | A cross-channel pattern report that took a support manager half a day to a full day (via Snowflake + Tableau) is answered by Orca's agent in about three seconds. |


## Entities mentioned

- **Orca** (company) — Tony Tom's company; the AI-first, account-first B2B customer support platform demoed throughout the episode (Slack/email/Discord ingestion, auto-triage, Loom-to-docs, natural-language agent). · https://leanscale-knowledge-hub.netlify.app/company/orca/
- **ZoomInfo** (company) — One of the larger B2B companies Tony worked at in product management before founding Orca; part of the background that surfaced the voice-of-customer gap. · https://leanscale-knowledge-hub.netlify.app/company/zoominfo/
- **Snowflake** (company) — Named as part of the legacy reporting stack — data reported back to Snowflake, then pulled into Tableau to build a report — that Orca's natural-language agent replaces. · https://leanscale-knowledge-hub.netlify.app/company/snowflake/
- **Tableau** (company) — Named alongside Snowflake as the old analytics path support teams used to generate reports; Orca's agent answers the same questions in seconds. · https://leanscale-knowledge-hub.netlify.app/company/tableau/
- **LeanScale** (company) — The host's company; Anthony connects Orca's Loom-to-docs feature to LeanScale, which Looms everything it builds but leaves that knowledge trapped in video. · https://leanscale-knowledge-hub.netlify.app/company/leanscale/
- **Tony Tom** (person, guest) — Founder & CEO of Orca, an account-first, AI-native B2B customer support platform built around Slack; ~10 years in B2B product management (incl. ZoomInfo). · https://leanscale-knowledge-hub.netlify.app/guest/tony-tom/
- **Anthony Enrico** (person, host) — Co-founder of LeanScale and host of The LeanScale Podcast. · https://leanscale-knowledge-hub.netlify.app/guest/anthony-enrico/
- **Slack** (tool, Team Messaging) — The centerpiece channel for Orca — it sits in Slack Connect channels, turns messages into tickets, runs a triage channel and per-ticket team threads, and lets teams reply to customers via a pre-set emoji.
- **Loom** (tool, Video Messaging) — Source material for auto-generated documentation — Orca turns a Loom video into full step-by-step docs with screenshots and no human touch.
- **Discord** (tool, Community / Messaging) — One of Orca's support channels; often surfaces technical, community-sourced tickets with code snippets and errors that get AI-suggested responses.
- **GitHub** (tool, Developer / Code Hosting) — For technical customers, Orca can be granted controlled access to their GitHub codebase so its AI agents understand folder structure and implementation before drafting answers.
- **ChatGPT** (tool, AI Assistant) — Referenced as the default 'answer the question' AI pattern that Tony contrasts with the contextual, account-first approach B2B support needs.


## FAQ

**Q: What is Orca?**

A: Orca is an AI-first customer support platform built specifically for B2B companies, with the account — not the individual ticket — as its centerpiece. It sits inside Slack, email, and Discord; auto-triages and groups messages into tickets and account-level timelines; suggests AI responses for humans to review; generates documentation from Loom videos; and lets teams query their support data in natural language. Its founder and CEO is Tony Tom.

**Q: Why does Tony Tom say B2B support should be account-first instead of ticket-first?**

A: Because in B2B the relationship is the unit that matters. In pre-sales everything is organized around the account you're trying to win, but most ticketing platforms are horizontal and collapse post-sales support into disconnected tickets, losing the account. Orca keeps the account — its timeline, sentiment, history, and stakeholders — at the center of post-sales so support serves the relationship, not just the request.

**Q: How does Orca use Slack for customer support?**

A: Orca sits inside Slack Connect channels and tracks every incoming message as a ticket with an AI-generated description and auto-assignment. It groups stray, out-of-thread messages into one ticket by context, auto-triages full context (account, priority, type, original message) into a dedicated Slack triage channel, hosts a per-ticket internal team thread, and lets teams reply to the customer using a pre-set emoji. Teams can even mute their customer channels and just watch Orca.

**Q: Does Orca auto-answer customer questions with AI?**

A: Not for technical, contextual B2B questions. Orca deliberately surfaces AI-suggested responses that a human reviews and sends, rather than auto-answering. A non-technical rep can forward a documentation-grounded draft to a CTO and keep the customer feeling responded-to. Its stance is that AI should accelerate a person in complex B2B support, not replace them.

**Q: How does Orca turn Loom videos into documentation?**

A: Orca ingests a Loom (or other demo) video and generates complete step-by-step documentation from it — including screenshots — with no human touch. Because documentation is usually thin (nobody owns it in a B2B lifecycle), this converts the low-quality data AI draws from into high-quality source material, flipping 'garbage in, garbage out' to 'quality in, quality out' and closing the data loop.

**Q: How does Orca help with reporting and analytics?**

A: Orca has an in-house AI agent that answers natural-language questions over your support data — for example, grouping all accounts by ticket count or listing every Slack request from the last two weeks — in seconds. This replaces reporting that used to require piping data into Snowflake and Tableau and half a day to a full day of a support manager's work, and the queries can be scheduled as recurring workflows to leadership, product, and engineering.

**Q: What does 'workflows plus AI' mean in Orca?**

A: Underneath the product is a workflow engine. It runs triage workflows, condition-based routing (by time zone, ticket type, and other conditions), and AI-driven workflows — for example, escalating to a manager when sentiment turns bad, or alerting a specific channel when an SLA is repeatedly breached. Tony argues this orchestration layer, not question-answering, is what actually makes B2B support scale.


## Timeline

- **00:00** — Meet Tony Tom and the origin of Orca
- **02:08** — Why B2B support data is fragmented across channels
- **03:38** — Account-first vs. ticket-first
- **05:02** — Context over answers: what AI should actually do
- **08:12** — Product tour: Slack tickets and message grouping
- **11:42** — The triage workflow
- **13:42** — Team threads and replying to customers via emoji
- **16:21** — Multi-channel: email, Discord, and suggested responses
- **19:21** — The account timeline and sentiment view
- **21:03** — How AI responses are generated (GitHub + docs)
- **22:30** — Loom-to-docs: closing the data loop
- **26:14** — AI beyond answering: reporting and the in-house agent
- **30:18** — Workflows + AI for B2B
- **33:13** — How to get started with Orca


## Related episodes

- **Ep. 95: Why AI Means More RevOps Hires, Not Fewer** (Jimmy O'Halloran, New Relic) — Both episodes land on the same thesis: AI makes operators superhuman and needs a sanitized dataset — it augments people, it doesn't replace them. · https://leanscale-knowledge-hub.netlify.app/podcast/jimmy-ohalloran-new-relic-revops-consumption-revenue/
- **Ep. 85: Why AI + GTM Engineers Can't Replace RevOps** (Tessa Whittaker) — A companion take on the limits of AI in the operating layer, echoing Orca's 'suggest, don't auto-answer' stance. · https://leanscale-knowledge-hub.netlify.app/podcast/tessa-whittaker-ai-gtm-engineers-revops/
- **Ep. 88: Why AI Won't Close Your Biggest Deals** (Michael Kiernan, Nextdoor) — A CRO's view on keeping humans in high-stakes B2B moments — pairs with Tony's human-in-the-loop approach to technical support. · https://leanscale-knowledge-hub.netlify.app/podcast/michael-kiernan-nextdoor-ai-wont-close-deals/
- **Ep. 91: Why Outcome-Based Pricing Is a Trap for Most AI Companies** (Roee Hartuv) — Another founder-grade look at building an AI-native B2B product and where the real value (and traps) sit. · https://leanscale-knowledge-hub.netlify.app/podcast/roee-hartuv-outcome-based-pricing-trap/


## Full transcript

_Machine-transcribed and not diarized; speaker attribution is inferred._  
_Transcript only, as a separate file: https://leanscale-knowledge-hub.netlify.app/podcast/tony-tom-slack-b2b-support/transcript.md_

### 00:00 — Meet Tony Tom and the origin of Orca

**[0:00]** Today we got Tony Tom, founder, CEO of Orca. Tony, so excited to have you here. Really, really pumped to dive in to what you're doing and bringing an AI agentic experience to supporting B2B customers in Slack, where 99.99% of us are living all day long. So Tony, we'd love to hear how you got the inspiration to start Orca and gave you the courage to get it started. Yeah, thanks. I'm super glad to be here. Great to chat with you folks, being a fan of the podcast for a long time. To tell the founder story, it's always a long story for every founder, but long story short, I've been into startups for a very long time,

**[0:50]** especially in the early days when startups was not cool, being in product management, specifically for B2B companies for the last decade or so. And as we were building product for small companies, and I've been in a few big companies as well, like Zoom info, what I've noticed was the customer data that, or a better way to say this is probably voice of the customer, is not getting translated back into the product teams as much as we wanted it to be. We had to hunt for that. We had to go and work for that. That was the way that it was set up. Not necessarily

**[1:34]** because the organization wanted it that way, but it's how it was. That's the basic answer for that. So we started there with our first product. When we started the company, we thought about how do we bridge this gap between the go-to-market segment of customers, prospects, everybody's talking about what they want, et cetera, et cetera. And then we would bridge this gap to the research and development team, the team that's actually building the product. That's where we started with the first one. But as we went through the journey of building out that product, talking to customers and giving

### 02:08 — Why B2B support data is fragmented across channels

**[2:08]** it to customers to try it out, what we realized was even the customer-facing teams itself themselves don't have the ability to understand what exactly is happening with the customers. The scale of customer support, success, all those post-sales functions is too big to manage even. And especially when B2B is starting to scale up or go to the maturity of what we see today, probably scaled it up super fast after the 2020 era. What we're seeing today is an influx of customers going through Slack, email, Discord, five different channels. And then all the feedback is getting

**[2:51]** distributed, all the data is distributed across multiple channels. Nobody can manage that. Even the communication support teams cannot manage that. So instead of solving the larger problem initially, we thought, why don't we start solving the problem for the GTM teams itself or the post-sales teams itself? That's how we landed on what we have today, an AI-first customer support platform for B2B companies specifically built with account as the centerpiece of it. That's an interesting part that we figured is built because most of the ticketing platforms are built for horizontal use cases. If you take anything out there, it's more ticket is the center

### 03:38 — Account-first vs. ticket-first

**[3:38]** of that platform. But we see pre-sales or anything that until sales closure is always account, account, account. You have to keep account in your hands to cater them, pamper them throughout. But when we get into post-sales, that gets stopped. Account is nowhere to be seen. So we want to bring that back in as a positioning or as a way to do things in B2B. So that's probably a shorter version of how we landed here, the nuances still. Yeah, makes sense. And Tony on that, so current market when you started to that point, they were focused a lot on each individual ticket. When you're saying that, that's the centerpiece of their

**[4:23]** product. They were looking at a ticketing page and making sure the ticket was integrated with the right systems and all of that. You're saying that you're going account first so that you can pull in all these channels to one place. And again, kind of back to the data issue, is that the gap that you think AI is going to help with? And yeah, what advantage do you think I guess coming in with the account first approach will give you when it comes to AI? Yeah, it's when people start talking about support by itself, the default thought process goes into like, how do I solve a question

### 05:02 — Context over answers: what AI should actually do

**[5:02]** that's coming from a customer? How do I answer that question? So because it's all textual based and AI has the ability to look through a ton of data and then come up with an answer for a question. That's what you see in chat GPT. So by default, every AI company starts there, how to answer this question. But when it comes to B2B, what we're seeing is like, it's very contextual. You as a customer support or a customer success, anybody who's touching the customer post-sale has a ton of context or needs a ton of context. So AI can come in and look at all this data in the backend,

**[5:39]** maybe pre-sales data, call recordings, and all the other data points that are there in your CRM systems. Even the question answers that your humans have already delivered to the customers and got a thumbs up or got a five start from the customer, all that can be used to treat the account better, not just treat the ticket better. So what I mean by that is, is this account happy with all the tickets across different platforms. It could be happy with just having a good happy stakeholder. We see a lot of that. People buy stuff just because they like what they see,

**[6:19]** but the users might not love it. So how do you analyze that sentiment and bring it back into the stakeholders visibility? A champion might not be happy, but the users could always be happy. That's another scenario, specifically looking at that. A champion could change jobs. The new champion coming in might not be having enough context about how this buying process happened, where did we start, how is this product being used, et cetera. A lot of other scenarios like how is the customer actually aware of 80% of all the things that you have shipped so far. We've

**[6:54]** seen 80/20 rule happen a lot in B2B. 20% of the features is used by mostly 80% of the customers. So how do you make sure everyone is aware? All of this happens through various touch points, mostly through QBRs and quarterly reviews that happen from a CSM standpoint these days. But once every three months is not good enough for your customer to be like, hey, four times in a year, you're paying $20,000, $50,000 for a product. You talk to them four times a year, you have 30 minutes. How do you convey all of this? How do you get all of that within a limited 30 minute time

**[7:32]** period? So it's not happening as it should be. This is where AI comes in and looks at the scale across different platforms and help you communicate. Even your support teams get empowered to say, hey, we are seeing this pattern. We are going to send this to the product team and give them this pattern. We'll keep you posted on the update. That's a better way of supporting an account rather than just saying, hey, here's the answer for a question. We do not support this today. That's how we look at it. No, that's great. I think distributing the information to the right

### 08:12 — Product tour: Slack tickets and message grouping

**[8:12]** people at the right time, organizing the right information, especially in the B2B context, that account is the persona you're really trying to serve. So it's difficult to do that with the current solutions. I'm really excited to see how you pull this all together in Orca and show us how it's different than typical ticketing systems. Yeah, definitely. So what you're seeing on the screen is the Orca platform. I'll walk you through what it means. On the left side, what you're seeing is basically the account. So we'll get to the account. That's our centerpiece. This is

**[8:51]** the ticketing system. So we already have a ticketing built into the system where you can see and manage tickets within the system as well. We also have a piece where documentation is automated for most of the cases. To communicate back to customers broadcast and general settings, we also have the AI agent where if you want to dig deeper into specific scenarios, specific patterns that you want to identify, we can enable that too. So I'll start with Slack. What we are starting to see is a lot of B2B companies are starting to see or starting to bring customers onto a Slack Connect

**[9:34]** channel. So what you're seeing on the screen, I'm just simulating a customer here. So I'm just going to send message as a customer from here to my customer Connect channel with Orca. So it's just a problem that I'm seeing and hoping to see if this bug is removed. So what happens is since Orca is already present in this Slack channel, it keeps looking at all the messages that is coming in and keeps track of that as tickets. So if we go back to Orca, you would see this ticket is coming in from Slack here. And you can start responding to the ticket from here itself. You have basic

**[10:17]** description that's AI generated, what is happening exactly in the ticket. It's auto assigned to Jiren, one of our teammates, and the status is like all of the ticketing is managed there. Now, one pattern that we usually see is customers don't always go and respond in threads when they start looking at Slack. So they could be coming and saying, hey, somebody else could be coming in and saying, app updates could have a problem. They'll just send it as a message itself. This is one of the smallest applications that we have seen as AI is we are looking through a lot of messages and we

**[10:58]** are figuring out what is the context, what is the actual context from this customer started talking about this problem. We keep grouping that into one single place where we can keep track of things that are related to this problem where you would go and say, hey, we have similar messages coming in, AI would auto categorize them, auto group them, and then start looking at it. And you can start answering here, looking into it. This is a basic way to start a conversation and then you can send this across to your team and start looking into it. This is where our second part of the system

### 11:42 — The triage workflow

**[11:42]** comes in where you start sending this across to your team. It's a little bit difficult to convey what the customer is going through, especially when this conversation goes beyond your control, right? Customer keeps talking about it. These are the problems, et cetera, et cetera. It keeps coming in a lot. That's where we have a workflow within Slack itself where you can automate the triaging. So what you're seeing on screen right now is the Orca platform. So you might have seen Jaren is assigned for that particular ticket, ticket 232, but what Orca does is it auto triages the ticket. It brings in the account, which account is about

**[12:27]** what is a priority, what is a type of it, and with an original message context into a single Slack triage channel where your engineering team, your product team can come and see the whole context without you sharing anything, without you being able to take all the context that you want. You want to probably give everything to it. Whatever that happens in the customer conversations is always triaged in a Slack channel as well. This is a workflow that we have in our system. So your product team don't miss out anything. Your engineering team don't miss out anything, or even

**[13:03]** your leadership don't miss out anything. But that's where we start looking at B2B as a customer support. Let me pause there. It's a complex workflow to start with. I'll take a step back as you go through this and then explain how this is set up as well. I really appreciate the little things and intentionality, and it shows when you've actually been in the field solving these, just grouping another DM into the same ticket and having the context of knowing that it's grouped together. Because people communicate all different ways, and it always bothers me when people are

### 13:42 — Team threads and replying to customers via emoji

**[13:42]** slacking outside of threads. But sometimes you don't know if it should be a thread yet. So I think that is a huge, huge advantage. I know it's a small thing, but those little things go a long way. Yeah. Another thing that we facilitate from here itself. So this is our Slack, and we want our team to be able to discuss things here as well. So whenever a ticket comes in, ticket 232, this becomes a discussion thread with my team. So immediately I can tag anyone in my team, and how are we doing here? Any updates? This thread becomes my team's Bible on how to manage this

**[14:24]** ticket. So this is like becoming a longer thread. I can talk to my team. I can just simply tag people. None of this goes back to the customer. But let's say I'm just going to simulate myself here. But let's say my team member has a question. Hey, I have something to ask to my customer. Now, your team member has to be in the support platform or to be in the loop, regardless of whether it's email, Slack, whatever. You've got to be in a touch point with your customer to interface. So whenever my team wants to communicate with the customer, what they can do is they can

**[14:58]** come here. They can use a pre-determined emoji. This is again a setting in our platform. And Kira, do you mind sharing a quick video about this? So this particular message that you've seen, pre-labeled, Google can send this message or anybody in my team can send this message from here. And it goes back to Kira. So it goes back to the original thread. And it goes back as a question. And that enables my team to easily communicate with my customers. And also, whenever that happens, the major problem that we hear from customers is like, oh, do I know what my team is talking about?

**[15:42]** Do I know what is exactly that they're talking about? Because the ticket's volume can be high. You don't have to keep track of things in Slack. It always comes back here in the system. So you don't have to worry about what your team is talking about. You will always have that track in the system. So you never worry about what's missing there or what's happening there. And whenever you want to go back to the original message, this is where the source comes in. The source clicking on the original message directly takes you to the customer's channel and exactly where the customer is talking about this problem. So it is all linked together so

### 16:21 — Multi-channel: email, Discord, and suggested responses

**[16:21]** that your Slack is never getting missed. Now at this point, all our customers can mute their customer Slack channels and just listen to either one Slack channel or just look at Orca to be in the whole spectrum of listening to customers and understanding this. That's just the Slack part of things where we start. This is one of the focus points for our product as well. Because we see a lot of customers bringing their customers onto Slack. Slack has become a high-touch way of doing customer support for B2B specifically. That's where we started working on this. But as we scaled up,

**[17:04]** as we started seeing more and more patterns, we saw, hey, email is another way of looking at customers. So this is coming in from emails. And we started seeing Discord as a channel as well because you see a lot of tickets coming in from community, a lot of tickets coming in from people who really want to understand. So I'm just going to jump into Discord community here quickly. So this ticket 231 came in from one of the communities that we manage. And you can see it's fairly technical. It has a code snippet in it. It has some of the errors in it, et cetera, et cetera.

**[17:41]** And you also probably are seeing suggested response here. So what we do here, especially for technical tickets, is whenever we get a technical ticket, your support team might not be empowered to kind of have the context. And what we also say is it needs a lot of context on the implementation B2B end. Dig deeper into all of this. As we could dig deeper into this, just as I shown you, the technical person or non-technical support guy can just simply use this AI response. Hey, here is the documentation. And here is what I found from documentation. Can you check this as we go through this internally? This is a simple message that my technical,

**[18:33]** non-technical support person can send across and assign this to the CTO or somebody who's in charge of the technical stuff and enable them to look through this very fast. And meanwhile, the customer would be happy that they've gotten a response. That is where our AI comes in. We believe in terms of enabling AI to suggest answers rather than just auto answering, especially in the B2B, very technical, very contextual questions. That's where our AI suggestions come in as well. So this is the starting part of ticket management and we still have emails, all of that. But the core part, as I mentioned, in the starting point

### 19:21 — The account timeline and sentiment view

**[19:21]** is account base, right? All of this is tickets, regular, some things that you see in any platform out there. But the difference comes in when you start looking at the account section of things. So this is where we come in as a system and we track everything. So the timeline that you're seeing here tracks everything. So the Slack messages that you have, the tickets that are getting created, the responses, all of this. And this enables you to track the engagement in a much deeper, much horizontal level, the sentiment of the customer on a more horizontal level. And whenever you want to jump into specifics, you always have the sources here itself at an

**[20:08]** account level. So you never have to worry about whether I'm keeping track of things beyond tickets. It's always account level. Everything that your account is communicating with, you can keep track of that, go through the history of the account, understand where we lost or where we won. If I want to look at March specifically, I know the communication is like in the early days and probably towards the middle, I haven't touched base with them towards the end of the quarter, which probably is a mistake. Then if somebody comes and asks me, "Hey, what is happening with

**[20:42]** this particular customer?" I can always say, "Oh, this communication is a little bit broken." I can simply trigger a communication from here itself by going into their Slack channel and say, "Hey, how are things going? How is everything happening on your end?" Yeah, that was really a really cool view on the account level.

### 21:03 — How AI responses are generated (GitHub + docs)

**[21:03]** Sort of aligned with this and what you showed before on the AI responses. How are you generating the responses? What information are you looking for right now to give that type of suggestion? So there are two ways of... It's a fairly high touch setup that we do when we want to enable AI responses because what we have seen a lot of companies do is they'll just give you, "Okay, go and tag in your documentation and we'll take it from there." That's where I think the quality gets dropped a lot and the responses that you get is not really relevant for the context. So we analyze the customer initially. So if it's a technical customer, we're going to...

**[21:53]** There's some open source code base. So if they can give us access to their internal GitHub controlled way, we also understand their code bases. We go in technical. Our AI agents go in and understand the folder structure of those, how it's been getting implemented. That is the starting point for us. We also look at documentation. So that's where our documentation piece comes in. We would take in any documentation that you have today, but what we're seeing is people don't have all the complete documentations. So whenever you start using AI, you would see almost all the

### 22:30 — Loom-to-docs: closing the data loop

**[22:30]** documentations are like, "Okay, this is not great." But what we have figured is, okay, if we can enable somebody to create documentations within a few seconds with AI, some things that we do specifically just for our system. If you want to bring your documentation to our system, we have that, but that's not a mandate for us to work on top of documentation. But if you do not have a documentation and just let's say you have only a loom video, I'm just going to quickly take this demo video here, you can just simply go and enable this loom video to create a documentation for you

**[23:08]** out of the blue. So it's going to come back. I'm just going to quickly move into one of the created ones. It's going to come back after creating to me. So something that I've created here is it's this documentation was created totally from a loom video, including the screenshots, no human touch at all. It has step-by-step instructions. It has 11 screenshots. It has what do you do with a screenshot, how to configure things in the basic configuration. So this is fully created from a loom video. So we enable two things. One, go into deep technical stuff whenever you

**[23:44]** want to. That's a hand-holding stuff. When you think documentation is not sufficient enough for AI to answer, or when you see low quality, you can come here and just paste your loom video, just paste your demo videos and enable your documentation to be much better, much more comprehensive and go deeper into each of these use cases because loom is something that every company kind of like uses today or one of the video platforms where you have videos recorded everywhere, especially for customer communication. You have caught a lot of videos is what I see. Now, if you were to take all

**[24:20]** of that video and then convert into documentation, the cycle gets completed, the data becomes better. So instead of garbage in garbage out, it will become quality in quality out. That's our way of disclosing the loop and in data as well as giving the best answers from AI agents. That's a huge feature. I think even if we're thinking about us at LeanScale, we loom every single thing we build for a customer. We film a loom for it. And a lot of that is just kind of living in that video. It's not put into documentation that could train our own models as well.

**[24:59]** So I think this is huge and just baking that into the workflow to continually train the model based off of probably a lot of people are sending these looms to customers, right? So just closing that loop and then having it feed the model, that's huge. Yeah, sending loom, one of the biggest use cases of like quick video recordings like loom is to send it across to customers, right? I mean, quick recording, quick take, copy the link, send it across to customers. Now, you can just use that for improving your documents itself. You don't have to worry about the problem with documentation

**[25:35]** that we see very often is nobody owns documentation piece in a B2B lifecycle. So is the product person owning that? Is the customer person owning that? The customer success manager owning that? Nobody has ownership. If you ask like five people, all of them say, "I don't own it." So the problem is nobody wants to write this thing. And it's where we come in with our unique angle and you'd see a lot of loom videos getting converted into documentation as you go forward. Wow. That's awesome. And we talked about this a little bit, but this is sparking some ideas

### 26:14 — AI beyond answering: reporting and the in-house agent

**[26:14]** for what could be next. How are you thinking about leveraging AI and the products with already a lot of these foundational things you've already built out? Yeah. One of the things that we really believe in is whenever you start looking at this, I think this is going to keep repeating in my conversation across, people start thinking about AI just answering questions. That's not the way to like properly use AI or like, I wouldn't say properly. There's more to it. There's more to what you can do with AI. And when you look at support or customer post sales, especially in

**[26:57]** B2B, there's a lot of backend that is happening. So the backend includes understanding what the stakeholder needs. Like I need to report back to my manager, my leadership team, my customers. Everyone needs what exactly are they looking into? What exactly are the problems that we are seeing across? Probably like email as a channel, Discord as a channel, Slack as a channel, and maybe chat as a channel. Where is my documentation lacking clarity? All of those questions come up from leadership. Now what happens is the customer support people or whoever is like manning the ground

**[27:36]** gets loaded with these questions and they cannot have enough context on what to do. They don't have the time to manage this. That's one of the places where we see AI. And this is a starting point for us. We have an agent in house as well. This enables just an agent. So what we are looking at is like, I just asked a question, list all the accounts based on tickets and group them by ticket count. Now for you to get this in the past, you had to go and figure out like how to do analytics on top of the data that is reported back to Snowflake and bring that data back into Tableau and

**[28:11]** like generate a report. This table is like taking three seconds. Any question that you have on top of data, like give me, show me, I'm just going to ask this, show me all the requests from Slack messages in the last two weeks. To find this data and give this to your product team or to your leadership team and seeing, hey, this is what the pattern that I'm seeing today for a support person or a support manager used to at least take like half a day or even maybe one full day of work. This is where a lot of backend stuff gets automated. You can write workflows to automate,

**[28:50]** send this across every two weeks to my leadership, my product team, my engineering team, just so that I'm clear on my end. I've communicated properly. You have kept track of all of these things. This is where I think AI is going to shine the most, where you can have visibility across a lot of data and you can see what are the things that are happening across different accounts as AI comes back with all of that. I have a ton of history on my questions, everything that's happening there. I keep asking AI, hey, what do I look at for my priorities in what are my customers talking about?

**[29:28]** This is one major aspect where people are not talking enough, especially when you go into support. I hear this a lot because when we say, hey, we are a support platform, people are, oh, do you want to answer questions? Do you have AI to give you suggestions on answers? Even people get to suggestions, but they think support always relates to answering questions, which is where we come in and bring in a differentiation. Yeah. 100%. 100%. That's awesome. Yeah. That's awesome. One, another thing that I think it's really relevant is the workflow system. All of the system defaults that you've seen or the base layer that you've seen, it has an underlying

### 30:18 — Workflows + AI for B2B

**[30:18]** workflows engine that's working out for you. Some of the things that we hear from a lot of B2B customers is now workflows plus AI is the key in B2B is what I see. Workflows plus AI using the components to deliver what really, really matters. One of the workflows that I've shown in this demo initially is the triage workflow, where you can enable your team to respond, enable your team to be access to the customer conversations, et cetera. Another one interesting part is the routing workflow, where we have very specific routing actions based on conditions that is time zones,

**[31:01]** conditions that is tickets, et cetera, to build a detailed workflow system for routing. We are also bringing in AI specific workflow. So let's say if your customer is not happy, sentiment is really bad and you are seeing a lot of bad patterns across your customers, escalate this to a manager is a routing workflow that AI can bring in. It is again, the backend stuff where AI can help a lot. SLA being breached for a bunch of times and customer is not happy, alert me in this particular channel in a particular way that I always look at the customer when SLA is getting praised. So these kinds of workflows is what I think builds the B2B system of the

**[31:48]** ticketing management or like customer support for B2B rather than just answering questions that I think is where the future is going. I love what you showed with the workflows. I think orchestrating the SLA's assignments, creating everything automatically is really is what's going to help a B2B company scale. And I really appreciate everything you shared. I think you've shown a new way of thinking about not just support, but getting your product data, leveraging what you've already done before. So the looms, the documentation, building responses, but then using those responses and sentiment to feed valuable data to the product team. So you

**[32:36]** can do what every company is trying to do. You're trying to build the best product possible to serve your customers in the best way. And sometimes it's so hard to get that data. But I think you've built a platform that does this in a really elegant way that helps integrate the support with the product, helps take care of your customers while also feeding that data back and then automatically building a lot of the components you need so you can actually scale. Tony, I'm really, really excited for people to take a look at this. And I'm excited. I know this is just the beginning

### 33:13 — How to get started with Orca

**[33:13]** of Orca too. So I'm excited of what's coming next too. That's very kind of you. And we're just getting started. That long way to go. And if anyone wants to get started, you can just go sign up directly on Orca. And it's a really slick process. But is that the best way to get things going for anyone that's interested? Yes. One, since you've already mentioned, so what happens there is that's one workflow that we want to ship out to customers as well. We're testing it on our end that if there is somebody who's signing up at get Orca.ai, they would by default get a Slack notification to join the customer channel. You don't have to wait for

**[33:57]** us to reach out. You don't have to come back and ask us, can we have a Slack channel? By default, you get a Slack invite to the email that you're signing up with. And then you just join that channel. There'll always be me and my people there. Our team will always be there in Slack. That's one workflow that we are hoping that we can ship to customers as well. That is where we start. So just sign up. We'll see you on Slack. Perfect. Perfect. Awesome. Love it. Well, thank you, Tony, so much. Appreciate it. And can't wait to see what you guys build next. Yeah, great. Appreciate you guys having me here. Thanks.


---

_LeanScale Podcast Knowledge Hub. Free to quote and cite with attribution to The LeanScale Podcast (https://www.leanscale.team)._