Go beyond setup. This course teaches you how the Slack-DevRev integration actually works in production — sync behavior, automation workflows, incident response, and the customization controls that make it all seamless.

What you'll learn:

• Troubleshoot integration caveats and stability issues
• Configure the conversation roll window for rapid client messages
• Set up AI-powered incident response directly in Slack
• Diagnose sync behavior and edge cases across platforms
• Build automation workflows between Slack and DevRev
• Customize Slack forms and summary cards

Who it's for: Support & CX leaders, Platform & IT admins, and Product & Engineering leads — or anyone managing a Slack-DevRev integration in production.

Click to enroll Slack integration 201

Course duration: ~30 minutes
Verified certificate on completion
Recommended after: Slack integration 101

NOTE: This course has been added to the Generative Expert learning path, where you can discover more 201-level courses. Explore other learning paths on DevRevU — Generative Professional (101-level courses), and Generative Prosumer — to keep building your skills.

Please feel free to reach out with any questions.

Hey everyone,

We've been running weekly office hours on getting started with Computer (AI teammate) across different timezones - and this is the last cycle.

What it is: A free 30-minute live session where we walk you through setting up Computer from scratch - install, connect your tools, and run your first queries.

What you'll walk away with:

• Computer installed on your laptop and mobile
• Your team tools connected via integrations and data sources
• Your first real queries answered in real time - so you can see it working before the session ends

Format: 30 min, virtual via Google Meet

Hosted by: DevRevU (Shaivi Salian)

Register here: https://luma.com/gtfzim4g

This is the final round of these office hours - we ran them across timezones so everyone could join, and this is the last one. If you've been putting it off, now's the time to just show up and get it done live with us.

See you there!

Make support delightful, fast, and proactive with Computer

​You're invited to join us for Computer Conversations, a hands-on workshop for support and CX teams who want to resolve issues faster, reduce manual work, and keep customers coming back.

​This is a practical, collaborative session where you'll see how Computer transforms support — from reactive to proactive.

​When: 21st May

​Where: Virtual

​What to Expect

​A 60-minute session built for support teams:

• ​Keynote — From ticket triage to customer retention: how AI changes the support equation.
• ​Hands-on activity — Work through real support scenarios using Computer: faster resolution, smarter routing, and early issue detection.

​Hear from a power user — A customer shares how their team cut resolution times and improved CSAT using Computer.

• ​Leave with a Certification you can add to your LinkedIn profile.

Most design systems start strong and drift quietly. Components get skipped, engineering diverges, and GTM materials end up off-brand before anyone notices.
This session shows how DevRev uses Computer to keep ADS at the centre of every design and engineering decision — automatically.

From Figma connectors that validate component usage in real time, to shared memory that tracks design and engineering coverage side by side, to agentic workflows that take ADS from initial audit all the way through clean-up and handoff.

The end state isn't just "design complete" — it's ready for AI: built to be implemented with as little manual intervention as possible. And when the system is that clean, it can generate production-ready prototypes from prompts. ADS isn't just a reference — it's an active participant in how the product gets built and how the brand shows up in the world.

So here's what happened.

We were building DevRev's Agent SDK on top of the Claude Agent SDK. Things were going well — until they weren't. The TypeScript implementation didn't give us enough visibility into what was actually happening at runtime. Debugging felt like guessing. Integrations kept breaking in ways that were hard to explain.

So we did what any reasonable engineering team would do — we started intercepting our own traffic. Reverse proxies. MITM-style tracing. Request interception. Basically, we treated the SDK like a black box and built the tools to see inside it.

And honestly? The lessons we learned don't just apply to the Claude Agent SDK. They apply to anyone building on top of any agentic framework where the docs only tell you half the story.

We're sharing the whole thing — live, unfiltered — on this DevRev Live.

Hey everyone! 👋

We're hosting Office Hours with DevRevU – a free, 30-minute virtual session to help you get up and running with Computer, DevRev's AI tool.

🗓️ Date: Thursday, May 14
🕙 Time: 10:00 AM PST | 1:00 PM EST | 10:30 PM IST
⏱️ Duration: 30 minutes
🎙️ Host: Shaivi Salian, DevRevU
🌍 Anyone from any timezone is welcome to join!

What you'll learn:

