Find answers. Get support. Join conversations.

I just thought that I would share a bit about how we at SuperOffice Customer Experience Center are working with signatures — maybe it will bring some inspiration. No matter how much we tried to provide guides, templates in text, or templates in HTML, the signatures never looked the same for all users. Some supporters also came up with the idea to added an opening phrase with varaibles for the customer's name. This is one way to do it, but it's not optimal since a signature is by definition placed at the bottom of the message. It may not sound like an issue to have 2 or 3 rows of spacing at the top of your message, but trust me — when you spend your entire day, five days a week, replying to customers, having to delete extra rows in every single message will get to you, and the time spent adds up. On top of that, the signature is only in one language, while many of our supporters work in two languages and may need to cover a third if needed. Along came Request Type. This tool allowed us to include a reply template whenever we press reply in a request. The benefit of reply templates is that they will always look the same for all users, they support language variants, and they allow for more advanced formatting. We can also have different tempaltes added for different request types.  At this point, things started to look good. We could now have several language versions of the template based on the preferred language of the contact person we were communicating with. If we wanted to make any changes to the signature, we only had to change it in one place per lanugage. The last thing we did to complete the signature was to add the user's title. Unfortunately, the person card title for the user is not accessible from a request template, so what I did was create an extra field called "title." (For faster adding of titels to users, and to get an overview of every users titels, you can use a ejuser selection in the old Service module)  To make sure the signature looks good regardless of whether the user has a title — and to apply slightly different formatting depending on the title — I added some IF statements in the HTML of the template. In the source code it looks like this: And in the editor it looks like this: When a reply is created in a request, the signature will only show one of the three versions of the department field. I also made sure to add a few <br /> tags as spacing between the opening phrase and the signature. This gives the supporter a clear area to type their message and helps keep the formatting consistent. This also results in single line breaks instead of the 1.5-line spacing that the editor for New Service uses by default.   I hope you found this solution inspiring — feel free to share other tips or setups you have created!

Hi This sounds great and something we have missed for a long time. As heavy users of Customer Service, I do hope that it will offer capabilities similar to the Outlook plugin so that we can either create a new case from a chat or add it to an existing case. Looking forward to getting this enhancement Best regards Ole

SuperOffice for Teams Save your Microsoft Teams conversations and files straight into SuperOffice – so important customer chats and documents  don't  get lost.   Pilot start: TBD   What is this pilot about?   SuperOffice for Teams connects your Microsoft Teams conversations with your CRM. Instead of searching through channels and chats to  find  what a customer said last week, you save the conversation to SuperOffice – right where it belongs.   With SuperOffice for Teams, you can:   Save messages from chats and standard channels to SuperOffice.   Save a single file from a standard channel message.   Archive a date range of messages – like "Yesterday" or "Last 7 days."   Generate an AI summary of the conversation before saving. Requires AI Labs.  

Hi everyone Please may I request as many people click follow on this wish report - I have been trying to get my fellow work colleagues to also follow this but they seem to click follow and nothing happens at the moment.  I think it is a massively important quality of life change - surely you all will agree. Hopefully more follows means it can be looked at quicker Bug info - Wish: possible to have criteria field value "Is (not) Empty"

Hello on one site we have an strange issue with IMAPS. It is a Lotus Notes server with latest version and we use a selfsigned certificate. When we switch to IMAPS, then quite often Service is not able to load the emails. It looks, that the oldest email is blocking all the others. Some times a solution is, to delete the oldest email or move it to a different folder. But when we switch back to IMAP protocoll, then this issue does not happen.  All needed ports are open and the certificate works.  Does have anyone know similar issues and can give me a hint, what to do. Thank you! 

Have a customer with remark concerning 'archiving as task'.   I have not seen this mentioned in documentation, but before any wishlist entry:   When we archive an email as a task, we would also need to include any attachement(s) in the email that is the basis for this task. Am I missing something in existing capability, or is this a wishlist item, or should it be ?   Thank you