Automatic customer configuration

Hi! We are working in the migration from FreshDesk to OTRS. One feature in FreshDesk is that Customers are tied to a "domain name" (example: @mycustomercompany.com), and then all tickets created from users in that domain become users for that customer. Is that possible in OTRS? How to implement this feature? I would like to avoid the maintenance required for customer's users. Thanks for any help, -- Atenciosamente, Edson Carlos Ericksson Richter

Hello,
In OTRS you need to have customer user and customer companies, you can use
create customer companies and asociate domain name as Company ID and then
when adding customer users you can link them to the company by that ID.
To avoid maintenance of customer users, you would need to use one or more
external customer backends, but that means you still need to maintain your
external backends.
OTRS needs customer user's and that cannot be avoided.
Regards
2015-12-01 12:38 GMT-06:00 Edson Richter
Hi!
We are working in the migration from FreshDesk to OTRS. One feature in FreshDesk is that Customers are tied to a "domain name" (example: @mycustomercompany.com), and then all tickets created from users in that domain become users for that customer.
Is that possible in OTRS? How to implement this feature? I would like to avoid the maintenance required for customer's users.
Thanks for any help,
-- Atenciosamente,
Edson Carlos Ericksson Richter
--------------------------------------------------------------------- OTRS mailing list: otrs - Webpage: http://otrs.org/ Archive: http://lists.otrs.org/pipermail/otrs To unsubscribe: http://lists.otrs.org/cgi-bin/listinfo/otrs
-- *Alvaro Cordero RetanaConsultor de Tecnologias* *Tel: 22585757 ext 123* *Email:* alvaro@gridshield.net

Hi Edson,
On 01 Dec 2015, at 19:38, Edson Richter
We are working in the migration from FreshDesk to OTRS. One feature in FreshDesk is that Customers are tied to a "domain name" (example: @mycustomercompany.com), and then all tickets created from users in that domain become users for that customer. Is that possible in OTRS? How to implement this feature? I would like to avoid the maintenance required for customer's users.
First: Welcome to OTRS :-) I don’t have a out-of-the-box solution ready, but if you can create invoker and operations for the generic interface, you may listen to the TicketCreate event and create a new customer user record assigned to the right customer. You may also do this with a perl-only event module listening to the TicketCreate event. :-) -- Cheers, Nils

Em 01/12/2015 20:22, Nils Leideck escreveu:
Hi Edson,
On 01 Dec 2015, at 19:38, Edson Richter
wrote: We are working in the migration from FreshDesk to OTRS. One feature in FreshDesk is that Customers are tied to a "domain name" (example: @mycustomercompany.com), and then all tickets created from users in that domain become users for that customer. Is that possible in OTRS? How to implement this feature? I would like to avoid the maintenance required for customer's users. First: Welcome to OTRS :-)
Thanks, Nils! So far, we have found OTRS really lean and flexible.
I don’t have a out-of-the-box solution ready, but if you can create invoker and operations for the generic interface, you may listen to the TicketCreate event and create a new customer user record assigned to the right customer.
You may also do this with a perl-only event module listening to the TicketCreate event.
Thanks for your tips. Unfortunately, Perl it is not in the list of languages I do program with :-) I'll try to google around for "TicketCreate" and see if I find something. Regards, Edson
:-)
-- Cheers, Nils
--------------------------------------------------------------------- OTRS mailing list: otrs - Webpage: http://otrs.org/ Archive: http://lists.otrs.org/pipermail/otrs To unsubscribe: http://lists.otrs.org/cgi-bin/listinfo/otrs

You don't actually need a 'customer user', unless that customer wants to log on to the OTRS system itself. For the purposes of raising a ticket and delivering support, the customer really doesn't need to logon and can do it all via email. In this situation, you don't need a customer user stored in the database at all. This means there is no need to create Customer Users at all, let the system handle that. For auto-grabbing the "domain name" as the CustomerID, look into a postmaster filter that grabs the domain portion of the FROM email address and assign that to X-OTRS-CUSTOMERID email header. Oh, and I think you have to make sure to turn on CustomerCompany in the config file to get this functionality to work properly. Cheers Rob. -----Original Message----- From: otrs-bounces@otrs.org [mailto:otrs-bounces@otrs.org] On Behalf Of Edson Richter Sent: 01 December 2015 18:39 To: otrs@otrs.org Subject: [otrs] Automatic customer configuration Hi! We are working in the migration from FreshDesk to OTRS. One feature in FreshDesk is that Customers are tied to a "domain name" (example: @mycustomercompany.com), and then all tickets created from users in that domain become users for that customer. Is that possible in OTRS? How to implement this feature? I would like to avoid the maintenance required for customer's users. Thanks for any help, -- Atenciosamente, Edson Carlos Ericksson Richter --------------------------------------------------------------------- OTRS mailing list: otrs - Webpage: http://otrs.org/ Archive: http://lists.otrs.org/pipermail/otrs To unsubscribe: http://lists.otrs.org/cgi-bin/listinfo/otrs
participants (4)
-
Alvaro Cordero
-
Edson Richter
-
Nils Leideck
-
Rob Shears