| Key: |
CHD-903
|
| Type: |
New Feature
|
| Status: |
Closed
|
| Resolution: |
Fixed
|
| Assignee: |
Unassigned
|
| Reporter: |
Joe Geck
|
| Votes: |
3
|
| Watchers: |
1
|
Clone this issue
|
|
If you were logged in you would be able to see more operations.
|
|
|
Original Estimate:
|
Unknown
|
Remaining Estimate:
|
Unknown
|
Time Spent:
|
Unknown
|
|
Issue Links:
|
Related To
|
|
This issue is related to:
|
|
CHD-537
Implement Service Levels (SLA) Ticket...
|
|
|
|
|
|
|
| Value: |
2 - Significant Value
|
Summary:
http://www.cerb4.com/forums/showpost.php?p=7403&postcount=1
Assigning service levels based on domain would allow brand new addresses (not already a contact) to also work properly with SLA. Currently you have to assign an SLA to a specific address already in your address book, so this would give you the option to SLA prioritize an entire domain (or organization).
[[quote]]
One issue we are having though is automatically assigning Service Levels to inbound addresses. This is not to say we're having an issue assigning SL's to organizations or individual addresses, but with assigning those levels automatically if an address is not already in the address book.
Example:
We wish to have a specific Service Level priority set for any sender from a certain domain (@example.com). We do not have the addresses from @example.com that will be emailing us.
Is there any way in the example above to assign the service level automatically (in our specific example, @example.com would have higher priority than standard senders)? Or, based on domain, to automatically tie an inbound address not already in the address book to an Organization and use it's SL?
[[/quote]]
|
|
Comment by Joe Geck [06/Nov/08 02:55 PM]
SLA's based on domain could be part of an entire SLA escalation system if we decide to do so.
Comment by Joe Geck [27/Jun/09 12:10 AM]
Better handled with filter extensions
|
|
