Actually tickets work this way:
- You send a ticket - you receive an email with your original message and the key to read it.
- There's some status change - moved the ticket to a superior if it's not attended in two days, for expample. No email is generated.
- You get a response. You receive an email again with the key to read. This email does not include the response, you have to read the ticket with the key to read it.
- You answer again. No email is generated.
- You get another response. You receive an email again with the key to read. This email does not include the response, you have to read the ticket with the key to read it.
- After sometime, ticket expires and it's deleted.
My suggestion is this, each time you get a response, or you write an answer, this answer is also emailed to your email account.
Why is this suggestion needed?
Imagine in your universe you get the permission to connect various accounts from the same IP (you and your brother, for example). Now imagine one year passes, a new GO comes in, and he bans you for multi. I suppose each account has its own notes, but, if you are banned, and don't have access to the tickets, how can you proof that this was already told and you were allowed?
More examples of this can be given (e.g. each time somebody with lower rank pays you a moon shot you need to sent a ticket. If in your ally you make 10 or so attacks per week and the GO says, ok, don't need each attack a ticket and later one GA bans you... how can you proof he allowed you before?)
Another usefull thing is having a record in your email of all your tickets. When you have to report an ACS with 5 people attacking, 5 or more recycling and complex resources sending, keeping a copy of that for future tickets comes handy.
- You send a ticket - you receive an email with your original message and the key to read it.
- There's some status change - moved the ticket to a superior if it's not attended in two days, for expample. No email is generated.
- You get a response. You receive an email again with the key to read. This email does not include the response, you have to read the ticket with the key to read it.
- You answer again. No email is generated.
- You get another response. You receive an email again with the key to read. This email does not include the response, you have to read the ticket with the key to read it.
- After sometime, ticket expires and it's deleted.
My suggestion is this, each time you get a response, or you write an answer, this answer is also emailed to your email account.
Why is this suggestion needed?
Imagine in your universe you get the permission to connect various accounts from the same IP (you and your brother, for example). Now imagine one year passes, a new GO comes in, and he bans you for multi. I suppose each account has its own notes, but, if you are banned, and don't have access to the tickets, how can you proof that this was already told and you were allowed?
More examples of this can be given (e.g. each time somebody with lower rank pays you a moon shot you need to sent a ticket. If in your ally you make 10 or so attacks per week and the GO says, ok, don't need each attack a ticket and later one GA bans you... how can you proof he allowed you before?)
Another usefull thing is having a record in your email of all your tickets. When you have to report an ACS with 5 people attacking, 5 or more recycling and complex resources sending, keeping a copy of that for future tickets comes handy.
