Shantanu Vishwanadha (@thecoderpanda) header
Shantanu Vishwanadha (@thecoderpanda) profile picture

Senior Solutions Engineer @hops_ai & @zencoderai | AI Agents

India
Joined October 2014
Photo by Shantanu Vishwanadha (@thecoderpanda)Photo by Shantanu Vishwanadha (@thecoderpanda)Photo by Shantanu Vishwanadha (@thecoderpanda)Photo by Shantanu Vishwanadha (@thecoderpanda)Photo by Shantanu Vishwanadha (@thecoderpanda)Photo by Shantanu Vishwanadha (@thecoderpanda)Photo by Shantanu Vishwanadha (@thecoderpanda)Photo by Shantanu Vishwanadha (@thecoderpanda)Photo by Shantanu Vishwanadha (@thecoderpanda)Photo by Shantanu Vishwanadha (@thecoderpanda)
Shantanu Vishwanadha retweeted
Judged the internal hackathon at JD College, Nagpur last month. The pitches were good, but the best part was students defending their ideas under tough questions. That is where the real thinking showed.
1
1
32
Feature requests reach support every day and mostly stay in closed tickets. A weekly job that copies each request into a shared table, links the ticket, and groups duplicates gives product something to sort and verify. I'd send that table before any summary deck.
30
Answering one support ticket can mean the helpdesk for history, the CRM for the plan, Slack for the engineering thread, and the docs to check the fix. I'd want an assistant that reads all four from the ticket and shows where each fact came from, so I can check it before replying.
2
1
35
Design feedback often lands as a Slack screenshot with a red circle and "can this be bigger?" A week later it's hard to tell which comments were handled. Pinning the comment on the image itself, with the revised version posted beside it, keeps the request and the change together.
32
Before a customer call I want a one-page brief: open tickets, last call notes, plan, recent usage. An agent can pull that from the CRM and helpdesk, as long as every line shows its source and date, and anything it couldn't find is marked missing instead of guessed.
1
47
Per-seat pricing for AI tools decides who is in the loop. When a team buys seats for a few people, everyone else gets the output secondhand, pasted into Slack. Pricing the AI's work instead of each user (Hops does this) lets the whole team use one agent in the same doc.
28
A decision made in a Slack thread often gets recorded nowhere else. Two weeks later someone asks where it was agreed, and the thread is buried. An agent in that thread could write the decision into the tracker before the conversation ends, with a link back to the messages.
1
31
I'll be in Bangalore from November 23–25! Looking forward to connecting with founders, GTM, RevOps, and community professionals. I'd love to meet new people, exchange ideas, build meaningful connections, and share how Hops can simplify the way teams work. If you're around, let's catch up over coffee!
3
6
186
@boardyai do your magic. connect me with folks around.
29
For one day, count how often you copy text out of a tool, paste it into an AI chat, and paste the answer back somewhere else. Each round trip leaves the sources and the original question behind, so the next person sees only the answer.
23
When an AI draft starts in one person's chat, it reaches the team as an attachment: v2.docx in a DM, while a colleague has already edited v1. The cleanup after that is version reconciliation. Drafting in the shared doc, with the source files linked, skips that step.
1
23
Release notes usually get written by whoever merged last, and support reads them the morning customers start asking. I'd draft them in a doc where engineering, docs and support edit together, and give support one section: what customers will ask about this change.
27
Before rolling out a shared AI workspace, run one test. Ask it about a file only you can open, in a thread others can read, and check who sees the answer. It should stay with you until you choose to share it. Hops (where I work) does this. I'd require it of any tool.
17
When two people bring different numbers to a meeting, they often pulled the same report from separate exports on different days. I'd rather everyone read one shared dashboard built from the source, so the meeting is about the number and not whose spreadsheet is newer.
26
Sales-to-support handoff notes tend to get written from memory at the end of a busy week. If an AI drafts the note from the CRM record, the call notes and the open tickets, with a link on each line, support gets a note they can check line by line.
29
Many support teams have an escalation checklist that mostly lives in someone's head. Write it down once as a method an AI agent can run, and every escalation arrives with the same repro steps, environment, and what was tried. In Hops that's a skill, and you pick who can use it.
23
One support escalation can involve a ticket, a Slack thread, a Jira issue, a Sentry trace, and a doc. Switching tabs costs less than re-explaining the customer's problem each time it changes hands. Keep those pieces in one place and each handoff starts where the last one stopped.
15
Good prompts at work often live in one person's chat history. If a call-prep prompt works, write it down as team instructions: which sources to read, cite the date of each fact, flag conflicts instead of picking one. Then anyone can run it and the reviewer knows what to check.
27
Shantanu Vishwanadha retweeted
Day 2 of #WebSummit2026 canceled because of Storm Charles, so 70k tech people got an impromptu rain day in Lisbon. Spent the morning in a hotel lobby planning dinner for our group across different hotels, all inside Hops. Thread pulled everyone’s locations into a shared map, set up a ranked-choice voting table, and tallied the picks in under 15 minutes. Real collaborative AI is built for messy group workflows like this. @hops_ai @WebSummit
1
1
247
A DevRel use for a shared AI workspace: have it read the week's GitHub issues and community threads, then list the questions the docs don't answer, each linked to its thread. The docs team edits that list in the same place and can open any original thread.
24