Services & delivery
A better way to handle
the everyday work.
Start with the work your business needs handled. We agree the system, the exact connections and the support before building.
01 / Your phone receptionist
A phone receptionist.
Built around your business.
Plan a phone receptionist that handles incoming calls in English, using the business information and questions you approve.
What we agree
We agree the hours, recording and disclosure settings, the information collected and the escalation path. Your phone account stays in your name. The configuration has its own tests and written acceptance before a limited pilot is activated.
Inbound voice is a separately accepted component, not an automatic inclusion. It does not make emergency, dispatch or booking decisions.
02 / Customer records, organised
Your customer records.
Your rules.
Define the customer information your team needs, who can view or change it and how a request moves to the right person.
What we agree
We agree which customer-record software to use and exactly what it can add, show or update. The plan includes who has access, how changes are recorded and what happens if a connection fails. Each connection is tested before you rely on it.
Your account, your data and your export stay in your name. The system only gets the access you agree; compatibility with your existing tools must be checked.
03 / New enquiries, captured
The details your team
needs to respond.
Collect a name, contact, relevant job details and a preferred next step within an agreed intake workflow. Your team receives context instead of an unexplained request.
What we agree
The questions, record destination and human handoff are defined before the build. Your website is included in the engagement; if the existing site is suitable, we work with it.
A requested time is not a confirmed booking. Your team makes that commitment. Open the website chat demonstration.
04 / Less repetitive paperwork
One recurring task.
A defined working process.
Discuss a specific office operation: invoice preparation, a bookkeeping handoff or a records workflow. We define the inputs, checks and human approvals for that operation.
What we agree
Each build has its own written scope and acceptance. We do not sell an unspecified complete back office or assume every tool can be connected.
Related work
Review requests.
With permission.
A consent-based review-request process can be included in accepted scope. We agree when a request is appropriate, who sends it and how a customer declines. A request is never a promise of a review.
Ownership & delivery
You know what you own.
And who looks after it.
- Your accounts and data.Your domain, data and accounts stay in your name. Export, permissions and handover are written down.
- Tests before launch.Review ordinary requests, missing information, failed connections and the handoff to a person.
- Defined ongoing care.The agreement names what CAS maintains, how support works and when a change needs a new scope.
The work, the payment terms and permission to start are agreed in writing before delivery begins.
Important operating boundaries
Prices, quotes, work commitments, emergency severity and insurance coverage are decided by people at your business, never by the system.
Booking requests need human confirmation. No autonomous dispatch, health-data compliance, guaranteed outcome or unrestricted connection to every CRM is promised. Customer outreach, follow-up and re-engagement are not activated by an intake or voice engagement.
About Crusader
Start with the work.
Every service should have a clear job. Tell us what happens today, what your team needs and where the process breaks down. We turn that into a defined scope for the build.
A direct working relationship.
Steve scopes the work, reviews the tests with you and is the person you contact. The agreement names the responsibilities, the support and the decisions that stay with your team.
Your business stays yours.
Your domain, data and accounts stay in your name. Permissions, export and handover are agreed before launch.
Judge the working system.
A demonstration is not a customer result. Review what works, the failure cases and the written scope before relying on a system. CAS does not present fictional examples as delivered-client evidence.
04 / Getting started
No tech knowledge.
No problem.
- 01
Map the work.
Tell us what takes too much time or where new enquiries get stuck. We help you choose a useful place to start.
- 02
Build it. Test it.
See the work before it goes live. We test the normal steps, the handoffs and what happens when something goes wrong.
- 03
Keep it working.
Know who looks after what. Your agreement sets out the ongoing support, maintenance and changes.
03 / Put your numbers to work
What could a better
working day be worth?
Estimates only. Nothing is sent or saved.
Potential extra sales / month
–
Before job costs and service fees.
Possible jobs each week: –
Missed enquiries each week: –
Start with your enquiries, possible jobs and average sale. The numbers update as you type.
Allow for job costs and service fees
– / month after the job and service costs entered
Before tax, other overhead and one-time setup costs. Time value is not included.
Think about time spent taking messages, copying details or preparing paperwork.
Value of time freed up / month
–
– hours a month to put to other work.
Time freed up becomes cash saved only if your paid costs actually fall. It is not added to sales.
How the numbers work
Potential monthly sales = extra jobs per week × average sale × 52 ÷ 12. Monthly time value = weekly hours freed up × hourly cost × 52 ÷ 12. The after-cost figure uses the share left after job costs, then subtracts the monthly service cost you entered. Currency labels do not convert money. These calculations use your assumptions, not measured CAS results or a promise of future earnings.
Start with your business
What should your
system handle?
Tell Steve about the calls, records or recurring work you want to improve.
A conversation first. No purchase or appointment is made here.