First, this:
viewtopic.php?f=60&t=7531
KPS wrote:We have direct customers who may have multiple users contacting us with support issues. I'm guessing a create companies and customers for this and assign them to each other. I'm guessing that customerid is really companyid and that's how to link them. I'm not sure what the customerid should be or why it's not autogenerated as a unique id.
When creating a user by hand, the CustomerID is free text. When sync with LDAP it can be anything (Department?) but default is email (unique).
The rest of your question I'm not sure I follow, and it makes a difference in the answer.
"the same person may log calls for any of the customers."
If the partner is an agent, this reduces complexity as the partner can have limited access to simply create tickets in his queue (login at index.pl) for the customer(s) he represents. You'd probably manage creating customers if these are repeat customers, or just let partner create email or phone tickets for non-customers. (Tickets can be created without any connection to the Customer database backends.)
In fact, you can create a web form specifically for the partner that submits the ticket as an email as if the partner's customer sent it directly to you. I'd give that webform an email address that goes to a queue that DOES NOT have an autoresponse.
KPS wrote:If I set up the companies as Microsoft - LA, Microsoft - London and Microsoft - New York. Then set up the customers as
dave.smith@microsoft.com,
jo.davies@microsoft.com and
support@microsoft.com. How can assign these three users to each of the three companies or is there any easier way of doing it and I'm going the wrong way about it.
Do you even care? I mean this in a practical sense. If *you* are needing to store demographic information on the (repeat?) customers from the partners and the partners are managing the customer tickets as agents, then yes. If you collect, for instance, ticket-specific customer demographics (phone, time zone, OS) in Dynamic/FreeText fields, you may not need to store that in a *customer* database.
OTRS 6.0.x (private/testing/public) on Linux with MySQL database.
Please
edit your signature to include your
OTRS version, Operating System, and database type.
Click Subscribe Topic below to get notifications. Consider amending your topic title to include [SOLVED] if it is so.
Need help? Before you ask