What would stop you from trying VELA (https://vela.cx/) this month? Be specific about how you handle this today. Also say the maximum you would pay per month in USD (0 if nothing).

Ervin Farrellneutral

The biggest hurdle for us right now is integrating a new tool seamlessly into our existing workflow without a significant upfront time investment. Today, my two support specialists and I manually manage our Discord, shared inbox, Notion docs, and Gmail archives. We spend considerable time training our AI on Notion content and manually tagging past tickets. The idea of an AI agent that can learn from all those sources is intriguing, especially to tackle our repetitive onboarding and billing questions. However, I need to see how it handles the nuances of our specific product and community. If it requires extensive data cleaning or complex setup, that's a barrier. I'd be willing to pay up to $150 per month for a solution that demonstrably reduces our team's manual effort and improves response times.

Simulated interest: 60/100

Nettie Considineneutral

The main thing stopping me from trying VELA this month would be the integration with our existing systems and the training overhead for my team. We've just consolidated our Slack and Telegram queues, so introducing another tool requires careful planning. Today, we manually route recurring questions into a single queue using Intercom for email, which is already a big step. I'd need to see clear evidence of how VELA integrates with Slack and Telegram without disrupting our current flow, and how straightforward the AI training process is before committing. I'm also concerned about the context it passes to my team on escalated issues. I would consider paying up to $200 per month for a solution like this, given its potential to streamline recurring queries.

Simulated interest: 60/100

Agniprava Bhattathirineutral

What would stop me from trying VELA? Honestly, my team's current bandwidth is the biggest concern. We're already swamped with integration questions, and introducing a new tool, even a promising one, requires dedicated setup and training time. My current process involves pulling context from Zendesk, our internal docs, and release notes, which is time-consuming. If VELA could truly automate that initial context gathering and answer repetitive queries efficiently, it would be compelling. However, I need to be sure it integrates seamlessly and doesn't create more work in the initial stages. The biggest hurdle would be the time investment from my team and me to get it fully operational and accurate for our specific fintech API context. I'd be looking for a smooth onboarding process and clear ROI on the time spent. If it proves effective, I might consider paying around $150 per month, primarily for the AI agent capability.

Simulated interest: 60/100

Gloria Kerlukeneutral

VELA sounds promising for handling repeat questions and offloading some work from my team. The main thing stopping me from trying it this month is understanding how it integrates with our existing workflows, especially since we rely on GitHub Discussions and YouTube comments, which aren't explicitly listed as primary channels here. We currently manage these by manually escalating complex issues to our support engineer or updating our knowledge base, which takes considerable time. I'd need to see a clear path for how VELA would augment, not just duplicate, this. I'm willing to pay up to $150 per month for a solution that demonstrably reduces our team's workload and improves response times.

Simulated interest: 60/100

Lennard Delongeneutral

This looks promising, especially the ability to train on various sources like PDFs and past tickets. Currently, we rely heavily on HelpScout for direct tickets and our Slack community, along with onboarding videos, to handle repeat questions. Consolidating this knowledge into an AI agent could certainly help automate our goal of handling 70% of common queries. My main concern would be the integration effort and ensuring the AI agent accurately reflects our nuanced support policies without generating incorrect information. We'd also need to see how it handles escalations to our product and finance teams. The pricing basis isn't immediately clear on the page, so I'd need more details before committing to a specific amount.

Simulated interest: 70/100

Aurelle Nguyenneutral

What would stop me from trying VELA this month? Primarily, the integration with our existing Crisp inbox. Right now, I manage everything there, and while VELA mentions an 'omnichannel inbox,' I need to understand how seamlessly it connects with Crisp. My current process involves triaging tickets in Crisp and then updating a separate spreadsheet with approved answers. If VELA can automate the answer retrieval and ensure it doesn't create a new silo, that would be a huge win. I would be willing to pay around $40 per month, but it would depend entirely on the integration and the efficiency gains.

Simulated interest: 60/100

Mustafa Verbeekneutral

My current priority is handling customer questions myself to gain direct insights, which I document in Notion. Introducing an AI agent right now would require significant setup time to train it on my existing knowledge base and ensure it integrates smoothly with my workflow, which is a considerable overhead for a two-person operation. I'm not sure if the AI would be able to handle the nuances of the specific analytics questions my users have without extensive customisation. Given my focus on bootstrapping and efficiency, I'd need to see clear evidence of time savings and a low setup burden before considering it. If it could truly automate a substantial portion of my support without much effort on my end, I might consider paying up to $40 per month.

Simulated interest: 30/100

Aasa Acharineutral

VELA sounds interesting as it promises to automate responses to repeat questions, which is a significant part of my current workload managing our Telegram and Slack channels. Today, I manually copy resolved questions into a document and then coordinate with tutors for recurring issues, or escalate complex cases to product. My main concern would be the accuracy and tone of the AI; ensuring it provides helpful, empathetic responses without sounding robotic is crucial. Also, the integration with our existing systems and the learning curve for the team would need careful consideration. I'd be willing to pay around $50 per month for this, given that it's a subscription.

Simulated interest: 70/100

Jorge Ceballos Marroquínneutral

The main thing that would stop me from trying VELA this month is the lack of clear pricing information. I need to understand the cost structure before committing any time. Currently, my team spends a significant amount of time manually searching for answers across our Intercom, community forum, and PDF guides. We also have to create and maintain documentation, which is often inconsistent, especially for new features. If VELA could demonstrably reduce this manual search and improve our documentation quality, I would consider it. However, without knowing the price, it's difficult to assess the value. I would be willing to pay up to $150 per month, but only if it significantly streamlines our current workflow and improves team efficiency.

Simulated interest: 60/100

Christopher Gloverneutral

My main concern with trying VELA this month is integrating it seamlessly with my existing workflow. I currently manage our knowledge base in Notion and archive past tickets in documents and spreadsheets. I need to ensure VELA can effectively ingest and utilize that data without creating more manual work. The AI needs to be highly accurate; I'm the final human-in-the-loop and can't afford errors damaging our brand. Pricing isn't clear from this page; I'd need to see a breakdown. I'd pay up to $150 per month for a tool that demonstrably reduces my review time and improves response accuracy without introducing new complexities.

Simulated interest: 70/100