LIGHTNING
PHONE · EMAIL · ENQUIRY MANAGEMENT

Know who asked. Know who is following up.

Calls, website forms and emails are easier to manage when the details reach one place and someone owns the next step. We set up phone, email and CRM workflows around how your business responds, from the first enquiry onwards.

The enquiry always arrives. Surviving is the hard part.

01

Calls arrive when nobody is free

They land while you are on site, in a meeting or on the other line. Voicemail catches a few. The rest ring out and the caller dials the next firm on the list.

02

Email that never arrives

Quotes land in spam. Notifications go to an address nobody opens. The shared inbox is a free account several people log into and delete from.

03

Nobody knows who owns it

The same enquiry sits in a personal inbox, a notepad and a call log. Nobody chases it, because nobody is certain somebody else has not already.

A small office desk with a handset lifted off its cradle, a laptop open on a list of enquiries and a notepad of scribbled callbacks.
A desk telephone in use beside a working screen

Your numbers. Your inbox. Your data.

Every account is registered to you. The numbers sit on your billing, the domain stays in your registrar, the CRM licence is yours and we work inside it as named users you can remove yourself. Every route, rule and integration we set is written down: which number rings where, which DNS records were changed and why a pipeline stage exists. If you decide to take this in-house next year, the numbers, the domain and the CRM are already in your name.

Scope starts with listening, not a proposal. We sit with your call log, your inbox and whatever the CRM already holds, and we tell you which of the three is actually costing you work. Sometimes the answer is a routing change and a DMARC record, not a migration. We will say so, and we will say when a routing change will not hold on top of a phone system that should have been replaced.

Ported, tested, then live. In that order.

01

Trace the current route

We ring your own numbers, send mail to your own addresses and watch where each one lands. You get a map of where calls and messages actually end up, including the routes nobody set up on purpose.

02

Build alongside the old one

New numbers, mailboxes and pipeline are built and tested while the existing setup keeps running. Nothing is switched until your team has taken real calls on it and sent real mail from it.

03

Port and cut over

Number porting is booked for a quiet window and mail records change with the old route still catching stragglers. Whatever history the old system will give up is migrated into the CRM before day one.

04

Watch it in real use

We check answer rate, bounced mail and enquiries sitting with no owner, then adjust routing and stages. The handover note your team keeps holds the routing map, the DMARC policy state and what each pipeline stage means.

Before you start. Practical questions, answered.

What to consider when deciding whether this work is right for your business.

01

Can 3CX log every call against the right customer record in Pipedrive?

Usually. The call event carries the caller's number, and a match on that number writes the call, its direction and its outcome onto the contact's timeline as it ends. Numbers matching nothing create a new record instead of being dropped, which is how most call logs end up half empty. Connecting phone and CRM

02

Our reception writes enquiries on a paper pad and types them into HubSpot later. Better way?

Yes. The record is created while the call is still happening, from a short form that opens with the caller's number already in it, so the entry is finished when the caller hangs up. The pad disappears because there is nothing left for it to hold.

03

Nobody answers the phone when we are all out on site. What happens to those calls?

An answering workflow can collect the reason for calling and contact details, then create a follow-up task for your team. The questions, opening hours, transfer options and fallback need to suit your business. We agree and test that journey before connecting it to your number, including what happens when a call needs a person. Automating the enquiry queue

04

Most of our calls are people moving an appointment. Can that stop being a call?

Often. The confirmation message carries a link into the same diary the office works from, so a customer moving their own slot moves it in the one place everybody reads. What is left on the phone is the work that needed a person anyway, and the diary stops existing in two versions.

05

We already pay for Microsoft 365. Do we need a separate CRM as well?

Probably not yet. Microsoft 365 already carries shared mailboxes, a calendar and file storage, so use the product you already pay for until the pipeline outgrows it. A CRM earns its place when you need every touch on one customer visible to people who never share an inbox.

06

Do we have to tell callers we record, and where do the recordings end up?

Yes, and the announcement plays before anything is captured rather than after the greeting. Recordings need a retention period set at the point they are stored, because a recording nobody deleted is a subject access request waiting to happen, and the caller has a right to a copy of it.

WORKING EXAMPLESWebsites built for businesses we own and run
WRITTEN SCOPEDeliverables and price agreed before work begins
DIRECT CONTACTA named person responsible for your project
CLEAR HANDOVERAccounts, access, documentation and support agreed up front

A phone line, an inbox and a CRM are one system pretending to be three. Wire them together and the call that comes in on Friday afternoon is still somebody's job on Monday morning.

Start with the change you want to make.

Tell us what you use now, where the work slows down and what a better result would look like. We will explain the next step, with any paid work agreed before it starts.

Talk to Lightning