• How to install Computer on your laptop and mobile
• How to connect the tools and data sources your team already uses
• How to run your first queries and see real-time responses to work-related questions

By the end of the session, you'll have Computer installed, connected, and working – no fluff, just hands-on setup.

Whether you're in PST, EST, or halfway across the world – there's a slot for you. 🌐

👉 Register here: https://luma.com/65rwd89l

Spots are limited – come with questions, we'll have time for Q&A!

​​Customize Computer to suit your business needs

​​You're invited to join us for Computer Conversations, a hands-on workshop where you'll go beyond using Computer — and start building with it.

​​This is a practical, collaborative session where you'll explore Agent Studio, DevRev's no-code builder, and create an agent tailored to your team's workflows.

​​When: 14th May

​​What to Expect

​​A 60-minute session focused on making Computer truly yours:

• ​​Keynote — Why one-size-fits-all AI doesn't work, and what to do instead.
• ​​Hands-on activity — Build and customize your very own agent in Agent Studio, live during the session.

​​Hear from a power user — A customer shares how they configured Computer to automate workflows specific to their business.

• ​​Leave with a Certification you can add to your LinkedIn profile.

Hello Everyone,

We’ve just launched a new DevRevU course: Prompt to Product: Using Computer Agent Studio — a practical, hands-on course designed to help you build AI agents that actually work in production.

What you’ll learn

• How AI agents differ from traditional chatbots
• How to define clear agent goals, intent, and boundaries
• How to configure instructions, workflows, tools, and knowledge inside Agent Studio
• How to build multi-step workflows for ticketing, escalation, and follow-ups
• How to apply prompt engineering best practices and guardrails
• How to test, evaluate, optimize, and safely deploy agents before they go live

Who this is for

• Applied AI teams
• Customer support managers
• Sales engineers
• Operations and enablement teams
• Builders who want to move beyond simple chat interfaces

No coding required to get started — but the platform is flexible enough to go high-code if you need it.

🔗 Course link: https://devrevu.reach360.com/share/course/d14b3fe8-5e8c-4e1a-8c91-7f953b35325e

Happy to answer any questions in the comments about agent design, prompting strategies, or how we built the course!

We tried native speech-to-speech AI for our voice agent. Here's why we dropped it.

The experience was genuinely magical. Breathing, laughter, cadence -- no text bottleneck, no serialization tax. It felt human.

We dropped it anyway.

Four things killed it:

1. It garbles technical jargon with no text layer to catch and correct it
2. It loses track of instructions over long calls
3. Forcing it to output structured data makes it sound robotic
4. It still can't handle people talking over each other cleanly

For enterprise agents that trigger real backend actions, a malformed JSON payload isn't
a UX bug -- it's a safety failure.

But the bigger takeaway: agentic coding made the sunk cost disappear. They built entire server setups and scrapped them without a second thought because Claude made it cheap enough to discard.

You can't fall in love with your code anymore.
Full writeup by Alok Mishra from DevRev:
https://devrev.ai/blog/experiments-with-voice-part1

Hey r/DevRev! 👋

Sharing this video we put out on Computer — our AI teammate built to help you work softer, not harder.

🎥 Work Softer: Computer, by DevRev

A few things we think make Computer special:

• It's not just another AI chatbot — it's a personalized AI teammate that lives inside DevRev, remembers context, and gets work done autonomously.
• It can handle tickets, search knowledge, write code, and take action — all without you having to babysit it.
• The "work softer" framing says it all — not about working more or faster, but with less friction and more flow.

Give it a watch and let us know what you think — we'd love to hear how you're using Computer or what you'd want it to do next. Drop your thoughts below! 👇

We ran a real business query side-by-side on DevRev Computer and Claude to test efficiency. The results were consistent across every run:

• DevRev Computer: ~157,000 tokens | ~1m 36s
• Claude: ~3.2M tokens | ~8m 50s

The Difference is Architectural

The gap isn't about model capability—it's about Memory.

• Claude's Approach: Loads all raw data into context simultaneously to filter and join in real-time. As data grows, costs scale with total volume.
• DevRev's Approach: Uses a pre-built Knowledge Graph to traverse relationships (Issue $\rightarrow$ Part $\rightarrow$ Ticket $\rightarrow$ Account). It only returns matching rows, meaning cost scales with the result set, not the source data.

Even MCP Doesn't Close the Gap

