Tickets

Bring requests into one working record

A customer may report an access problem by email while another sends the same question through a portal form. Capture the incoming source and identify the person behind the request before deciding which customer record it belongs to. Repeated delivery of the same connector event should return the existing ticket, keeping one conversation instead of creating several copies for the team to chase.

A recognizable email address helps with intake, but it does not establish a portal identity. An unverified request can remain available for the support team to investigate without granting someone access to a customer’s earlier tickets. Customer-supplied priority, ownership and internal fields are reviewed under the configured service policy rather than accepted as instructions to the system.

Separate the reply from the investigation

Public replies explain the next step to the customer. Internal notes hold diagnostic detail for authorized colleagues working the request. An attached log follows the same visibility boundary, including when somebody opens its direct download link. Marking a comment internal must protect its body and files; it is more than a different label in the conversation.

Before sending a reply, review the customer, the question being answered and the information included. A specialist can share a public explanation without exposing the internal reasoning or another customer’s data. The ticket retains who made the contribution and when, so the next assigned agent can understand the investigation without relying on a separate personal conversation.

Check delivery without losing the conversation

A reply sent through email may have an uncertain provider result. Keep that uncertainty visible and reconcile the original message before sending another copy. A public portal reply becomes a response when it is durably available to its intended customer; an outbound email needs the provider’s correlated acceptance. Automated acknowledgments and internal notes do not establish the first agent response.

The finished ticket record should tell a coherent story: what the customer asked, who worked on it, which messages were shared and what outcome was reached. A customer response racing with automatic closure must return the ticket to the right working state rather than disappearing behind a completed label.

Review the working record

Before handing the request to a colleague, confirm its current customer, assignee, public conversation and outstanding service target. These details allow the next person to continue from the recorded outcome, without reopening private conversations or assuming that a queued notification has already reached the customer.