<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:dc="http://purl.org/dc/elements/1.1/" version="2.0"><channel><description>Here lies the blog of ENTP, a web application development company based in Portland, OR.</description><title>The ENTP Blog</title><generator>Tumblr (3.0; @entpblog)</generator><link>https://blog.entp.com/</link><item><title>Say what?</title><description>&lt;p&gt;Howdy,&lt;/p&gt;

&lt;p&gt;Echoes have long provided a way for support staff to provide answers faster. Unfortunately, it was not always easy to use with a large number of echoes. So today, I&amp;rsquo;m happy to announce that we redesigned the Echo box to be much faster and more usable:&lt;/p&gt;

&lt;p&gt;&lt;img src="http://entp-blog-images.s3.amazonaws.com/2015-03-04-echoes.gif" alt="New echo box uses autocomplete"/&gt;&lt;/p&gt;

&lt;p&gt;The Echo box now uses a single autocomplete field. So you can press &lt;code&gt;CTRL+e&lt;/code&gt; or &lt;code&gt;Command+e&lt;/code&gt;, type a few letters, select your Echo, and continue typing your reply. And because Echoes now insert at the cursor, you can easily use multiple echoes in one reply.&lt;/p&gt;

&lt;p&gt;This opens the door to using Echoes for everything from standard replies, to signatures. Add a short code to the title, &lt;code&gt;#sj&lt;/code&gt; for &lt;code&gt;signature julien&lt;/code&gt; for example, and you&amp;rsquo;ll be on your way in not time!&lt;/p&gt;

&lt;p&gt;I hope this small improvement will make every day a little smoother&amp;hellip;&lt;/p&gt;

&lt;p&gt;Cheers!&lt;/p&gt;</description><link>https://blog.entp.com/post/112695641427</link><guid>https://blog.entp.com/post/112695641427</guid><pubDate>Wed, 04 Mar 2015 06:46:10 -0800</pubDate><category>tender</category><dc:creator>asciithoughts</dc:creator></item><item><title>Slack integration</title><description>&lt;p&gt;Hi all,&lt;/p&gt;

&lt;p&gt;We know Slack is awesome. We love it and use it every day. Until now, there was not an easy way to integrate Slack with Tender. But rejoice! You can now receive all your Tender notifications in the channel of your choice :)&lt;/p&gt;

&lt;p&gt;You can find more info on the KB: &lt;a href="http://help.tenderapp.com/kb/third-party-integrations/how-do-i-integrate-my-tender-with-slack" target="_blank"&gt;http://help.tenderapp.com/kb/third-party-integrations/how-do-i-integrate-my-tender-with-slack&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;Enjoy!&lt;/p&gt;</description><link>https://blog.entp.com/post/108663737862</link><guid>https://blog.entp.com/post/108663737862</guid><pubDate>Tue, 20 Jan 2015 11:39:12 -0800</pubDate><category>tender</category><dc:creator>asciithoughts</dc:creator></item><item><title>Service interruption: DDOS</title><description>&lt;p&gt;Hi all,&lt;/p&gt;

&lt;p&gt;This evening we experienced a large DDOS on Tender which brought the site down for most customers. We worked with our hosting provider to mitigate the attack and the traffic is now under control. Most sites should be back online, and we&amp;rsquo;ll give ongoing updates as the situation evolves.&lt;/p&gt;

&lt;p&gt;If you have any question, or if you are still experiencing issues, you can reach us at &lt;a href="http://help.tenderapp.com" target="_blank"&gt;http://help.tenderapp.com&lt;/a&gt;, &lt;a href="mailto:support@tenderapp.com" target="_blank"&gt;support@tenderapp.com&lt;/a&gt; and &lt;a href="https://twitter.com/tenderapp" target="_blank"&gt;@tenderapp&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;Cheers.&lt;/p&gt;</description><link>https://blog.entp.com/post/105320257182</link><guid>https://blog.entp.com/post/105320257182</guid><pubDate>Mon, 15 Dec 2014 19:01:00 -0800</pubDate><category>tender</category><dc:creator>asciithoughts</dc:creator></item><item><title>Maintenance Thursday 25th at 8pm EST</title><description>&lt;p&gt;Lighthouse will be in maintenance mode tomorrow night at 8pm EST, for about 1h, hopefully less.&lt;/p&gt;

&lt;p&gt;This is a bit short notice, but we have to perform some important hardware updates.&lt;/p&gt;

&lt;p&gt;As usual, you can contact us at support@lighthouseapp.com if you have any question or concern.&lt;/p&gt;</description><link>https://blog.entp.com/post/98331380672</link><guid>https://blog.entp.com/post/98331380672</guid><pubDate>Wed, 24 Sep 2014 13:40:19 -0700</pubDate><category>Lighthouse</category><dc:creator>asciithoughts</dc:creator></item><item><title>Tender is mobile friendly!</title><description>&lt;p&gt;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 &lt;a href="https://help.tenderapp.com/kb/customization/mobile" target="_blank"&gt;the KB article&lt;/a&gt; for details.&lt;/p&gt;

