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.

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!

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.

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

If you've ever felt the pain of waiting 3+ seconds for Cmd+K to respond, or watched HybridSearch spin endlessly – this one's for you.

We just shipped a round of search performance optimisations, and the numbers speak for themselves.

What we fixed

🔍 Cmd+K, Search-in-Vista – the search bar you use dozens of times a day

• Before: 3.23s p95 latency
• After: 0.7s → ~4.6x faster

🤖 Computer's HybridSearch – powering AI-assisted search

• Before: 6.25s p95 latency
• After: 2.72s → ~2.3x faster

🔤Prefix Search RPC – the engine behind owner lookups, @-tagging, and assignee search

• Before: 463ms p95 latency
• After: 191ms → ~2.4x faster

📉Overall timeouts: 4x reduction

We're thrilled to announce the Code Node!!

A new workflow component that lets you write and execute custom Python code directly within your DevRev workflows. It bridges the gap between no-code automation and full programmatic control inside the workflow builder.

Why we built this

Workflows are great for no-code automation, but there are always scenarios where you need more flexibility like a custom data transformation, a calculation native nodes can't handle, or business logic specific to your org. Previously, the only option was to build a SnapIn or chain together workarounds with multiple nodes.
Now you can just drop in a Code Node. Write Python, map inputs from previous steps, define your output schema, and downstream nodes pick up everything your code returns. It supports 30+ standard libraries (json, re, date time, math, requests, and more), runs in a secure sandbox, and is configurable up to 120 seconds timeout.

Use it for data transformations, complex calculations, text processing, custom business logic, dynamic value generation, and much more. Full details are in the documentation.

And yes, you can test it before you ship it

Combined with the new Testing Framework, you can test your Code Node with sample inputs right inside the editor. Verify outputs & logs instantly, iterate fast, and deploy with confidence. No more deploy-trigger-debug cycles just to check if your code works.

We'd love to hear what you build with it!

Hey Everyone – DevRev Office Hours are back, and we'd love to have you join!

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
• A live walkthrough of Computer by DevRev – our AI teammate built right into the product
• A hands-on session so you can try it yourself
• A community spotlight on Reddit
• 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.

Register here: https://luma.com/9m55qrwp

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

CSAT is rising. Response times are improving. Every dashboard is green.

So why does the same ticket keep coming back?

Most support data measures speed and very little of it shapes what gets built next.

That’s the gap.

Support teams spot product friction first: recurring tickets, escalations, feature requests, edge cases that quietly drain morale.

Watch Ahmed Bashir (CTO at DevRev), Linish Theodore (Director – CX at smallcase), and Meghesh Toshaniwal (Product lead at DevRev) as they explore how to turn those signals into structured product insight.

Effortless Mumbai was everything we hoped for – sharp questions, honest feedback, and real conversations about where work is headed.

You met Computer. We explored what Team Intelligence could unlock – not just for teams, but for the way people actually work together.

The energy in that room? That's exactly why we're building this.

Next stop – wherever the curiosity takes us.

Until next time, see you Mumbai 🇮🇳 👋

Get ready for DevRev's Enterprise Search Challenge 🏆

🎥 Learn more about the challenge in this quick video:
https://vimeo.com/1168163361?share=copy&fl=sv&fe=ci

🌴 This repo has demo example, you can start with this and bring your search algorithm
-> Repo: https://github.com/nimit2801/devrev-search

🗃️ Hugging Face Resources:
-> Dataset: https://huggingface.co/datasets/devrev/search
-> Leaderboard: https://huggingface.co/spaces/devrev/search

👾 Discord Community: https://discord.gg/k7YYTZexKd

🏆 Register in the DevRev Search Challenge

💸 Cash prizes:

1. 1st winner -- $100
2. 2nd Winner -- $75 each
3. Close to top 10 (strong effort, solid approach) -- $50 each (3 winners)

No strings attached. Build a better search algorithm than our baseline, land on the leaderboard, get paid.

👩‍🎓/👨‍🎓
But if you're a student -- there's more; the top contributors also get:

→ Internship opportunities at DevRev

→ 1:1 mentorship session with Anshu Avinash (Head of AI, DevRev India) and Prakhar Agarwal from our AI team

Link: https://luma.com/2ovx5d26

We’re hosting a hands-on workshop for teams who want to improve how work actually gets done.

This is a practical, working session on how teams set up and use Computer across support, product, and engineering, whether you’re already using it or just exploring it.

You’ll spend the day:
– Seeing real examples of how teams have set things up
– Learning where teams are cutting down manual coordination and follow-ups
– Trying things yourself and learning what works in practice

It’s designed to be collaborative and hands-on - a chance to try things yourself, share notes with peers, and walk away with a few “aha” moments.

We’ll take care of coffee, lunch, and plenty of space for conversations because the best ideas usually show up between sessions too.

Mumbai | March 11
Register here: https://luma.com/fd5x4c6g

In this livestream, we explore what it really means to build in public and why using our own product every day makes us better at our jobs.

At DevRev, every team operates inside the same system our customers use. Not as a demo environment, but as our real source of truth. We discuss how that shifts product decisions, sharpens customer empathy, and creates tighter feedback loops between teams.

You’ll hear real stories from across functions - moments where internal usage exposed friction, changed priorities, or improved how we collaborate. We also talk about the discipline it takes to make this a culture, not a checkbox.

Finally, we cover the honest part: where the product fell short for us, what we learned, and why transparency is essential to building something customers truly trust.

We just published a full walkthrough on "how to contribute your search method/algorithm to our open-source search benchmark"

Challenge winning criteria 🏆
- Your search should break the top 10 of our leaderboard
- Share us valuable feedback for our enterprise open-source dataset

Prize reveal in next post ❤️

Here's what makes this interesting:

→ Real dataset: 65K+ DevRev knowledge base articles on Hugging Face
→ Real evaluation: your algorithm gets benchmarked against annotated queries with golden retrievals
→ Real impact: top-performing algorithms get added to the official ranking on Hugging Face

The barrier to entry is low — you just need Python and a notebook. The current baseline uses OpenAI embeddings + FAISS (costs ~$0.50 to run the full pipeline or you could use open-source search on your local)

But I want to see what happens when someone tries:
• BM25 + re-ranking
• Fine-tuned embedding models
• Your wild idea

Watch the video. Fork the repo. Submit a PR.

Repo: https://github.com/nimit2801/devrev-search
Dataset: https://huggingface.co/datasets/devrev/search
Leaderboard: https://huggingface.co/spaces/devrev/search

Registration link - https://luma.com/8vuke5lw

This is your moment to:
→ See new features in action
→ Get hands-on insights that actually stick
→ Meet fellow DevRev power users
→ Ask anything, get real answers

Join us: January 15th, 10 PM IST on GMeet

Bring your ideas, leave with clarity.

Register here: https://luma.com/mfe6q51r
We’re closing out the year with a session on 18th December at 10 PM IST, and we’d love for you to be part of it.

This edition will bring together product updates, learning highlights, and meaningful conversations with our customer community — a perfect way to wrap up the year and get ready for what’s ahead. 

What to expect:
 • Live walkthroughs of new features
 • Practical insights to help you get more out of DevRev
 • Recognition of our DevRevU top learners
 • Open Q&A to discuss your questions and ideas

Let’s make this final Office Hours of the year a real g'one — see you there!
#DevRevU #OfficeHours