{"id":934,"date":"2021-02-17T12:52:51","date_gmt":"2021-02-17T12:52:51","guid":{"rendered":"https:\/\/wearesmile.com\/help\/?post_type=ht_kb&p=934"},"modified":"2026-03-27T10:26:45","modified_gmt":"2026-03-27T10:26:45","slug":"the-transition-to-post-project-communications","status":"publish","type":"ht_kb","link":"https:\/\/wearesmile.com\/help\/documentation\/the-transition-to-post-project-communications\/","title":{"rendered":"What happens after launch: support and communication"},"content":{"rendered":"\n

Summary of New Process<\/h2>\n\n\n\n

With the launch of your website, the delivery phase – including testing, bug-logging and fixing – comes to its natural end. Hopefully, you will have enjoyed a close and collaborative relationship with the team at SMILE during delivery. If you\u2019ve launched your website and it remains supported by us through one of our support subscriptions – great! We aim to deliver the same level of service moving forward into the future.<\/p>\n\n\n\n

Pre-launch<\/strong><\/td>Post-launch<\/strong><\/td><\/tr>
Bug-logging through marker.io <\/td>Start a support ticket<\/a><\/td><\/tr>
Reactive changes to scope<\/td>Change control<\/a> \/ Evolve request<\/td><\/tr>
Regular progress meetings<\/td>Tactical monthly meetings
(available as a bolt-on)<\/td><\/tr>
Email<\/td>Email<\/td><\/tr><\/tbody><\/table>
Key differences between pre and post-launch tooling<\/figcaption><\/figure>\n\n\n\n

What kind of things should we expect will change and why?<\/h2>\n\n\n\n

Over of the course of a project’s delivery, deadlines are made, timelines drawn up and hours are planned based on the requirements of the complete package of work. As well as pure design and development, there are a lot of operations hours spent on meetings, reactive correspondence and issue triage.<\/p>\n\n\n\n

With the move to hosting and maintenance, a final product has been signed off for launch. Any changes to that product require a more formal structure in order to sign-off and schedule extra work that is no longer covered by the scope of the working project.<\/p>\n\n\n\n

Bugs that damage the look and functionality of the site now need to be logged as support tickets for investigation and triage by our Support team. Priority decisions and SLAs come into play.<\/a> New feature requests and changes to original scope now need to be time and cost estimated by our Operations team. Long-term strategy can be discussed at regular tactical meetings rather than sometimes-weekly check-ins held during delivery.<\/p>\n\n\n\n

The process generally becomes less reactive and more deliberate and this is all for the better. The original scope has been realised and we can now make plans to keep the site in good shape while helping it to evolve with clear direction moving forward.<\/p>\n\n\n\n

How do I get in touch?<\/h2>\n\n\n\n

Following a successful launch, the quickest and most convenient way to get in touch with us is via the live chat widget which you can find on the home page of our Help Hub<\/a>. The advantage of live chat is that our whole operations team has eyes on it. This protects against response delays due to annual leave or meetings.<\/p>\n\n\n\n

\"\"
Open the live chat widget with the icon in the bottom right corner of the Help Hub<\/figcaption><\/figure>\n\n\n\n

Can I still email the delivery team?<\/h2>\n\n\n\n

Yes – you can still email team members you worked with during delivery, but please bear a couple of points in mind.<\/p>\n\n\n\n

We now have a dedicated Support team that manages post-project queries so issues can be tracked, prioritised and resolved consistently. Project team members still receive emails, and we\u2019ll help where we can, but we can\u2019t guarantee the same fast turnaround<\/strong> that you enjoyed during active delivery. For anything that requires action, tracking or a timely response, we\u2019ll always direct you to the Service Desk or live chat so it can be handled through the correct support workflow.<\/p>\n\n\n\n

Can I still log bugs?<\/h2>\n\n\n\n

Of course! However, the way that you report problems with your site will change. You may have been using a tool such as marker.io to log bugs with us during the testing phase. While this is a quick and convenient way to record a wave of issues for development attention during testing, it is not practical when issue management is governed by SLAs. <\/p>\n\n\n\n

Instead, we ask that you open a support ticket<\/a> with us. Including as much detail as possible will help us to assign a priority level to your ticket and delegate it out to the right team member efficiently. You can attach supporting evidence such as screen captures or recordings directly via the form. Alternatively, you can use a service such as droplr<\/a> to host media and link to it in the description.<\/p>\n\n\n\n

You can read more about how to write a good support ticket here<\/a>.<\/p>\n\n\n\n

I have ideas for new improvements<\/h2>\n\n\n\n

If you’d like to formally request a change to the way your site looks or functions, you can submit a change control request<\/a> with specifications. Our team will endeavour to get back to you within 48 hours with any clarifying questions should they be required. A cost estimate will be sent over to you as soon as the scope is clear.<\/p>\n\n\n\n

If you are an Evolve customer, you should also have access to a dedicated request form<\/a> in your project’s Asana board.<\/p>\n\n\n\n

Is this a bug, or a feature request?<\/h2>\n\n\n\n

This is one of the questions we hear most during the weeks following a project’s completion, and it\u2019s completely normal to be unsure.<\/p>\n\n\n\n

Quick guide<\/strong><\/p>\n\n\n\n