I sent two messages to a mechanic through his website and received no answer.

When I visited him, he said: I paid a lot for that website, but I don t check those emails. It is all spam.

He did not need another complicated system. He needed a clear list of real customers who contacted him today.

That experience pushed me to build Customers Today over a weekend.

Many small businesses do not need pipelines, stages, reports and weeks of setup.

They need to know three things:

1. Who contacted us today?

2. What do they need?

3. Who is still waiting for an answer?

At what point does a simple customer list need to become a CRM?

A business can spend thousands on a website, add a polished contact form and still never answer the people using it.

The messages arrive in an inbox filled with spam, marketing emails, invoices and automatic notifications. Eventually, the owner stops checking it.

Have you ever contacted a business through its website and received no response? What do you think caused it?

We use AI to separate genuine customer enquiries from spam, sales pitches and automated messages.

The difficult product question is how much control users should have.

Should the system hide obvious noise automatically, place it in a separate folder, or show everything with confidence labels?

Which approach would make you trust the result?

Long customer messages are difficult to scan on a phone.

We reduce each enquiry to a short title and a one or two sentence summary while keeping the original message available.

For example:

Brake repair needed today

Many small business owners spend their day in workshops, shops, vehicles or customer locations. They are not sitting inside WordPress or watching an email inbox.

Would a mobile notification with the customer s request and a direct reply button help you respond faster?

Or do you still prefer handling every enquiry through email?

Direct integrations are convenient, but there are hundreds of form builders and website platforms.

Our fallback is simple: every business receives a private Customers Today email address. Point any form notification to that address and the enquiry can be processed.

Do you prefer native integrations, a universal email connection, or both?

We wanted onboarding to avoid migrations, CRM configuration and form replacement.

The basic setup is:

1. Create a business.

2. Connect a supported form or copy a private email address.

3. Send the next successful form notification there.

4. See the real customer appear.

What is the longest onboarding process you would accept for a tool designed to save missed customers?