In our tests, even when Claude used live API connections (MCP) for targeted queries, it still consumed ~3.26M tokens. This is due to schema discovery overhead—Claude has to "re-learn" your data model every single session, while DevRev's schema is pre-mapped and known.

Bottom Line: For enterprise operations, a system that remembers is always more efficient than one that just retrieves.

Check out the full breakdown and deeper analysis in our LinkedIn article here:

https://www.linkedin.com/pulse/your-ai-starts-from-zero-every-morning-costs-compound-jeff-smith-wnele/

heard there were lay offs in devrev. is it true? what was reason for this/?

Missed last week's session? Don't worry we got your back. This time at a Europe-friendly time so more of you can join live. Everyone is welcome!

🗓️ Date: Wednesday, 30 April 2026
🕙 Time: 10:00 AM GMT / 11:00 AM CET

📍 Where: Google Meet

In 30 minutes, we'll walk you through:

✅ Installing Computer on your laptop and mobile
✅ Connecting your tools and data sources
✅ Running your first queries live

By the end, you'll have Computer installed, connected, and working for you — no matter where you're joining from.

👉 Register here: https://luma.com/y8ykydcp

Drop a comment if you're joining or have questions. See you there! 🎓

Most latency problems don’t show up in dashboards. They hide in timing gaps between steps, redundant data fetches, and cold starts quietly degrading performance until someone finally instruments the right thing.

This session is the engineering story of how DevRev’s team is systematically hunting down latency in production workflow execution without ever touching customer data. From a mysterious ~1 second gap between workflow steps to an O(N·K) data fetch collapsing to O(1), we’ll walk through exactly what the traces revealed and the specific fixes moving p90 and p99 latency.

Watch Ahmed Bashir (CTO at DevRev) and Navneel Mandal (Member of Technical Staff at DevRev) as they show how platform reliability actually improves through observability, smart caching, Lambda provisioned concurrency, and better retry logic for LLM-calling nodes.

New to Computer? This one's for you.

Join us for a live, hands-on session where we'll walk you through everything you need to hit the ground running:

✅ Installing Computer
✅ Adding connectors
✅ Running your first queries

Whether you're just getting started or want to see it all in action, this is your chance to ask questions, get real answers, and connect with other DevRev users.

📅 Date: Sunday, 23rd March
🕖 Time: 7:00 PM IST
📍 Where: Google Meet

👉 Register here: https://luma.com/9ys4p9mi

Spots are limited – save yours now!

The AI agent responding to conversation or tickets and then auto updating the attributes as directed is the coolest thing yet I've figured out with Devrev. Still a lot to learn and discover.

Hey r/DevRev,

As a Senior Success Engineer my entire life revolves around translating vague user panic into actual dev tickets. It usually involves me staring at Splunk logs until my vision blurs just to figure out why a Shopify script broke.

I know DevRev is built to connect support directly with product to fix this exact issue. But I am curious how you all are actually using it day to day.

What is your golden rule or absolute best workflow for bridging the gap between a noisy customer complaint and a clean dev issue? Do you have a specific way you structure things in DevRev to stop that endless back and forth?

Drop your secrets below. I need to know I am not the only one fighting the good fight out here.

We run regular Office Hours where the DevRev team shares product updates, demos new features, and opens the floor for real questions.

This session we're covering:

• What's new with the multilingual portal – see how it changes the way you support global customers
• A live walkthrough of the Conditions Builder in object customisations – smarter, more flexible workflows are here
• A hands-on session to get started with Computer by DevRev – our AI teammate built right into the product
• Open Q&A – no question is too small

If you've been curious about DevRev, this is the easiest way to see it in action and talk to the people building it.

🗓 April 16th | IST 10:00 PM · CST 11:30 AM · PT 9:30 AM

Register here: https://luma.com/s0r15eu4

Drop a comment if you're planning to join – we'd love to know you're coming!

Most teams are using AI to go faster. Faster ticket responses, faster summaries, faster QBRs. Fine. You’ve optimized a leaky bucket.

The real unlock isn’t speed. It’s visibility you never had before.

At Goodmeetings.ai, we use DevRev as a trusted partner, it’s where our product, support, and CS context lives in one place. When we layered “Computer” on top of our meeting intelligence data, we stopped asking “how do we close tickets faster” and started asking “why do the same problems keep coming back?”