&lt;p&gt;Let us know how you like it :)&lt;/p&gt;

&lt;p&gt;Cheers!&lt;/p&gt;</description><link>https://blog.entp.com/post/98140883622</link><guid>https://blog.entp.com/post/98140883622</guid><pubDate>Mon, 22 Sep 2014 05:42:31 -0700</pubDate><category>tender</category><dc:creator>asciithoughts</dc:creator></item><item><title>Lighthouse integrates with Raygun.io!</title><description>&lt;p&gt;Raygun.io (&lt;a href="https://raygun.io/" target="_blank"&gt;https://raygun.io/&lt;/a&gt;) 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.&lt;/p&gt;

&lt;p&gt;&lt;img src="http://entp-blog-images.s3.amazonaws.com/kbs/kb-raygun.png" alt="raygun.io"/&gt;&lt;/p&gt;

&lt;p&gt;They recently added support for Lighthouse and we wrote a &lt;a href="http://help.lighthouseapp.com/kb/integrations/raygunio" target="_blank"&gt;KB article&lt;/a&gt; to get you started.&lt;/p&gt;

&lt;p&gt;So check them out, and start tracking!&lt;/p&gt;</description><link>https://blog.entp.com/post/98139550447</link><guid>https://blog.entp.com/post/98139550447</guid><pubDate>Mon, 22 Sep 2014 05:09:00 -0700</pubDate><category>Lighthouse</category><dc:creator>asciithoughts</dc:creator></item><item><title>A plan by any other name ...</title><description>&lt;p&gt;&amp;hellip; still gets you better, simpler, customer support!&lt;/p&gt;

&lt;p&gt;We decided to change the names of our plans. If you are currently on the following plans, don&amp;rsquo;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.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Core =&amp;gt; Starter&lt;/li&gt;
&lt;li&gt;Extra =&amp;gt; Standard&lt;/li&gt;
&lt;li&gt;Ultimo =&amp;gt; Pro&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Let us know if you have any questions at &lt;a href="mailto:help@tenderapp.com" target="_blank"&gt;help@tenderapp.com&lt;/a&gt;&lt;/p&gt;</description><link>https://blog.entp.com/post/97900172242</link><guid>https://blog.entp.com/post/97900172242</guid><pubDate>Fri, 19 Sep 2014 10:50:48 -0700</pubDate><category>tender</category><dc:creator>asciithoughts</dc:creator></item><item><title>Maintenance Friday 29th at 10pm EST</title><description>&lt;p&gt;We will have a routine maintenance for Lighthouse this Friday 29th at 10pm EST. It should last about 30 mins, hopefully less.&lt;/p&gt;

&lt;p&gt;Go enjoy your friday night!&lt;/p&gt;

&lt;p&gt;Cheers.&lt;/p&gt;</description><link>https://blog.entp.com/post/96004644977</link><guid>https://blog.entp.com/post/96004644977</guid><pubDate>Thu, 28 Aug 2014 08:26:22 -0700</pubDate><category>Lighthouse</category><dc:creator>asciithoughts</dc:creator></item><item><title>KB Ratings</title><description>&lt;p&gt;Howdy!&lt;/p&gt;

&lt;p&gt;What is this new section that just appeared in the sidebar for KB articles?&lt;/p&gt;

&lt;p&gt;&lt;img src="http://entp-blog-images.s3.amazonaws.com/2014-08-06-kb-ratings-1.png" alt="Screenshot of the sidebar showing a 'Is this article helpful, thumbs up/down' section"/&gt;&lt;/p&gt;

&lt;p&gt;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:&lt;/p&gt;

&lt;p&gt;&lt;img src="http://entp-blog-images.s3.amazonaws.com/2014-08-06-kb-ratings-2.png" alt="Same section showing the actual rating"/&gt;&lt;/p&gt;

&lt;p&gt;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:&lt;/p&gt;

&lt;p&gt;&lt;img src="http://entp-blog-images.s3.amazonaws.com/2014-08-06-kb-ratings-3.png" alt=""/&gt;&lt;/p&gt;

&lt;p&gt;Or head over to &lt;strong&gt;Knowledge Base &amp;gt; Ratings&lt;/strong&gt; to see all ratings for all articles.&lt;/p&gt;

&lt;p&gt;I hope you enjoy the change, and let us know if you have any feedback ;)&lt;/p&gt;

