advith chelikani
811 posts

advith chelikani
@advith_c
Co-Founder @ Pylon
San Francisco, CA Katılım Ekim 2023
8 Takip Edilen276 Takipçiler

Tomorrow we'll show you why he's so excited about this.
I'm hosting a webinar with Alex Carleton (Head of CX @braintrust) to show how teams are using Pylon MCP with AI tools to...
→ Investigate tickets
→ Analyze account data
→ Automate support <> engineering workflows
→ and a whole lot more
English

The Pylon MCP x Claude Code combo is so powerful...
@marty_kausas logged into GitHub for the first time in years to set it up.

English

So we filmed a new video to show you.
Watch the full demo here: usepylon.com/videos/pylon-p…
Or in our docs: docs.usepylon.com/pylon-docs/
English

We added SKUs and features like...
- Account Intelligence
- Product Intelligence
- AI anomaly detection
- AI issue suggestions
- AI fields for issues and accounts
- Call recording integrations
- Product ticketing integrations
- Calendar integrations
- Personal email integrations
- AI churn risk tracking
- AI reports
...and way too much more to list out.
English

@braintrust Come see how Alex's team has architected an entire support flow with Pylon data, Pylon's native AI agents, and Claude Code.
Register for a spot:
usepylon.com/events/claude-…
English

@braintrust So I'm really excited to continue our conversation next Thursday and...
You can join us live!
March 19 @ 9:30 AM PT.
English

When we decided to do a webinar about Pylon <> AI tools, I immediately thought of Alex Carleton.
We had talked about how @braintrust uses Claude Code with Pylon MCP, and Alex had this incredible flowchart of how it all works for their team.

English

𝟮/ 𝗔𝗜 𝗳𝗶𝗲𝗹𝗱𝘀 𝗿𝘂𝗻 𝗯𝗲𝗳𝗼𝗿𝗲 𝘁𝗿𝗶𝗴𝗴𝗲𝗿𝘀 𝗳𝗶𝗿𝗲
Previously when a new issue got created, triggers would fire before AI fields had a chance to run. So some triggers (for routing, triage, etc.) wouldn't work as intended because AI conditions weren't correctly set yet.
Now AI fields will run first so triggers have the right context to route, classify, or act on new issues.
English

