Lighthouse will be in maintenance mode tomorrow night at 8pm EST, for about 1h, hopefully less.

This is a bit short notice, but we have to perform some important hardware updates.

As usual, you can contact us at support@lighthouseapp.com if you have any question or concern.

Starting today, if you access a Tender site on mobile, you will get a nice mobile view (at last!). If your site uses custom CSS, you will need to manually activate it: please read the KB article for details.

Let us know how you like it :)

Cheers!

Raygun.io (https://raygun.io/) is an error tracking service that helps you build better software, allowing your team to keep an eye on the health of your applications by notifying you of software bugs in real time. Raygun works with every major web and mobile programming language and platform.

raygun.io

They recently added support for Lighthouse and we wrote a KB article to get you started.

So check them out, and start tracking!

… still gets you better, simpler, customer support!

We decided to change the names of our plans. If you are currently on the following plans, don’t fret! Nothing has changed other than the name. All your existing features are still there. If you were on a legacy plan, nothing changes for you at all.

  • Core => Starter
  • Extra => Standard
  • Ultimo => Pro

Let us know if you have any questions at help@tenderapp.com

We will have a routine maintenance for Lighthouse this Friday 29th at 10pm EST. It should last about 30 mins, hopefully less.

Go enjoy your friday night!

Cheers.

Howdy!

What is this new section that just appeared in the sidebar for KB articles?

Screenshot of the sidebar showing a 'Is this article helpful, thumbs up/down' section

Well, starting today, users can now rate your KB articles! If you are logged in as a regular user, you will see the rating widget, and if you are logged in as staff, you will see the actual rating:

Same section showing the actual rating

Click through and you will be able to see all ratings and comments for the article, as well as the version they are associated with, so that you can keep track of your progress when improving articles:

Or head over to Knowledge Base > Ratings to see all ratings for all articles.

I hope you enjoy the change, and let us know if you have any feedback ;)

Cheers!

Howdy everyone!

Today I would like to highlight two updates we deployed to the Knowledge Base in the past few weeks.

Versioning

KB articles are now versioned. You can see changes between versions, restore versions, and see who made the changes. This should make it safer to update your articles regularly and allow you to recover from mistakes more easily :)

You can see the versions on the KB list:

Showing the number of versions in the KB listing

On the KB page:

Showing the number of versions on the KB page

And look at the history:

Showing the versions history

Export

On the KB admin page, in the left sidebar, there is an option to export your whole KB as an HTML page:

Export your KB

We just improved this feature to add a Table of Contents, and fix all links between the different articles. This means that if you use the same anchor names in different articles, they will now work flawlessly in the exported file. If you moved or renamed articles but still have links to the old address, the export will take care of that as well.

This change will allow you to export your entire KB in one page, and print it as a PDF, and you have a complete manual for your application/service. Some of our customers do just that!

This last part is a bit experimental (the re-linking of everything), so if you experience any issue, just let us know.

Enjoy!

On Monday April 7th, a vulnerability in OpenSSL was disclosed as CVE-2014-0160, also known as Heartbleed. This is a serious vulnerability as OpenSSL is widely used to secure HTTPS traffic, and so it affects a large part off the internet.

All our services have been patched and secured: Tender was never vulnerable but Lighthouse was partially vulnerable through our use of Amazon Elastic Load Balancer. Our load balancer runs on a dedicated instance, which limits the data that could have been exposed. On Tuesday 8th, Amazon issued an update to their services, and we immediately updated our certificates and moved to a new load balancer.

What do I need to do?

If you are a Tender customer: nothing. Tender was never affected.

If you are a Lighthouse customer we recommend:

  • Sign out and back in
  • Change your password
  • Update all your API tokens

No malicious activity has been detected, but given the nature of the bug, and the amount of time it existed, it is better to err on the side of caution.

As usual, if you have any question, comment or concern, feel free to reach out to us at support@lighthouseapp.com or support@tenderapp.com.

Be safe.

Howdy.

Today we are deploying some changes to Companies. Companies are groups of users that have access to each other’s private discussions. This is often used when your product/service is used by multiple people inside a company, and they all need/want to participate in discussions/issues. This is a helpful system, but it was missing one big feature: notifications. So today, we are introducing Notifications for Companies.

So what are the changes:

  • By default, all members of a company will receive notifications about any discussion started (or replied to) by someone else in the company. This will help reduce duplicate reports, and keep everyone in the loop about what’s going on.

  • While “notifications on” will be the default, it can be turned on/off for each company individually. Small companies may want to know about everything, while larger group might just need access. You can change the default on the company page.

  • Each user of a company can set their own preference regarding notifications. This means that if the default for a company is “off”, one particular user may still decide that they want to be notified about everything. On the other hand, if the default is “on”, one or multiple users might not need to be involved all the time and can decide not to receive notifications. We feel that this offers the most flexibility, both for the support site, and for the individual users.

  • Finally, if a user is subscribed to company notifications, they can still unsubscribe from a particular discussion by clicking the “unsubscribe” button or replying #ignore by email.

While notifications are the biggest change, there are also a number of smaller improvements across the board:

  • You can now add/remove a Company as a watcher. When a user who is part of a company creates a discussion or replies to a discussion, the company gets added as a watcher. So if you need to keep the discussion private with only this user, you can simply remove the company and the original user will be the only one with access/notifications.

  • Adding watchers now autocompletes on the “add watcher” widget, as well as on the “new discussion” page, both on the frontend and on the dashboard. And you can add companies directly (or you can add a member of the company, both will work).

    Adding a watcher

  • Users get notified when they are added to a company, and will get links to update their notifications and access all the company discussions. This should make onboarding of new members easier.

  • It is now easier to add an existing user to a company: just go on their profile and select the company in the dropdown.

    Selecting the company

  • You can now see if a user is part of a company in the discussion header: John Doe (Company).

That’s about it. Hope you enjoy the changes! You can find out more about companies in the knowledge base.

Cheers.

Howdy!

While Tender is a great support platform, sometimes all you need is a simple Knowledge Base. So we just deployed an option to do just that. You can find out more in the knowledge base article.

Cheers!

1 2 3 4 5 Next