&lt;p&gt;Cheers!&lt;/p&gt;</description><link>https://blog.entp.com/post/93985558512</link><guid>https://blog.entp.com/post/93985558512</guid><pubDate>Wed, 06 Aug 2014 10:51:57 -0700</pubDate><category>tender</category><dc:creator>asciithoughts</dc:creator></item><item><title>Knowledge Base updates</title><description>&lt;p&gt;Howdy everyone!&lt;/p&gt;

&lt;p&gt;Today I would like to highlight two updates we deployed to the Knowledge Base in the past few weeks.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Versioning&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;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 :)&lt;/p&gt;

&lt;p&gt;You can see the versions on the KB list:&lt;/p&gt;

&lt;p&gt;&lt;img alt="Showing the number of versions in the KB listing" src="http://entp-blog-images.s3.amazonaws.com/kbs/2014-07-16-kb-1.png"/&gt;&lt;/p&gt;

&lt;p&gt;On the KB page:&lt;/p&gt;

&lt;p&gt;&lt;img alt="Showing the number of versions on the KB page" src="http://entp-blog-images.s3.amazonaws.com/kbs/2014-07-16-kb-2.png"/&gt;&lt;/p&gt;

&lt;p&gt;And look at the history:&lt;/p&gt;

&lt;p&gt;&lt;img alt="Showing the versions history" src="http://entp-blog-images.s3.amazonaws.com/kbs/2014-07-16-kb-3.png"/&gt;&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Export&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;On the KB admin page, in the left sidebar, there is an option to export your whole KB as an HTML page:&lt;/p&gt;

&lt;p&gt;&lt;img alt="Export your KB" src="http://entp-blog-images.s3.amazonaws.com/kbs/2014-07-16-kb-4.png"/&gt;&lt;/p&gt;

&lt;p&gt;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.&lt;/p&gt;

&lt;p&gt;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!&lt;/p&gt;

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

&lt;p&gt;Enjoy!&lt;/p&gt;</description><link>https://blog.entp.com/post/91953858152</link><guid>https://blog.entp.com/post/91953858152</guid><pubDate>Wed, 16 Jul 2014 08:20:24 -0700</pubDate><category>tender</category><dc:creator>asciithoughts</dc:creator></item><item><title>Security update: Heartbleed</title><description>&lt;p&gt;On Monday April 7th, a vulnerability in OpenSSL was disclosed as &lt;a href="https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2014-0160" target="_blank"&gt;CVE-2014-0160&lt;/a&gt;, also known as &lt;a href="http://heartbleed.com/" target="_blank"&gt;Heartbleed&lt;/a&gt;. This is a serious vulnerability as OpenSSL is widely used to secure HTTPS traffic, and so it affects a large part off the internet.&lt;/p&gt;

&lt;p&gt;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 &lt;a href="http://aws.amazon.com/security/security-bulletins/aws-services-updated-to-address-openssl-vulnerability/" target="_blank"&gt;an update&lt;/a&gt; to their services, and we immediately updated our certificates and moved to a new load balancer.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;What do I need to do?&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;If you are a Tender customer: nothing. Tender was never affected.&lt;/p&gt;

&lt;p&gt;If you are a Lighthouse customer we recommend:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Sign out and back in&lt;/li&gt;
&lt;li&gt;Change your password&lt;/li&gt;
&lt;li&gt;Update all your API tokens&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;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.&lt;/p&gt;

&lt;p&gt;As usual, if you have any question, comment or concern, feel free to reach out to us at &lt;a href="mailto:support@lighthouseapp.com" target="_blank"&gt;support@lighthouseapp.com&lt;/a&gt; or &lt;a href="mailto:support@tenderapp.com" target="_blank"&gt;support@tenderapp.com&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;Be safe.&lt;/p&gt;</description><link>https://blog.entp.com/post/82213145681</link><guid>https://blog.entp.com/post/82213145681</guid><pubDate>Wed, 09 Apr 2014 11:57:01 -0700</pubDate><category>Lighthouse</category><dc:creator>asciithoughts</dc:creator></item><item><title>Companies</title><description>&lt;p&gt;Howdy.&lt;/p&gt;

&lt;p&gt;Today we are deploying some changes to Companies. Companies are groups of users that have access to each other&amp;rsquo;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.&lt;/p&gt;

