Coda vs. OpenText Hightail

My organization considers Coda for a variety of business and organizational projects. Using Coda, my organization keeps a lot of data and different types of data in one place. The user interface of Coda is very fluid and easy to use. My organization has benefitted from using the efficient and effective operational functionality of Coda.

Incentivized

Hightail is my go-to source when I need to send large files that would never fit as regular attachments. That being said, sometimes there are files that would perfectly fit as attachments but I want the security that Hightail provides when sending sensitive or private material. It's very comforting knowing that the content I'm sending is only being received and viewed by the intended parties. It's also comforting for my clients when it's THEIR content that I'm sending for review.

Incentivized

• Flexibility. It's easy to get started on a small scale, but add more complex organization strategies as needed.
• Integrations. It's simple to ingest data from sources like Zapier for time-saving automations.
• Useful components. View table data across different formats like cards or custom detail views.

Incentivized

• Management of content, communication, spaces, and projects in general.
• Control of processes, tasks and activities between the different members of teams.
• Collaborative work through different media and channels.

Incentivized

• It takes getting used to in terms of how the formulas per column is implemented, in contrast to how we build tables in Excel. For organization/team purchase, it would be worth considering having a training for the core team of users. Right now, we do a lot of self-learning.
• Inability to email charts or image without these objects being hosted on a third party. The community has been great in providing workarounds but it would be much more convenient to be able to have such ability natively.
• APAC Support. I'm based in Malaysia, due to timezone differences, even with a livechat implemented, the support for each step and conversation takes up to 24 hours per response. Having some hours covered in our timezone would greatly improve customer support experience.

Incentivized

• Some of our recipients are not very tech-savvy and can get confused with how to download a file. There is some room for improvement by making it clearer where the user should click to download the file.

Incentivized

Coda is definitely something that has been proven to drive positive impact in our organization. We have many divisions that can benefit from this that we have yet to explore. It would definitely be worth renewing.

Incentivized

Coda can seem either really useful or really useless. The extremes of both ends is driven by what our own understanding of what we want to implement. If we lack this understanding, it will be easy to misunderstand Coda's usability especially in the wrong context.

Incentivized

So far in the past year, we haven't had situations that Coda has gone down for us which is great.

Incentivized

We haven't done any integrations - the initial part of our experience we found that for docs with complex formulas, the page tends to load slowly but in recent months, Coda has improved and optimized the loading times in general and we generally don't find any problems in terms of speed anymore.

Incentivized

Mainly due to timezone differences. I think Coda's support in general is well implemented and executed. They know their stuff and are helpful. But since I'm not in the same timezone, solution rates are slower for me, and that's not something I prefer. I work in customer service, too, and more often than not, time is important. Shortening the solution time would be a much greater experience.

Incentivized

I'm relatively inexperienced but this experience is meaningful. It would have been nice to have some guidance from Coda so that we understood more on Coda's purpose and potential.

Incentivized

While all of the products listed have great features and platforms, there was always one thing missing from them that I would need to get from another application. Coda was the first one we used that really combined some of the best parts of those products and allowed us to use it in one place. I also appreciate the flexibility of creating your own framework and workflow, unlike in other tools where you have to follow how they capture data and organize projects.

Incentivized

Honestly, once we started using Google Drive more efficiently and saw what improvements OpenText Hightail had made, it was hard to choose. But now that we more consistently use Google Drive, I use it probably 75% more than I use OpenText Hightail for the same tasks. I'm not sure how much longer I'll be a customer at OpenText but it's great to have both options.

Incentivized

I think scalability is definitely good here since it's based on number of doc makers. Implementation into each dept becomes simpler. That being said, due to the nature of our work, we find it easier that we have a "super user" and then a team of other doc makers. This would make the doc creation and management more efficient.

Incentivized

• Increased insight for all stakeholders involved--both in terms of overview and details
• Better grip on issues and escalations--reduced friction, confusion, and higher clarity on status, next actions, and ownership.
• Reduced time required by those who need to maintain all information. Record (a detail) once and use multiple times.

Incentivized

• Hightail simply saves time. We no longer struggle with trying to meet the requirements of OutLook. When we have a file that is too large to send via OutLook we just "hightail it".

Incentivized