|
|
| (9 intermediate revisions by 4 users not shown) |
| Line 1: |
Line 1: |
| − | == Getting help from Emersion ==
| + | This page has been [https://resources.emersion.com/display/EKB/Support+and+Help+from+Emersion moved] |
| − | | |
| − | While we understand sometimes the situation calls for it, we request that you kindly do not email staff directly. This also includes raising a ticket but carbon-copying other staff unless you have been requested to do so. Due to the overwhelming number of emails our staff receive daily, it is regrettable that many direct emails are lost or missed, resulting in frustration. We request all clients use one of the following channels so we can ensure you get the speediest and best service possible. At Emersion, it is company policy that all technical fault reports, work orders, project deliverables, account queries, sales queries and alike is tracked & managed via the Emersion Support Portal, powered by ConnectWise.
| |
| − | | |
| − | Raise a ticket in the [http://support.emersion.com.au Emerson Support Portal]
| |
| − | | |
| − | '''''"If it isn't in a ticket, we do not know about it"'''''
| |
| − | | |
| − | Once a ticket is raised you will receive a tracking id, commonly called a ticket number. When referring to the issue with staff, you will be always be asked for the ticket number. If you have not raised a ticket, our staff will request immediately that you do so. When you wish to update a ticket in writing, you can do so via either or via the Emersion Support portal web interface.
| |
| − | | |
| − | Occasionally a ticket may be time-sensitive. If your request is time sensitive, please make this clear in the ticket and the reason why. This will greatly assist our staff prioritise your ticket during the ticket triage process.
| |
| − | | |
| − | == Raising a Ticket ==
| |
| − | | |
| − | The Emersion Support system has a number of queues to ensure your ticket is sent to the most appropriate team. Raising a ticket to the correct service board will avoid unnecessary delay in addressing your query.
| |
| − | | |
| − | Emersion prefers that you use the [http://support.emersion.com.au Emerson Support Portal] to raise and update tickets, but when cases where that is not possible, you can raise and update tickets via email.
| |
| − | | |
| − | === Technical Support ===
| |
| − | [mailto:emesupport@emersion.com.au emesupport@emersion.com.au]
| |
| − | Contact our technical support team for any technical support matter such as reporting faults and defects with your services with Emersion. In all cases, please provide us with the following:
| |
| − | | |
| − | <ul>
| |
| − | <li> A detailed description of the problem</li>
| |
| − | e.g. what you attempting to do? What were you expecting to see vs what you actually saw happen?
| |
| − | <li> The conditions to reproduce the issue</li>
| |
| − | <li> Any errors you have received</li>
| |
| − | <li> Record IDs where the problem arose</li>
| |
| − | e.g. service ID, note ID, Account ID
| |
| − | <li> Details regarding what checks you have performed to try and isolate the problem yourself, such as any screens shots that support your concern, or report output that reflects what you are seeing.</li>
| |
| − | </ul>
| |
| − | | |
| − | When we receive this information we can proceed with investigating your issue. Escalations where it is clear there has been no investigation performed by a client will be returned as insufficient information.
| |
| − | | |
| − | ===Sales===
| |
| − | [mailto:sales@emersion.com.au sales@emersion.com.au] | |
| − | For sales enquiries & sales requests, new features, new services, extra training, business analysis and help with your business development.
| |
| − | | |
| − | ===Work Orders===
| |
| − | [mailto:workorder@emersion.com.au workorder@emersion.com.au]
| |
| − | Existing clients can submit a work order during times where you need Emersion undertake work for you that we typically have done for you in the past, and for which you are happy to be invoiced immediately for upon completion. Examples include:
| |
| − | <ul>
| |
| − | <li> Enabling a downstream retail service provider</li>
| |
| − | <li> Importing data</li>
| |
| − | <li> Updating records in bulk because it is undesirable to do so via the user interface</li>
| |
| − | <li> Double-check the configuration of a package, package plan, rate card prior to enabling and ordering new services</li>
| |
| − | </ul>
| |
| − | | |
| − | Work requests are typically less than 4 hours’ work. All work requests are estimated (time) for your approval and billed in arrears. Please allow at least 14 business days for your request to be completed once submitted.
| |
| − | | |
| − | ===API Support===
| |
| − | [mailto:APISupport@emersion.com.au APISupport@emersion.com.au]
| |
| − | For submissions of requests, bugs and fault reports for Emersion’s API where it is suspected Emersion is at fault. Please be aware that all queries & support issues related to the API are billable until it is proven and acknowledged that Emersion is at fault.
| |
| − | | |
| − | ===Accounts Receivable===
| |
| − | [mailto:billing@emersion.com.au billing@emersion.com.au]
| |
| − | This is for billing enquiries related to your services with Emersion. If you have any billing disputes or SLA claims, please direct your request here.
| |
| − | | |
| − | ===General Finance issues===
| |
| − | [mailto:accounts@emersion.com.au accounts@emersion.com.au]
| |
| − | Includes accounts payable, company finance, etc.
| |
| − | | |
| − | == Emersion Projects ==
| |
| − | If you are undertaking a formalised project the following queues are to support you. If you have a problem or issue with the system, please ensure your email is detailed and specific. Please include at a minimum:
| |
| − | | |
| − | <ul>
| |
| − | <li> The environment on which you encountered the problem</li>
| |
| − | <li> The account you were using</li>
| |
| − | <li> Any error messages you encountered</li>
| |
| − | <li> What were you attempting to do?</li>
| |
| − | <li> What you were expecting to see occur</li>
| |
| − | <li> What actually occurred</li>
| |
| − | </ul>
| |
| − | | |
| − | Escalations where it is clear there has been no investigation performed by a client will be returned as insufficient information.
| |
| − | | |
| − | Project tickets are a different category of ticket. Each project ticket forms a key part of your project plan. Your project plan can be viewed under the '''Projects''' tab of the [http://support.emersion.com.au Emerson Support Portal]. While you are engaged in a project with Emerson, it is essential you review and update these tickets regularly and when requested. It's important to know that while you can update a project ticket, you cannot raise a new ticket. If you wish to raise a matter please use the following service desk queues that Emersion has reserved for clients undergoing a project.
| |
| − | | |
| − | === Project Support ===
| |
| − | [mailto:project-support@emersion.com.au project-support@emersion.com.au]
| |
| − | This queue is specifically for clients who are undergoing a project with Emersion. While your project is in progress, please refer all matters regarding the project and project deliverables here.
| |
| − | | |
| − | === Onboarding Projects ===
| |
| − | [mailto:onboarding@emersion.com.au onboarding@emersion.com.au]
| |
| − | This queue is specifically for new clients implementing Emersion in their company.
| |
| − | | |
| − | == Updating your ticket via email ==
| |
| − | The system will automatically add your email to the ticket description if you use the following convention in the '''summary''' of your email. Please use the following conventions when updating a ticket.
| |
| − | | |
| − | Option 1
| |
| − | <blockquote>Ticket #xxxx/ <subject></blockquote>
| |
| − | Option 2:
| |
| − | <blockquote>SR #xxxx <subject></blockquote>
| |
| − | | |
| − | ''Examples that will correctly append your email to the relevant ticket''
| |
| − | <blockquote>Ticket #xxxx/ data import errors</blockquote>
| |
| − | <blockquote>SR #xxxx data import errors</blockquote>
| |
| − | | |
| − | ''Examples that will not append your email to the relevant ticket''
| |
| − | <blockquote>#xxxx data import errors</blockquote>
| |
| − | <blockquote>Ticket #xxxxData Import Errors</blockquote>
| |
| − | | |
| − | Failure to use the correct format will result in either a duplicate ticket being created, or Emersion not receiving your update. In either case, this often results in unnecessary frustration as the Emersion staff member who is assigned to your original ticket, does not know that you have attempted to update it. Emersion will not be held responsible and no SLA claim will be deemed valid for clients who fail to update tickets appropriately and correctly.
| |
| − | | |
| − | == Priorities and Escalation Process ==
| |
| − | | |
| − | Emersion always works hard to ensure that the appropriate resources and level of focus are applied to your request to ensure a timely resolution. However it is not always possible for us to attend to your request straight away. The Service Level Agreement (SLA) provides for response times for Severity 1 and 2 issues.
| |
| − | | |
| − | # Emersion will prioritise Severity 1 and 2 issues above all other work.
| |
| − | # We will prioritise scheduled work (projects and work requests) following Severity 1 and 2 issues.
| |
| − | # Severity 3, 4 and 5 issues will be actioned in accordance with the following policy:
| |
| − | ## In order of the assigned priority
| |
| − | ### Tickets rated as Severity 3 will be actioned before those rated at Severity 4 and 5, etc
| |
| − | ## Tickets with the same severity will be addressed in order of the queue (oldest ticket first).
| |
| − | | |
| − | === Changes in Priority ===
| |
| − | | |
| − | Emersion are sensitive to the fact that sometimes, changes in priority can occur. If you are waiting for a ticket to be addressed, and the matter is becoming time-sensitive, it is essential that you update the ticket before it becomes time-critical so we can re-prioritise your ticket accordingly. Please include a '''reason''' for requesting a ticket escalation. Context of a situation is rarely obvious. Explaining why a ticket has become more urgent assists us greatly and ensure all customers receive the right level of support at the right time.
| |
| − | | |
| − | === When to Escalate ===
| |
| − | | |
| − | If after you have checked the status and updated the ticket, you are still not satisfied with the progress of your request, you are invited to escalate directly to a Manager. By invoking the escalation process, additional levels of Emersion management attention, procedure reinforcement and resource prioritisation are brought to bear on resolving your support request.
| |
| − | | |
| − | Use the escalation procedure only when:
| |
| − | * you believe that the SLA time frame for a technical support issue has not been met. Please refer to SLA time frames in your agreement.
| |
| − | * the delivery date on a Work Order has not been met and you have not been provided with a new date.
| |
| − | * the priority of your issue changes or becomes time-critical or time-sensitive.
| |
| − | * you have attempted to contact the person allocated to your ticket and have been unsuccessful.
| |
| − | | |
| − | Do not use the escalation procedure to:
| |
| − | * Demand Emersion resolve a Sev 3, 4, 5 technical support matter if we have given you a valid workaround.
| |
| − | * you have made no attempt to contact the resource(s) allocated to the ticket and request an update (you can see who is assigned your ticket via the Emersion Support Portal).
| |
| − | | |
| − | ''Escalations should not be a matter of course for every ticket, all the time. Emersion will ignore unreasonable or unjustifiable escalation requests''
| |
| − | | |
| − | ==== Who to Escalate to ====
| |
| − | | |
| − | If you need to escalate an issue, please try the following points of contact in order that they are listed.
| |
| − | | |
| − | Sharon Carpenter, Operations & Project Manager 03 8658 9470
| |
| − | | |
| − | Martin Edge, CTO 03 8658 9489
| |
| − | | |
| − | Paul Dundas, CEO 03 8658 9488
| |