&lt;p&gt;So what are the changes:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;By default, all members of a company will receive notifications about any discussion started (or replied to) by someone else in the company&lt;/strong&gt;. This will help reduce duplicate reports, and keep everyone in the loop about what&amp;rsquo;s going on.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;While &amp;ldquo;notifications on&amp;rdquo; will be the default, it can be turned on/off for each company individually&lt;/strong&gt;. Small companies may want to know about everything, while larger group might just need access. &lt;a href="https://help.tenderapp.com/kb/companies/what-are-companies#notifications" target="_blank"&gt;You can change the default on the company page&lt;/a&gt;.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;a href="https://help.tenderapp.com/kb/companies/what-are-companies#notifications" target="_blank"&gt;Each user of a company can set their own preference regarding notifications&lt;/a&gt;. This means that if the default for a company is &amp;ldquo;off&amp;rdquo;, one particular user may still decide that they want to be notified about everything. On the other hand, if the default is &amp;ldquo;on&amp;rdquo;, 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.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Finally, if a user is subscribed to company notifications, they can still unsubscribe from a particular discussion by clicking the &amp;ldquo;unsubscribe&amp;rdquo; button or replying &lt;code&gt;#ignore&lt;/code&gt; by email.&lt;/p&gt;&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;While notifications are the biggest change, there are also a number of smaller improvements across the board:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;&lt;p&gt;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.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Adding watchers now autocompletes on the &amp;ldquo;add watcher&amp;rdquo; widget, as well as on the &amp;ldquo;new discussion&amp;rdquo; 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).&lt;/p&gt;

&lt;p&gt;&lt;img style="width:30%" src="http://entp-blog-images.s3.amazonaws.com/kbs/kb-companies-5.gif" alt="Adding a watcher"/&gt;&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;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.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;It is now easier to add an existing user to a company: just go on their profile and select the company in the dropdown.&lt;/p&gt;

&lt;p&gt;&lt;img style="width:50%" src="http://entp-blog-images.s3.amazonaws.com/kbs/kb-company-invite-1.png" alt="Selecting the company"/&gt;&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;You can now see if a user is part of a company in the discussion header: &lt;strong&gt;John Doe (Company)&lt;/strong&gt;.&lt;/p&gt;&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;That&amp;rsquo;s about it. Hope you enjoy the changes! You can find out more about companies in the &lt;a href="https://help.tenderapp.com/kb/companies" target="_blank"&gt;knowledge base&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;Cheers.&lt;/p&gt;</description><link>https://blog.entp.com/post/80795385292</link><guid>https://blog.entp.com/post/80795385292</guid><pubDate>Wed, 26 Mar 2014 11:26:20 -0700</pubDate><category>tender</category><dc:creator>asciithoughts</dc:creator></item><item><title>Knowledge Base Only</title><description>&lt;p&gt;Howdy!&lt;/p&gt;

&lt;p&gt;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 &lt;a href="https://help.tenderapp.com/kb/setup-installation/using-tender-as-a-knowledge-base" target="_blank"&gt;knowledge base article&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;Cheers!&lt;/p&gt;</description><link>https://blog.entp.com/post/80096577228</link><guid>https://blog.entp.com/post/80096577228</guid><pubDate>Wed, 19 Mar 2014 13:56:10 -0700</pubDate><category>tender</category><dc:creator>asciithoughts</dc:creator></item><item><title>Spam improvements</title><description>&lt;p&gt;Howdy,&lt;/p&gt;

&lt;p&gt;Today we deployed a number of improvements to our spam engine. As a result you should see a big decrease of false positives (real discussion incorrectly marked as spam). It is possible that you will also notice a slight increase of false negatives (real spam, not caught). As you continue marking those as spam the situation should rapidly improve.&lt;/p&gt;

&lt;p&gt;We also added a new option: you can now ignore spam checking for a particular category. This is useful when you receive emails from an automated source (form, etc), which contains a lot of (sometimes malformed) HTML which may trigger some of our spam rules.&lt;/p&gt;

&lt;p&gt;You will find this setting when editing a category:&lt;/p&gt;

&lt;p&gt;&lt;img src="http://entp-blog-images.s3.amazonaws.com/2014-02-24-spam.png" alt="Don't check for spam"/&gt;&lt;/p&gt;

&lt;p&gt;As usual, if you have problems with spam on your site, please contact us. This includes:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Emptying a very large spam folder&lt;/li&gt;
&lt;li&gt;Too many false positives&lt;/li&gt;
&lt;li&gt;Too many false negatives&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Thanks!&lt;/p&gt;</description><link>https://blog.entp.com/post/77742970737</link><guid>https://blog.entp.com/post/77742970737</guid><pubDate>Mon, 24 Feb 2014 14:56:03 -0800</pubDate><category>tender</category><dc:creator>asciithoughts</dc:creator></item><item><title>Site offline for maintenance</title><description>&lt;p&gt;Hi all,&lt;/p&gt;

&lt;p&gt;Tender will be offline for 5-10 minutes tonight, Thursday 1/9 at 9pm PST, while we perform a maintenance operation on one of our database servers. Emails coming in during this period will be slightly delayed.&lt;/p&gt;

&lt;p&gt;We apologize for the inconvenience.&lt;/p&gt;

