Find answers. Get support. Join conversations.

Hi Andreas.  Now I´m not sure you are using Online or Onsite or if you use MailGun or your own SMTP for the seding.  Since moste customers use Online with MailGun I will base my reply on this.  When you are sending out an mailing / messagr from Service using MailGun then we are only looking at the domina. So the part after the @ in your exaple the ...."company.com" part.  The customer can use the standard dommain that we proivide for the customer when createing the maibox it looks something like: "company.suocrm.eu"  or the customer can use there own domain.  If they use there own domain then they need to have SPF recrod configurd, and we also recomend having setup DKIM. The SPF record is liked to the domian not the full address, so if the SPF (and DKIM) is configured for the domain it self not the full address.  So in short if you have configurd SFP for the domain, then it should not be any bigger issue to set "No-reply" infont of an e-mail address with the domain.  Just rembembrer that SuperOffice uses the e-mail address where a request gets registerd as sender address, even when you move the request to am other category.  Exmple: Customer sends an e-mail to info@company.com  This email box is on an e-mail server with a fowardgin to the email box linked to noreply@company.com The customer gets an autoreply from this no reply address. Later a supporter moves the request to an other category that is in use, and replies,  Then the reply will sent out from noreply@company.com even if the new category is linked with an other mailbox.  To get around this you will need to do some scripting. 

HI Bas, thanks. We have a single Support mailbox to support Emergency Incident with our Support Teams from diff. Regions for all global Customer. Currently integrierted is our Support Teams in HQ Bremen and Singapore, later planned is more Countries/Regions in Far east. I check in Database, the Escalation Level will be reached if alert-timeout is on time, with exception of Weekend and Red days. Maybe I must buld Logic to calculate this with seprated Time frame and red days for our diff. User groups in Scripts.

That's amazing news, thank you, I will let the customer know 😊

For a customer, we helped with calculating the merge fields in Word. See the example where we needed to find the unit price, but only had the line total price and quantity available.

Hi Samuel, very weird syntax that it does not include the '.', but indeed it works with , only not when using it in a url of a custom object record in the right click context menu, then it uses the value from the last record you actually 'opened', instead of the row that is active, propably it uses the record that is in your currents.  How supported is this? since this is not documented anywhere (so far i can find)

Hi Bas, Our tickets in CS are not only for our service & support but also Billing monthly sent to our Customer. Closing a ticket requires filling in several mandatory fields shown in bold in Tieckt Header; otherwise, it’s IDs will display in a red row to user, this ensures that no tickets being skipped to bill to our customer.   The associated lists of cost center in extra table and project are two of them. We have thousands of projects; For enabling users to quickly and easily find and select his correct project in TicketEdit, we need a filtered project-list with status neither closed nor cancelled, sorted by project start date, includes specific display fields. The Solution in Screen with Simple Value works exactly on our demand. In contrast, triggered dialogs require a step more   to ask user in dialog to confirm the Project Status -- The process lacks conciseness. Similar to the linked cost center list, which includes a "Disable" field in extra table, in TicketEdit should display only active cost centers, the Triggered dialogs require the user to confirm the display of active cost centers via an additional prompt -- an unnecessary step for the user.  In short, triggered dialogs is general good but not ideal for our this application. The ideal approach would be to implement the necessary conditions beforehand -- like simple value in Screen or conditions in Archive of ScreenDesigner.