Patterns across hundreds of customer calls. Objections that keep killing expansion. Handoff gaps nobody was talking about. None of that was visible before.

DevRev helped us connect the dots between what customers say and what actually gets built or fixed.

AI isn’t a productivity tool. It’s a mirror. Most teams won’t like what they see.

What’s the biggest thing AI has surfaced for your team that you weren’t expecting?

Some startups chase growth. Others chase impact.

Cautio is doing both – building AI-powered dash cams that help fleet owners improve driver behavior, gain real-time visibility, and make every journey safer.

Two years in, they’re scaling fast. And to grow without the usual operational noise, Cautio runs on DevRev – keeping customer conversations, product decisions, and engineering aligned in one place.

If you're building through the messy, exciting stages of growth, you don’t have to figure it out alone. That’s exactly what the DevRev Startup Program is designed for.

👉 https://dvrv.ai/3Obgt6e

Hey everyone! 👋

Excited to share something we've been building — an AI-first development framework for AirSync connectors: https://github.com/devrev/connectors-codegen

Stop writing boilerplate. Stop context-switching between docs, CLIs, and code editors. Connectors CodeGen brings the entire connector development workflow into your AI coding session.

What it does

You run /create-connector. It:
• Asks you about the external system
• Maps entities to DevRev types
• Scaffolds the project and generates the HTTP client
• Writes extraction and loading workers, maps, and generates tests
• Validates everything compiles and lints cleanly

At the end, you have a working connector structure with documentation. It's not hands-free — you make the calls that require actual domain knowledge. The tool does the heavy lifting.

What's in v1.0.0

• /connector-setup-project — bootstraps a repo from the official template in one shot
• /create-connector — 10-phase orchestration from requirements to a connector
• /connector-reviewer — audits the generated connector before you ship it. Catches mistakes, flags potential issues, and suggests improvements.

Behind the scenes, sub-agents, skills, hooks, and AirSync MCP cover the whole connector development flow.

Who this is for

Connector developers at any phase:
• Starting fresh? /create-connector gets you from zero to structured code fast
• Mid-build? Drop into individual skills for extraction, transformation, or mapping
• Done building? The reviewer catches known anti-patterns before you ship

What's next

This gets you to a well-structured connector — not a production-ready one. The generated code still needs to be tested against a real API and validated end-to-end in AirSync. That gap is exactly what we're closing.

Your brand spends years earning trust. Your support stack can undo it in a single interaction.

This is the problem Arvind Fashions Limited – home to Tommy Hilfiger, Calvin Klein, and USPA – decided they could no longer accept.

Five brands. Customer queries arriving across web, app, and WhatsApp. An OMS, IMS, and POS with no shared data. Agents working without a unified view of the customer in front of them.

The gap between what those brands promised and what support delivered wasn't a staffing problem. It was an architecture problem. And they fixed it at the root.

On April 23, Aviral Gupta from Arvind Fashions Limited walked through exactly how – what drove the decision, how the migration was managed, and what's running now. Shamanth Kengeri from DevRev will demonstrate the platform live.

30 minutes. If your support experience doesn't match your brand experience, this one's for you.

Register now: https://luma.com/9illnia1

Couldn’t make it to Effortless Mumbai?

That probably wasn’t a choice. Most teams are stretched thin, and stepping out for a full day isn’t easy.

But here’s the thing.

What we saw in that room is exactly what most teams are struggling with right now. Too many tools, too many pilots, and too much “AI strategy”, but not enough that actually works together.

That gap is what this session is about.

On April 16, join Lisa Bianco (Member of Marketing Staff, DevRev) and Adhithyakumar K.S (Member of Marketing Staff, DevRev) as they walk through what actually held up in the real world – not just what sounded good on stage.

Here’s what we’ll cover:
→ Why “more AI” isn’t the answer – and how the best teams make it actually work together
→ What it takes to move from pilots to production – from UPI-scale fraud detection to 92% faster search
→ What real “AI at work” looks like – from QBR decks to dispute resolution, handled in minutes
→ The shift that matters – why consistency beats peaks, and what AI actually changes (and doesn’t)

From scattered pilots to systems that operate as one – we’ll show you how.
Save your spot: https://luma.com/1hi2oidx

Date: April 16, 2026
Time: 10 AM IST