&lt;p&gt;If you have any question or concern, drop us a line at support@tenderapp.com.&lt;/p&gt;

&lt;p&gt;Thanks!&lt;/p&gt;</description><link>https://blog.entp.com/post/72790864025</link><guid>https://blog.entp.com/post/72790864025</guid><pubDate>Thu, 09 Jan 2014 12:11:30 -0800</pubDate><category>tender</category><dc:creator>asciithoughts</dc:creator></item><item><title>Changelog 12/9 - 12/20</title><description>&lt;p&gt;Happy Friday,&lt;/p&gt;

&lt;p&gt;We have been a little quiet lately, mostly because we have been busy. We are in the process of upgrading a lot of our infrastructure: we bought shiny new servers, with lots of RAM, SSDs and myriad of other goodies, and we are installing them in our datacenter, configuring them, and slowly moving our different services to them. All of this takes time, as we are also upgrading our deployment process (we’re moving to Docker, for those interested). So there are a lot of balls in the air and this work will continue way into January. This slows down the development of new features and bug fixes, but it’s all for the best, I promise!&lt;/p&gt;

&lt;p&gt;With that being said, we haven’t been idle on Tender proper either.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Elastic Search&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;We recently spent a few days optimizing our search cluster. There were a couple of low hanging fruits and we got a 100% improvement: not too shabby!&lt;/p&gt;

&lt;p&gt;&lt;img src="http://entp-blog-images.s3.amazonaws.com/2013-12-13-search.png" alt="Graph of the performance improvement"/&gt;&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Assignments&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;Some teams are really busy, with dozens of agents buzzing and humming at any time. If that’s your case, distributing workload can be challenging. So today, we are introducing a small change that should bring happiness and joy to those hard workers: in the assignment dropdown, next to the name, you will now see the number of discussions open assigned to this supporter. This way, if Tom is under water, but Marry ahead of schedule, you know who to give the next one too. It is a small improvement, but it should definitely help.&lt;/p&gt;

&lt;p&gt;&lt;img src="http://entp-blog-images.s3.amazonaws.com/2013-12-20-assign.png" alt="Screenshot of the new dropdown"/&gt;&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Spam&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;We also deployed a couple of improvements to our spam engine that should reduce false positives.&lt;/p&gt;

&lt;p&gt;While we are on the subject of spam, I have a couple of public announcements:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;&lt;p&gt;If you have issues with spam or false positives on your site, please let us know. We have full control over our spam engine and we can usually improve things for you. Sometimes it’s just bad configuration, but sometimes a rule needs to be tweaked, and we can do that too. Many people contact us after months of suffering, when we could have fixed their problem the day it happened.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;If your spam folder has grown to unspeakable proportions, we can empty it for you. The best way to keep spam in check and customer happy is an empty spam folder. We recommend that you go through it regularly (every day if you can), restoring false positives and deleting the rest. By keeping it empty, you can make sure you never miss anything. You can also get a better idea as to whether the spam engine is doing its job correctly or not, which leads back to point 1. So if your spam folder is not empty, contact us: we’ll empty it for you and you can start fresh and renewed. You know 2014 is coming: let this be your new year resolution! (Well, one resolution at least. Enjoying life a little more should be on top of your list).&lt;/p&gt;&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Happy Holidays.&lt;/p&gt;

&lt;p&gt;Ho Ho Ho&lt;/p&gt;</description><link>https://blog.entp.com/post/70632896727</link><guid>https://blog.entp.com/post/70632896727</guid><pubDate>Fri, 20 Dec 2013 16:22:12 -0800</pubDate><category>tender</category><dc:creator>asciithoughts</dc:creator></item><item><title>How to Use Notification for Best Results</title><description>&lt;div class="post_title"&gt;When creating a new profile in Tender, the email preferences default to notifying the user of changes in the issues/discussions they have participated in (either by creating or commenting on), but you can curate your notifications for any given category or (if support staff) queue that you&amp;rsquo;d like.

&lt;p&gt;&lt;/p&gt;
&lt;p&gt;Just go to &lt;strong&gt;Edit Your Profile&lt;/strong&gt; and scroll mid-page where you&amp;rsquo;ll find &lt;strong&gt;Email Preferences. &lt;/strong&gt;Select as you see fit and &lt;strong&gt;Update Permissions&lt;/strong&gt;.&lt;/p&gt;

