Hi there,
I'm interested in adding more fields in Customer details. It can be
possible with OTRS? I think that Dynamic Fields are available only in
Tickets or Articles.
I try to keep helpdesk offers support if a customer didn't pay his
previous bill, so a *visible* message (such pop-up, custom
On Oct 11, 2012, at 9:21 AM, Adrià García-Alzórriz
adria.garcia-alzor...@adam.es wrote:
Hi there,
I'm interested in adding more fields in Customer details. It can be
possible with OTRS? I think that Dynamic Fields are available only in
Tickets or Articles.
Yes, this is possible. Add as
El dj 11 de 10 de 2012 a les 09:51 +0200, en/na Roy Kaldung va escriure:
On Oct 11, 2012, at 9:21 AM, Adrià García-Alzórriz
adria.garcia-alzor...@adam.es wrote:
Hi there,
I'm interested in adding more fields in Customer details. It can be
possible with OTRS? I think that Dynamic Fields
On Oct 11, 2012, at 12:14 PM, Adrià García-Alzórriz
adria.garcia-alzor...@adam.es wrote:
El dj 11 de 10 de 2012 a les 09:51 +0200, en/na Roy Kaldung va escriure:
On Oct 11, 2012, at 9:21 AM, Adrià García-Alzórriz
adria.garcia-alzor...@adam.es wrote:
Hi there,
I'm interested in adding more
El dj 11 de 10 de 2012 a les 12:17 +0200, en/na Roy Kaldung va escriure:
On Oct 11, 2012, at 12:14 PM, Adrià García-Alzórriz
adria.garcia-alzor...@adam.es wrote:
El dj 11 de 10 de 2012 a les 09:51 +0200, en/na Roy Kaldung va escriure:
On Oct 11, 2012, at 9:21 AM, Adrià García-Alzórriz
Hi,
I'm also looking into solving the customer's support contract is in
trouble = reduce / cut his access to OTRS problem, *without* changing
code shipped with OTRS (no HTML mods, no PL script tweaks, etc.) and in a
manner that can be automated (integrated with our contract management
system)
=
Sessions are by default (SysConfig Framework-Core::Session) 57600
seconds/16 hours while actually in use and 21600 seconds/6 hours when idle.
BI I haven't yet investigated what happens if an account is disabled and
the customer responds to an issue via email.
The ticket gets created. It gets
Hi,
Thanks for the reply. I read through it a couple of times but, because of
out-of-my-league tech refs, my understanding is mediocre.
Up until The above can effectively handle the email part of this. I think
I understood well. I hate to admit - because it involves .pm code changes -
but I may
BI you imply the customer account needs to be disabled,
I don't confirm this. Changing the email address is sufficient to block
incoming mail with the NewTicket hack. I only wanted to expand on your
inquiry what happens if... By default, random emails create tickets, even
if the user is disabled.
Thanks, a lot, for the input.
I'll keep the NewTicket hack in mind as a fallback.
As far as notifications in agent / customer interfaces go... the
CustomerAccept module is an interesting thing to know about but I can't
imagine making use of it in my situation. In customer's interface I would
BI I would really need to have something shown in the Customer Info box if
the customer account is suspended
That's what I'm saying about changing the email address of the Customer. If
you prefix the word SUSPENDED to the email address, it will be obvious and
automatically address two different
11 matches
Mail list logo
