This agreement sets out how quickly we respond to and complete work for TTOY Digital and SmartFlowCRM clients. It applies to every client on an active website, hosting, maintenance, web app or SmartFlowCRM plan.
Our targets are what we aim for, not a guarantee of how long every job takes. Most requests are done well inside them. If something is going to take longer, we'll tell you before the deadline passes, explain why and give you a new date.
A few terms we use throughout:
Working day: Monday to Friday, 9am to 5pm UK time, excluding bank holidays in England.
Response: we've read your request, confirmed it and told you what happens next. Kai, our AI assistant, answers many questions instantly. If Kai fully resolves your question, that counts as both a response and a completion. If Kai passes it to our team, the response target runs until a person picks it up.
Completion: the work is done and live, or ready for you to check and approve.
The clock starts when we receive your request with everything we need to do it.
Our support team works Monday to Friday, 9am to 5pm UK time. Requests that arrive outside those hours are picked up at the start of the next working day, apart from critical issues on websites we host and web apps we support (see priority levels).
The fastest way to reach us is the chat widget. It's the bubble in the bottom right of SmartFlowCRM, your client portal and your WordPress dashboard. Kai, our AI assistant, answers there first and can resolve many questions on the spot, day or night. Anything Kai can't resolve goes to our team with the details we need, so we can start straight away.
For how-to guides and answers to common questions, you can also browse our help centre at any time. It's often the quickest way to sort something yourself.
When you raise a request:
Log one request per change. Five website changes means five requests. It lets us track each one and stops small jobs getting stuck behind big ones.
Be specific. Tell us the page or screen, what's there now, what it should say or do, and include any images or copy. For problems, use the widget to take a screenshot or record a short video showing what's happening. It's the quickest way for us to see the issue and fix it first time.
Choose the right option in the widget: ask a question, submit a service request, report an issue or request a feature.
Some issues are easier to understand live. The chat widget has support calls built in, so we may invite you to a quick call where you share your screen and show us what's happening. You don't need to install anything, and we'll only ask when it'll get your issue fixed faster.
You can also email us at [email protected], but email or phone requests may take longer to log and won't be prioritised until they're in our system.
Every request gets a priority based on its impact on your business, not how urgent it feels. Kai sets an initial priority when you log it and our team checks it. If we think the priority is wrong, we'll tell you and agree it with you.
Priority | What it means | Examples | First response | Target fix or workaround |
|---|---|---|---|---|
P1 Critical | Your site or system is down or unusable for everyone | Website or web app offline, checkout or app not taking payments or orders, site or app hacked, customer data exposed, SmartFlowCRM login failing for all users | Within 1 working hour | Within 4 working hours |
P2 High | A key feature is broken, but the business can still run | Contact form not sending, bookings not syncing, a key screen in your web app not working, a core workflow not firing | Within 4 working hours | Within 1 working day |
P3 Normal | Something isn't right but has a workaround, or a standard change request | Layout issue on one page, content updates, new pages, workflow changes | Within 1 working day | See the service tables below |
P4 Low | Questions and minor tweaks | Colour tweak, how-to question | Within 2 working days | Planned in when capacity allows |
For P1 issues on websites we host and web apps we support, our monitoring alerts us automatically, so we're often working on it before you've noticed. P1 targets outside working hours are best endeavours.
If a web app is down because of an outage on the underlying cloud platform or a connected service, such as a payment provider, we'll escalate it straight away and keep you updated until it's fixed. The fix itself then sits with them (see Web apps).
These targets are included with all our website packages. They cover standard changes; bigger pieces of work are quoted and scheduled separately.
Request | Completion target | Notes |
|---|---|---|
Changes to existing pages (text, images, links) | 5 working days | Up to around an hour of work per request |
New page using an existing layout | 5 working days | You supply the copy and images |
Blog post upload | 5 working days | You supply the finished post and images |
Bug fix on your site (P2 or P3) | See priority levels | Target depends on impact |
New page with a new design, new functionality or a new section of the site | Quoted separately | We'll give you a timescale with the quote |
If we need anything from you to finish a change, like copy, images or sign-off, the clock pauses until we have it. We'll send one reminder after 3 working days, and close the request after 10 working days with no reply. You can reopen it at any time.
We aim for 99.9% uptime each month on sites we host, measured by monitoring that checks your site every 60 seconds. That works out at no more than about 43 minutes of unplanned downtime a month. Planned maintenance doesn't count towards it.
This section only applies to sites we host. If your site is hosted elsewhere, your host's own terms apply, although we'll still help where we can.
Request | Target |
|---|---|
Site down (P1) | Response within 1 working hour, fix or workaround within 4 working hours |
DNS changes | Within 1 working day |
Email account creation | Within 1 working day |
Password reset | Within 1 working day |
SSL certificate issue | Within 1 working day |
Moving a site to us from another host | Quoted and scheduled separately |
We carry out planned maintenance outside working hours where possible. If it's likely to cause noticeable downtime, we'll give you at least 2 working days' notice.
You can check live service status, current incidents and planned maintenance at any time on our
status page. It's the first place to look if your site seems slow or offline.
DNS changes can take up to 48 hours to show everywhere after we make them. That delay sits with the internet, not us, so it doesn't count against our target.
These apply to sites on our WordPress maintenance plan, whether or not we host them.
Service | Target |
|---|---|
Backups | Daily, stored off-site, kept for 30 days |
Restore from backup | Within 1 working day of the request (sooner for P1 issues) |
WordPress core, plugin and theme updates | Checked and applied at least weekly |
Critical security updates | Applied within 1 working day of release |
Uptime monitoring | Every 60 seconds, 24/7, with instant alerts to our team |
Malware found | Response within 1 working hour, clean-up started the same working day |
Update breaks your site | Rolled back or fixed within 4 working hours |
Monthly care report | Sent in the first 5 working days of each month |
Not every problem needs a restore. We'll always try to fix an issue first and only roll back if that's the quickest safe option, as a restore can undo recent changes such as new orders or form entries.
These targets cover changes we make in SmartFlowCRM on your behalf. Workflows often need testing before they go live, so complex changes may take longer. If so, we'll agree a date with you up front.
Request | Completion target |
|---|---|
Changes to an existing workflow | 5 working days |
New simple workflow (up to around 10 steps) | 5 working days |
New complex workflow or integration | Quoted and scheduled separately |
Email campaign build | 5 working days from receiving final copy and images |
Adding or removing users | Within 1 working day |
Login or access problem for one user (P2) | Within 1 working day |
Platform down for all users (P1) | Response within 1 working hour |
SmartFlowCRM runs on infrastructure provided by a third-party platform. If they have an outage, we'll keep you updated through the news section of the chat widget, but the fix sits with them and falls outside our targets.
This section covers custom web apps we build for you, such as booking systems, ordering apps, portals and internal tools. Your app runs on a managed cloud platform from one of our technology partners, which handles the servers, security certificates and global delivery.
We monitor your app around the clock and aim for it to be available at least 99.9% of the time. We can't guarantee a figure, because the underlying cloud platform doesn't guarantee one to us. What we do promise is that if your app goes down, we'll know about it, we'll be on it, and we'll keep you updated until it's back.
The platform may carry out maintenance or updates with little notice. They usually do this at quiet times, and we'll pass on any notice we get.
Request | First response | Target fix or workaround |
|---|---|---|
App down or unusable for everyone (P1) | Within 1 working hour | Within 4 working hours where the fault is in our code |
Security issue (P1) | Within 1 working hour | Made safe within 4 working hours, then fully fixed |
Key feature broken, such as payments or bookings (P2) | Within 4 working hours | Within 1 working day |
Minor bug with a workaround (P3) | Within 1 working day | Within 5 working days |
Small change to existing screens or text | Within 1 working day | Within 5 working days |
New feature, screen or integration | Within 2 working days | Added to our roadmap (see Feature requests and our roadmap) |
If the fault is with the cloud platform or a connected service, such as a payment provider or till system, we'll raise it with them straight away and chase it until it's fixed. Their response times then sit outside our control, but we'll never leave you without an update.
Any bug in the work we delivered that shows up in the first 30 days after launch is fixed free of charge. After that, bug fixes are covered by your support plan. A bug means the app not doing what we agreed it would do; new or changed functionality is a feature request.
You own your app and the data in it. Your app's code is kept in a secure repository away from the platform, so it's never tied to one provider. Your data is held in a managed cloud database. If you ever need data recovered, raise it as a P2 and we'll do everything we can to get it back quickly.
If you ever leave us, we'll hand over the code and help you export your data.
AI features. Some apps use AI from third-party providers, for example to write text or answer questions. AI can get things wrong, so check anything important before relying on it.
Connected services. Payment providers, till systems, email senders and other integrations run under their own terms and uptime.
Changes made outside our team. If anyone else edits the app, we can't guarantee our targets for problems that it causes. We'll still fix it, but it may be chargeable.
Any change that would affect everyone using a product goes on our roadmap, not into the support queue. That covers new features and changes to how things work in our web apps, SmartFlowCRM and the client portal. The roadmap is how we decide what to build next, and it keeps every client on the same tested version.
For web apps, the roadmap is how we deliver all new functionality. Improvements are built, tested and rolled out as planned releases, so a change made for one client never breaks something for another.
Your request | Where it goes |
|---|---|
A bug, or something not working as agreed | Support request, priority targets apply |
A change to your own content, branding or settings | Service request, targets in this agreement apply |
A new feature, or a change that would affect all users of a product | Feature request, onto the roadmap |
Something only your business needs that can't wait for the roadmap | Quoted as custom work and scheduled separately |
How it works:
Log it using "Request a feature" in the chat widget. If it's already on the roadmap, we'll add your vote to it.
We review new requests every month and mark each one as planned, under consideration or not right now, with a short reason.
Planned features show on our public roadmap and the roadmap tab in the chat widget. Vote for the ones that matter to you, as votes help us decide what comes first.
When a feature is released, we announce it in the news section of the chat widget.
Feature requests aren't covered by the response and completion targets in this agreement. We don't give delivery dates for roadmap items until they're planned, and then we share an estimated release window. If you raise a global change as a service request, we'll move it to the roadmap and let you know.
If we become aware of a breach affecting personal data in a website, web app or system we manage for you, we'll tell you within 24 hours of finding out. We'll explain what happened, what data is affected and what we're doing about it.
Under UK GDPR, you may need to report a breach to the Information Commissioner's Office (ICO) within 72 hours. Telling you quickly gives you time to do that, and we'll give you the information you need for your report.
These targets don't apply to:
New builds, redesigns and projects, which run to the timeline in your proposal.
Work we've quoted separately, which runs to the date we agree with you.
Problems caused by changes made by you or another supplier, such as installing plugins or editing code. We'll still fix them, but they may be chargeable.
Outages at third parties we don't control, such as domain registrars, payment providers, Google, Meta or the platforms SmartFlowCRM and our web apps are built on.
Hosting, email or domains managed by another company.
Delays while we wait for information, content or approval from you.
Events outside our reasonable control, such as major internet outages or cyber attacks on a provider.
If something falls outside your plan, we'll always tell you it's chargeable and get your go-ahead before we start. You'll never get a surprise bill.
We can only hit these targets if we have what we need. To help us help you:
Raise requests through the chat widget, one request per change.
Give us clear instructions, final copy, and high-quality images with the request.
Reply to our questions and approve work promptly.
Tell us before you or another supplier make changes to your site, web app or SmartFlowCRM account.
Keep your plan payments up to date. Accounts more than 14 days overdue are moved to P4 for all requests until settled.
Keep us updated with the right contact for your business.
If we're going to miss a target, we'll tell you before it passes, explain why and give you a new date. You'll never have to chase us to find out where something is.
If you're unhappy with how a request is being handled:
Reply on the request in the chat widget and ask for it to be escalated.
If it's still not resolved within 2 working days, email Chris Carr directly at [email protected] and we'll respond within 1 working day.
If our hosted uptime falls below 99.9% in a month for reasons within our control, we'll credit 10% of that month's hosting fee on request.
We'd rather keep you, but you're never locked in.
Your website. Your domain is always registered in your name, so it can move with you. Once your initial 12-month term is covered, your website is yours to take. We'll move it or hand it over, and send you a secure document with everything you need to run it elsewhere. Full details are in your contract.
SmartFlowCRM. You can export your data, such as contacts, at any time.
Web apps. We'll hand over your app's code and help you export your data (see Web apps).
We review this agreement at least once a year. If we change it, we'll give you 30 days' notice through the news section of the chat widget and by email.