&lt;p&gt;&lt;figure class="tmblr-full" data-orig-height="344" data-orig-width="500"&gt;&lt;img alt="image" src="https://64.media.tumblr.com/4dc1dba0aba3ee4efc1a5189aa38b072/4343ddf0966fe8a1-0e/s540x810/832587277ca5e0008bd74712ed3dc755198aaa7c.png" data-orig-height="344" data-orig-width="500"/&gt;&lt;/figure&gt;&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;*Tender Tip:&lt;/strong&gt; Choose your notifications wisely, young Jedi. If you get click happy, you may find your inbox quickly becomes inundated with things you don’t really want to know about.&lt;/p&gt;
&lt;p&gt;Here&amp;rsquo;s more on &lt;strong&gt;Notifications&lt;/strong&gt; in our &lt;a href="https://help.tenderapp.com/kb/general-use/managing-notifications" target="_blank"&gt;Knowledge Base article&lt;/a&gt;.&lt;/p&gt;
&lt;/div&gt;</description><link>https://blog.entp.com/post/69622803819</link><guid>https://blog.entp.com/post/69622803819</guid><pubDate>Tue, 10 Dec 2013 13:41:00 -0800</pubDate><category>tender</category><dc:creator>bemmabobemma-blog</dc:creator></item><item><title>This week's changelog</title><description>&lt;p&gt;Hi everyone,&lt;/p&gt;

&lt;p&gt;Time flies it seems, and while our little hands are never idle, we don&amp;rsquo;t always share what we are working on. This is unfortunate as many bugfixes and features, big and small, go into production every day. So let&amp;rsquo;s mix things up a bit and showcase this week&amp;rsquo;s changelog.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Bugfixes&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;&lt;p&gt;When posting a comment to a discussion that had changed category since the page was opened, the comment would seemingly disappear (it still existed, but not at the right place). This is now fixed.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Tender always had a &amp;ldquo;duplicate&amp;rdquo; detection mechanism that trashes multiple copies of the same message (people hitting the form a little too much, or sending the same email multiple times). The detection was a little too eager and would look for messages in a large timeframe. We reduced this timeframe to 2h which is what feels reasonable to catch those accidentals duplicates, while still allowing some customers to keep you on your toes.&lt;/p&gt;&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;strong&gt;Visible Features&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;&lt;p&gt;The sticky queue now provides pagination:&lt;/p&gt;

&lt;p&gt;&lt;img src="http://entp-blog-images.s3.amazonaws.com/2013-11-22-pinned-pagination.png" alt=""/&gt;&lt;/p&gt;

&lt;p&gt;You can choose which queue you want to always have around in the dashboard:&lt;/p&gt;

&lt;p&gt;&lt;img src="http://entp-blog-images.s3.amazonaws.com/2013-11-22-pinned-choosing.png" alt=""/&gt;&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;The miniprofile now shows the number of replies:&lt;/p&gt;

&lt;p&gt;&lt;img src="http://entp-blog-images.s3.amazonaws.com/2013-11-22-number-of-replies.png" alt=""/&gt;&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;The &amp;ldquo;attached files&amp;rdquo; section doesn&amp;rsquo;t show the &lt;code&gt;C:\fakepath\&lt;/code&gt; anymore:&lt;/p&gt;

&lt;p&gt;&lt;img src="http://entp-blog-images.s3.amazonaws.com/2013-11-22-filenames.png" alt=""/&gt;&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;You can now press &lt;code&gt;?&lt;/code&gt; on a discussion page to get a list of available shortcuts on that page.&lt;/p&gt;

&lt;p&gt;&lt;img src="http://entp-blog-images.s3.amazonaws.com/2013-11-22-help.png" alt=""/&gt;&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;We added some basic validation of all fields when creating a discussion or posting a comment. When you click the submit button, fields are checked and focus will be put back on incorrect values. Fields will turn a light green or red to indicate where the error is:&lt;/p&gt;

&lt;p&gt;&lt;img src="http://entp-blog-images.s3.amazonaws.com/2013-11-22-validation.png" alt=""/&gt;&lt;/p&gt;&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;strong&gt;Invisible Features&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;&lt;p&gt;Improved spam detection for certain types of evil emails.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Improved failover mechanism for some of our servers. We had a few minutes of disturbance last week because of a connectivity issue in one datacenter. If this happens again we should now automatically switch to a different server in a different datacenter.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Ongoing sysadmin work to improve our infrastructure.&lt;/p&gt;&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;strong&gt;Mobile&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;The &lt;a href="https://help.tenderapp.com/kb/customization/making-tender-mobile-friendly" target="_blank"&gt;move to mobile&lt;/a&gt; is still ongoing.&lt;/p&gt;

&lt;p&gt;You can now create new discussions and browse forums:&lt;/p&gt;

&lt;p&gt;&lt;img src="http://entp-blog-images.s3.amazonaws.com/2013-11-22-mobile-create-discussion.png" alt=""/&gt;
&lt;img src="http://entp-blog-images.s3.amazonaws.com/2013-11-22-mobile-categories.png" alt=""/&gt;
&lt;img src="http://entp-blog-images.s3.amazonaws.com/2013-11-22-mobile-browse.png" alt=""/&gt;&lt;/p&gt;

