1. Open Support > Support Tickets and review the full thread, customer identity, department and affected service. Check recent related tickets before starting another investigation.
2. Assign an accountable staff member and set the priority according to actual impact. Record the affected users, service and time the issue began.
3. Use an internal note for investigation findings, provider references and handover details. Keep the public reply focused on the customer's issue and the next useful step.
4. When requesting information, ask for a precise error, timestamp and reproducible action. Use the authorised process for sensitive access details rather than asking for passwords in ordinary ticket text.
5. Update the status when waiting for a customer, actively working or closing the resolved request. Follow your configured status definitions and department assignment rules.
6. Before closing, record what changed and how the result was checked. Include a relevant knowledgebase link where it helps the customer repeat the solution.

Merge only tickets that belong to the same customer conversation and can safely share their contents and recipients. Inspect CC addresses and contact access first. Preserve provider case numbers and evidence in the surviving thread.

When handing a ticket over, state the current condition, completed checks, outstanding uncertainty and next action. Use the ticket log to resolve questions about status or assignment changes.

A customer's site is reachable, but a scheduled export still fails. Instead of leaving only “please check”, place a concise handover in the internal note field:

Impact: daily catalogue export fails; storefront remains available.
Started: 06:10 UTC, after the last successful export yesterday.
Checked: hosting access, available storage and the recorded job error.
Provider case: CASE-EXAMPLE-104, awaiting worker-log review.
Next action: assigned technician compares the next run with that case.
Customer update: explain the export status after the next confirmed result.

Replace the illustrative identifiers with the actual case details. Keep ownership assigned to a named staff member, use the configured waiting or working status, and leave the customer conversation accessible. The next operator should be able to continue without repeating completed checks.

• Set up HostBill support departments
• Manage HostBill client contacts and access permissions
• Build a structured HostBill knowledgebase
• Prepare a useful escalation to your upstream hosting provider

• HostBill support ticket management
• HostBill ticket department general settings
• HostBill client contacts