&lt;p&gt;Only the discussion page is left, but it&amp;rsquo;s a big chunk. We want to provide all or most of the current functionality to supporters. This will give you more time to adjust the CSS of your site :)&lt;/p&gt;

&lt;p&gt;As we make progress on mobile, we are rewriting a lot of the frontend code from Prototype JS (I know&amp;hellip;) to Knockout. This is overall a good thing as it will make a lot of things faster and allows us to iterate more quickly in the future. But if you use custom JS, this may break things. So please be on the lookout for errors in your JavaScript console. If we removed code you were using, we will provide you with an alternative.&lt;/p&gt;

&lt;p&gt;Finally, still as part of the move to Knockout, we introduced jQuery in mode no conflict to the front part of the site. So &lt;code&gt;$&lt;/code&gt; and &lt;code&gt;$$&lt;/code&gt; still refer to Prototype, but you can now use &lt;code&gt;jQuery&lt;/code&gt;. Once the rewrite is complete, we will remove Prototype entirely.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Conclusion&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;I hope this changelog is helpful and provides a better insight into what keeps us busy. As usual, if you have comments, ideas, hit us up at &lt;a href="mailto:support@tenderapp.com" target="_blank"&gt;support@tenderapp.com&lt;/a&gt; or &lt;a href="http://help.tenderapp.com/discussions/announcements/2" target="_blank"&gt;post a comment on the discussion&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;Cheers!&lt;/p&gt;</description><link>https://blog.entp.com/post/67790771090</link><guid>https://blog.entp.com/post/67790771090</guid><pubDate>Fri, 22 Nov 2013 15:06:00 -0800</pubDate><category>tender</category><dc:creator>asciithoughts</dc:creator></item><item><title>Should there be only One? Merging User Profiles and Discussions</title><description>&lt;p&gt;Tender has an awesome feature which allows you to merge users and discussions. We are often asked why this feature is not always available, so here’s the breakdown:&lt;/p&gt;
&lt;p&gt;Merging will become available to you when someone replies by email to a discussion they do not have access to. This typically happens when someone uses two email addresses; they start a private conversation with one, but then reply from the other one (like work and home).&lt;/p&gt;
&lt;p&gt;&lt;figure class="tmblr-full" data-orig-height="263" data-orig-width="500" data-orig-src="https://64.media.tumblr.com/3d4955270c875c72446070c2d6617afa/tumblr_inline_n3bgrgHXgb1r2rd10.jpg"&gt;&lt;img alt="image" src="https://64.media.tumblr.com/e79abcdf27f391e1093d8ebf5078b0ca/tumblr_inline_pk2c1aDWlo1r2rd10_540.jpg" data-orig-height="263" data-orig-width="500" data-orig-src="https://64.media.tumblr.com/3d4955270c875c72446070c2d6617afa/tumblr_inline_n3bgrgHXgb1r2rd10.jpg"/&gt;&lt;/figure&gt;&lt;/p&gt;
&lt;p&gt;Since the conversation is private, and the new email address has not been authorized on that discussion, we can’t add it to the discussion, so we split that comment into a new discussion. We do recognize that it was a reply to the original discussion though, and that’s when we offer you the chance to merge it. This allows you to validate that the comment is legitimate before granting access to the private discussion.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;&lt;figure class="tmblr-full" data-orig-height="373" data-orig-width="500" data-orig-src="https://64.media.tumblr.com/12f8f7434542b6247d819f2428548ae2/tumblr_inline_n3bgshXYV61r2rd10.jpg"&gt;&lt;img alt="image" src="https://64.media.tumblr.com/47453a2e8c2ceb571cab13f00c914c46/tumblr_inline_pk2c1aqTDc1r2rd10_540.jpg" data-orig-height="373" data-orig-width="500" data-orig-src="https://64.media.tumblr.com/12f8f7434542b6247d819f2428548ae2/tumblr_inline_n3bgshXYV61r2rd10.jpg"/&gt;&lt;/figure&gt;&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;Voila! The two discussions have now been merged.&lt;/p&gt;
&lt;p&gt;&lt;figure class="tmblr-full" data-orig-height="372" data-orig-width="500" data-orig-src="https://64.media.tumblr.com/e01e098de6250b74e8202e47398b8f55/tumblr_inline_n3bgtfpL3m1r2rd10.jpg"&gt;&lt;img alt="image" src="https://64.media.tumblr.com/82fdacd3ea767db7f5d0996d1e5a4b1d/tumblr_inline_pk2c1antwH1r2rd10_540.jpg" data-orig-height="372" data-orig-width="500" data-orig-src="https://64.media.tumblr.com/e01e098de6250b74e8202e47398b8f55/tumblr_inline_n3bgtfpL3m1r2rd10.jpg"/&gt;&lt;/figure&gt;&lt;/p&gt;
&lt;p&gt;Down the road, we’d like to expand the feature to enable the merging of several discussions from many different users. This would come in handy when replying to several users experiencing the same issue.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Merging users&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;When the merge dialogue comes up, you may also be given the choice of merging the users, in which case the two users mentioned in the dialog box become effectively one and the same. This will occur when an unregistered user replies to a discussion started by a registered user.&lt;/p&gt;
&lt;p&gt;&lt;figure class="tmblr-full" data-orig-height="189" data-orig-width="500" data-orig-src="https://64.media.tumblr.com/83b270ca6fa6fd8954cf06d94fd8b132/tumblr_inline_n3bgv62wpX1r2rd10.jpg"&gt;&lt;img alt="image" src="https://64.media.tumblr.com/f2947b7e57d45e2970b4f4ca71b991da/tumblr_inline_pk2c1bqdZb1r2rd10_540.jpg" data-orig-height="189" data-orig-width="500" data-orig-src="https://64.media.tumblr.com/83b270ca6fa6fd8954cf06d94fd8b132/tumblr_inline_n3bgv62wpX1r2rd10.jpg"/&gt;&lt;/figure&gt;&lt;/p&gt;
&lt;p&gt;**Tender Tip**: BEWARE!! While the ability to merge users is particularly useful, it can indeed lead to some weird stuff when they are not the same person. We’ve made sure you can’t merge your support staff and Jane Doe user profile together, but just keep an eye out when clicking that merge button to ensure two unconnected user profiles aren’t merged unintentionally.&lt;/p&gt;</description><link>https://blog.entp.com/post/66987709504</link><guid>https://blog.entp.com/post/66987709504</guid><pubDate>Thu, 14 Nov 2013 12:10:00 -0800</pubDate><category>tender</category><dc:creator>bemmabobemma-blog</dc:creator></item><item><title>Lighthouse goodness</title><description>&lt;p&gt;Howdy Lighthouse users! I come bearer of good news! We deployed a couple updates in the last few days. It particularly touches spam on public projects, but there are a number of other goodies that should make everyone happier.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Spam&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;A number of prominent public projects have been suffering a lot from spam, and it was time to alleviate the pain. So here are the changes we made:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;&lt;p&gt;If you are an account admin, you can now manage spam across your account by simply searching for &lt;code&gt;spam:1&lt;/code&gt;. This will lead you to a dedicated view where you can mass delete/restore/preview content marked as spam, across all your projects. For big accounts, the first load may take a while, but after that it should work pretty well. If you have spammers with hundreds of post, we can clean them up for you, just email us at support@lighthouseapp.com.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;We used to delete comments with a really high spam score. This was originally intended to limit spam but we found out the spam detection had some issues, and this resulted in false positives. Well no more! All content is created and kept, and you can review it on the spam page. This was the number one complaint we had, and it should now be a thing of the past.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;As your mark content as spam/ham, we get notifications based on a number of parameters and heuristics. This means that in many cases, we&amp;rsquo;ll see when a legitimate user has been flagged as spam incorrectly, and when a spammer seems to be able to post unpunished. We&amp;rsquo;ll take care of those users appropriately so you don&amp;rsquo;t have to, and this should make for a smoother experience for everyone.&lt;/p&gt;&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;You can find more information on the KB: &lt;a href="http://help.lighthouseapp.com/kb/project-management/managing-spam" target="_blank"&gt;http://help.lighthouseapp.com/kb/project-management/managing-spam&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Emails&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;&lt;p&gt;It was a long time coming, but our notifications are now HTML emails. The style is simple and light, just like in Tender, and it should greatly improved readability.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Modifications to existing comments will now generate notifications. I realize this may not be ideal for a few users who edit comments a lot (and I apologize to them), but for the vast majority of users, this is a good thing. Many small changes on tickets went unnoticed before because there was no email.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;The &amp;ldquo;Show me&amp;rdquo; dropdown now include every member of a project when on a project page. Before, it only included account admins. So if you have a lot of project members, and you want to see what they are into, this should help you out.&lt;/p&gt;&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;strong&gt;Conclusion&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;I hope this improves your Lighthouse experience, and I&amp;rsquo;ll be happy to hear your thoughts.&lt;/p&gt;

&lt;p&gt;Cheers!&lt;/p&gt;</description><link>https://blog.entp.com/post/62849421564</link><guid>https://blog.entp.com/post/62849421564</guid><pubDate>Tue, 01 Oct 2013 16:18:25 -0700</pubDate><category>lighthouse</category><dc:creator>asciithoughts</dc:creator></item></channel></rss>
